On further investigation I think that this is caused by a problem in LiDO that was concealed in 3.0 by the njar implementation.
david jencks On 2002.07.01 17:08:06 -0400 David Jencks wrote: > Deploying the LiDO jdo implementation is failing on 3.0.1 while trying to > access the jdo metadata in a classes jar file. This works in 3.0 final. > Any ideas where I should start looking? > > Thanks > david jencks > > Heres some stack trace, note the peculiar url it is looking for: > > 2002-07-01 17:01:55,365 ERROR >[org.jboss.resource.connectionmanager.XATxConnectionManager] > Starting failed > javax.jdo.JDOFatalUserException: Can't locate > file:/usr/java/lido/samples/company_common/company_domain.jar!/metadata.jdo > at com.libelis.lido.xml.m.a(MetadataXMLParser.java:31) > at >com.libelis.lido.PersistenceManagerFactory.d(PersistenceManagerFactory.java:94) > at >com.libelis.lido.PersistenceManagerFactory.h(PersistenceManagerFactory.java:86) > at com.libelis.lido.jca.JDOConnectionFactory.k(JDOConnectionFactory.java:27) > at >com.libelis.lido.jca.JDOManagedConnectionFactory.createConnectionFactory(JDOManagedConnectionFactory.java:59) > at >org.jboss.resource.connectionmanager.RARDeployment.startManagedConnectionFactory(RARDeployment.java:578) > at java.lang.reflect.Method.invoke(Native Method) > at >org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
