[prev in list] [next in list] [prev in thread] [next in thread]
List: james-dev
Subject: [jira] [Created] (JAMES-1561) [PATCH] JPA Entities need public constructors
From: "Bernd Waibel (JIRA)" <server-dev () james ! apache ! org>
Date: 2014-10-29 9:26:33
Message-ID: JIRA.12751342.1414574758000.361891.1414574793951 () Atlassian ! JIRA
[Download RAW message or body]
Bernd Waibel created JAMES-1561:
-----------------------------------
Summary: [PATCH] JPA Entities need public constructors
Key: JAMES-1561
URL: https://issues.apache.org/jira/browse/JAMES-1561
Project: James Server
Issue Type: Improvement
Components: James Core
Affects Versions: Trunk, 3.0.0-beta5
Environment: Eclipse LUNA
Java version: 1.6.0_45, vendor: Sun Microsystems Inc.
Reporter: Bernd Waibel
Fix For: Trunk
The JPA standard restricts JPA Entities to have a public or protected constructor, \
not a private one.
See: http://docs.oracle.com/javaee/6/tutorial/doc/bnbqa.html
The JPA entities JPADomain and JPARecipientRewrite have private constructors. \
Depending of the implementation of the JPA provider, this could lead to runtime \
errors. Using protected instead of private constructors should not be a problem, \
cause they are not used.
I will attach a patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic