Kevin Sutter wrote: > > The JPA spec requires a global jndi name, which would require a name along > the lines of "jdbc/EswaadAppDS". I know that WebSphere allows the use of > a > component-level name, but that would be along the lines of > "java:comp/env/jdbc/EswaadAppDS". Not sure what namespace you are going > after with just "java:/EswaadAppDS". Maybe it's something unique with > jboss that I am not familiar with. >
According to JBoss, the above DS is in the Namespace but is not exposed as a Global JNDI as it is not recommended to expose the DS. I agree that the openjpa.MetaDataFactory and openjpa.jdbc.DBDictionary is not really needed and hence it is removed. The problem still exists and I also posted the exception in JBoss forums but failed to receive any response from the community. So far, I am doing my development in hibernate but our intention is to move away from it and adapt openJPA I would appreciate if anybody can figure out what is causing the problem. I only have Serp.jar, common-lang.jar. log4j.jar, openJPA.jar and all of standard JBoss jars in the JBoss lib classpath. The Geromino.* are not there and I don't think it is needed -- View this message in context: http://www.nabble.com/Help-needed-with-JBoss-and-openJPA-tp15603051p15760089.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
