You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Eric Charles (JIRA)" <se...@james.apache.org> on 2015/03/01 10:02:04 UTC
[jira] [Closed] (JAMES-1561) [PATCH] JPA Entities need public
constructors
[ https://issues.apache.org/jira/browse/JAMES-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Charles closed JAMES-1561.
-------------------------------
Resolution: Fixed
Assignee: Eric Charles
Patch committed in trunk, thx Bernd.
> [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
> Assignee: Eric Charles
> Labels: patch
> Fix For: Trunk, 3.0.0-beta5
>
> Attachments: jpa_public_constructor.patch
>
> Original Estimate: 10m
> Remaining Estimate: 10m
>
> 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