Hello list,
once again occurs some mirgration problems to 0.9.7. This time we
present a nice TransactionManagerAcquireException:
org.exolab.castor.jdo.transactionmanager.TransactionManagerAcquireException:
Problem obtaining JDO configuration: Nested error: Stream closed
at
org.exolab.castor.jdo.transactionmanager.TransactionManagerFactoryRegistry.load(TransactionManagerFactoryRegistry.java:199)
at org.exolab.castor.jdo.JDOManager.getDatabase(JDOManager.java:690)
at com.morixs.mcare.ds.castor.CastorDS.getDB(CastorDS.java:121)
at com.morixs.mcare.ds.castor.CastorDS.init(CastorDS.java:106)
[...]
Caused by: org.exolab.castor.mapping.MappingException: Nested error:
Stream closed
at
org.exolab.castor.jdo.engine.JDOConfLoader.loadConfiguration(JDOConfLoader.java:98)
at
org.exolab.castor.jdo.engine.JDOConfLoader.getTransactionDemarcation(JDOConfLoader.java:145)
at
org.exolab.castor.jdo.transactionmanager.TransactionManagerFactoryRegistry.load(TransactionManagerFactoryRegistry.java:160)
... 8 more
Please remember, we only relaced castor.jar in our app and replace
depracted JDO code with JDOManager. No other changes. I wonder why every
new version is incompatible against predecessors.
Code to init JDOManager
JarEntityResolver pResolver = new JarEntityResolver();
String strMappingLocation = Configuration.getValue(CastorDS.class,
"CastorMapping");
InputSource pDatabaseConfiguration = pResolver.resolveEntity(null,
strMappingLocation);
//JDO.loadConfiguration(pDatabaseConfiguration, pResolver, null);
JDOManager.loadConfiguration(pDatabaseConfiguration, pResolver, null);
manager = JDOManager.createInstance("MobileCare");
manager .getDatabase();
Any suggestions or hints?
Thanks in advance
Andre Teubner
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
