You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Rick Curtis (Commented) (JIRA)" <ji...@apache.org> on 2011/12/01 21:20:40 UTC
[jira] [Commented] (OPENJPA-2083) Unmapped fields silently treated
as transient
[ https://issues.apache.org/jira/browse/OPENJPA-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161109#comment-13161109 ]
Rick Curtis commented on OPENJPA-2083:
--------------------------------------
Kevin / Harold -
Thoughts on the correct 'fix' for this issue? I'm leaning toward a warning message...
Thanks,
Rick
> Unmapped fields silently treated as transient
> ---------------------------------------------
>
> Key: OPENJPA-2083
> URL: https://issues.apache.org/jira/browse/OPENJPA-2083
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa
> Affects Versions: 2.1.1
> Reporter: Harald Wellmann
> Priority: Minor
>
> The JPA 2.0 spec requires any non-static non-transient entity field to be persistent unless explicitly mapped as transient by a @Transient annotation or the equivalent XML.
> OpenJPA 2.1.1 silently treats some unmapped non-primitive fields as transient instead of throwing an exception or at least logging a warning.
> Example:
> @Entity
> public class City {
> @Id
> private String name;
> private Integer population;
> private java.util.concurrent.Executor executor;
> // getters and setters
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira