APAR status
Closed as program error.
Error description
Description: When an attempt is made to instantiate a custom mapping class, the following exception is thrown: Caused by: <openjpa-2.1.2-SNAPSHOT-r422266:1179900 fatal user error> org.apache.openjpa.util.MetaDataException: Field "aaa.bbb.entities.MyEntity.name" declared custom mapping strategy "aaa.bbb.AValueHandler", but this strategy cannot be instantiated. at org.apache.openjpa.meta.JavaTypes.classForName(JavaTypes.java:27 at org.apache.openjpa.meta.JavaTypes.classForName(JavaTypes.java:23 at org.apache.openjpa.meta.JavaTypes.classForName(JavaTypes.java:20 at org.apache.openjpa.jdbc.meta.MappingRepository.namedStrategy (MappingRepository.java:580) ... 96 more
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All IBM WebSphere Application Server * * Feature * * Pack for OSGi Applications and JPA 2.0 * * users * **************************************************************** * PROBLEM DESCRIPTION: A MetaDataException occurs declaring * * that a custom mapping strategy cannot * * be instantiated by OpenJPA. * **************************************************************** * RECOMMENDATION: * **************************************************************** The ValueHandlers for customer mappings (such as ClassStrategy, DiscriminatorStrategy, etc) tries to load the class using the OSGi ClassLoader, and not the application's ClassLoader. Because customer classes do not reside in that level of the ClassLoader hierarchy, the lookup fails and is reported as a MetaDataException.
Problem conclusion
The strategy to locate a Class type requested by the MappingRepository has been enhanced to leverage the configured ClassResolver. The fix for this APAR is currently targeted for inclusion in fix pack 1.0.0.9. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM63960
Reported component name
JPA OSGI FEATUR
Reported component ID
5724J0857
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-05-04
Closed date
2012-05-11
Last modified date
2012-05-11
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
JPA OSGI FEATUR
Fixed component ID
5724J0857
Applicable component levels
R700 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 September 2020