On JBoss, it's best to use JBoss transaction manager, and datasources defined in JBoss.
You would typically remove all the jars that are duplicate of existing JBoss/J2EE APIs, such as jca, jta, etc. to avoid classloading issues. alex On Thu, Apr 2, 2009 at 7:36 AM, Jackson, Douglas < [email protected]> wrote: > Hi! > Has anyone seen class path issues like the following in JBoss? I thought I > fixed it by putting > tranql-connector-1.1.jar and geronimo-j2ee-connector_1.5_spec-1.0.jar in > the jboss lib endorsed > directory, but it came back. Had one successful run then had to reboot. > I am using jboss 4.2.2.GA. Help with a workaround would be appreciated. > Thanks in advance, > -Doug. > > javax.persistence.PersistenceException: java.lang.ClassCastException: > org.tranql.connector.jdbc.Data > Source > at > org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:252) > at > org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.ja > va:120) > at > javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:51) > at > org.apache.ode.store.jpa.DbConfStoreConnectionFactory.<init>(DbConfStoreConnectionFactory > .java:45) > at > org.apache.ode.store.ProcessStoreImpl.<init>(ProcessStoreImpl.java:128) > at > org.apache.ode.axis2.ODEServer.createProcessStore(ODEServer.java:469) > at > org.apache.ode.axis2.ODEServer.initProcessStore(ODEServer.java:462) > at org.apache.ode.axis2.ODEServer.init(ODEServer.java:162) > at org.apache.ode.axis2.ODEServer.init(ODEServer.java:116) > at > org.apache.ode.axis2.hooks.ODEAxisServlet.init(ODEAxisServlet.java:53) > >
