Fixes are available
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
The nested classpath element inside the mappingtool ant task is ignored when loading the persistent configuration file. User got the following error: <openjpa-2.0.2-SNAPSHOT-r422266:1361284M fatal user error> org.apache.openjpa.util.MetaDataException: MetaDataFactory could not be configured (conf.newMetaDataFactoryInstance() returned null). This might mean that no configuration properties were found. Ensure that you have a META-INF/persistence.xml file, that it is available in your classpath, or that the properties file you are using for configuration is available. If you are using Ant, please see the <properties> or <propertiesFile> attributes of the task's nested <config> element. This can also occur if your OpenJPA distribution jars are corrupt, or if your security policy is overly strict.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0.0 and V8.5.0 who make use the * * OpenJPA MappingTool Ant task. * **************************************************************** * PROBLEM DESCRIPTION: Nested classpath element inside * * the OpenJPA MappingTool Ant task are * * ignored when loading the persistent * * configuration file. * **************************************************************** * RECOMMENDATION: * **************************************************************** Take the following entry in an Ant build file: <target name="generateDDLCreate"> <taskdef resource="org/apache/openjpa/jdbc/ant/antlib.xml" classpath="com.ibm.ws.jpa.thinclient_JPA2FEP1.0.0.jar" > </taskdef> <mappingtool schemaAction="build" sqlFile="create.sql"> <classpath> <pathelement location="mapping-tool-pi.jar" /> <pathelement location="mapping-tool-persistenceunit-pi.jar" /> </classpath> </mappingtool> .... This build file runs the OpenJPA MappingTool Ant task. The build file contains two nested classpath entries to two jars. The jars are as follows: A) mapping-tool-pi.jar contains one JPA entity B) mapping-tool-persistenceunit-pi.jar contains META-INF/persistence.xml Given this setup, a org.apache.openjpa.util.MetaDataException is thown. This occurs because the nested classpath entires are ignored and as such the necessary jars are not found.
Problem conclusion
This fix ensures that the proper classpath is used when invoking the OpenJPA MappingTool. The fix for this APAR is currently targeted for inclusion in Service Levels (Fix Packs) 8.0.0.6 and 8.5.0.2 of WebSphere Application Server versions 8.0.0 and 8.5.0. 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
PM73312
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-09-20
Closed date
2012-12-31
Last modified date
2012-12-31
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PM77941 PM80449
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
29 October 2021