james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernd Waibel (JIRA)" <server-...@james.apache.org>
Subject [jira] [Updated] (JAMES-1561) [PATCH] JPA Entities need public constructors
Date Wed, 29 Oct 2014 09:27:33 GMT

     [ https://issues.apache.org/jira/browse/JAMES-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bernd Waibel updated JAMES-1561:
--------------------------------
    Attachment: jpa_public_constructor.patch

> [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
>              Labels: patch
>             Fix For: Trunk
>
>         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


Mime
View raw message