[
https://issues.apache.org/jira/browse/OPENJPA-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161704#comment-13161704
]
Kevin Sutter commented on OPENJPA-2083:
---------------------------------------
I think a warning message would be an excellent first step. At least it would
highlight to users that OpenJPA may not be doing the processing that you are
expecting (or vice versa). This could still potentially be raised as a spec
violation, but that's splitting hairs in my opinion. So, let's highlight the
processing with a warning message and say we're done.
> 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
