[
https://issues.apache.org/jira/browse/OPENJPA-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-2024.
--------------------------------------
Resolution: Fixed
Already fixed on master: bfa48697e is on master. MetamodelImpl.java:413-416 now
logs meta-field-not-param as a warning and returns null instead of throwing.
Closing; please reopen if this still happens with OpenJPA 4.x.
> IllegalStateException: localized message key: meta-field-not-param
> ------------------------------------------------------------------
>
> Key: OPENJPA-2024
> URL: https://issues.apache.org/jira/browse/OPENJPA-2024
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Kevan Lee Miller
> Priority: Major
>
> Geronimo testing (currently on 2.1.0) has turned up the following problem:
> java.lang.IllegalStateException: localized message key: meta-field-not-param;
> substitutions: [class com.foo.Baz_, serialVersionUID, long]
> at
> org.apache.openjpa.persistence.meta.MetamodelImpl.getParameterziedType(MetamodelImpl.java:341)
> at
> org.apache.openjpa.persistence.meta.MetamodelImpl.populate(MetamodelImpl.java:310)
> at
> org.apache.openjpa.persistence.meta.MetamodelImpl.instantiate(MetamodelImpl.java:257)
> at
> org.apache.openjpa.persistence.meta.MetamodelImpl.find(MetamodelImpl.java:226)
> at
> org.apache.openjpa.persistence.meta.MetamodelImpl.<init>(MetamodelImpl.java:91)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.getMetamodel(EntityManagerFactoryImpl.java:346)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.getCriteriaBuilder(EntityManagerFactoryImpl.java:333)
> at
> org.apache.openjpa.persistence.EntityManagerImpl.getCriteriaBuilder(EntityManagerImpl.java:1638)
> at
> org.apache.openjpa.persistence.EntityManagerImpl.getCriteriaBuilder(EntityManagerImpl.java:101)
> at com.foo.Test.query(Test.java:xxx)
> serialVersionUID is a synthetic field added by new Aries Proxy/Weaving code.
> I'm pretty confident that their weaving is the cause of this error. Is it
> possible to ignore synthetic method? Or can you provide some additional
> information about the cause of this exception?
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
