RE: [JBoss-dev] Missing jars (javax.persistence)

I would say they should be in the server lib dir as part of the JPA project. The only question is whether there are potential conflicts in terms of deployment isolation if both JPA and EJB3 are being used. In that case, we might need to obfuscate the non-javax.* classes and make them part of the ejb3.deployer. -----Original Message----- From: jboss-development-bounces(a)lists.jboss.org [mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Carlo de Wolf Sent: Thursday, August 03, 2006 3:02 AM To: jboss-development(a)lists.jboss.org Subject: [JBoss-dev] Missing jars (javax.persistence) Hi all, I saw that ejb3.deployer no longer contains a lot of jar files. But I need these three: <fileset dir="${hibernate.entitymanager.lib}"> <include name="ejb3-persistence.jar"/> <include name="hibernate-entitymanager.jar"/> </fileset> <fileset dir="${hibernate.annotations.lib}"> <include name="hibernate-annotations.jar"/> </fileset> (Basicly the javax.persistence stuff.) They are not in the <server>/lib directory, but they are in the client directory. Is another project going to deploy these artifacts or can I add them back to the build.xml of ejb3.deployer? IMHO they're part of a separate product (javax.persistence) on which ejb3 is dependant. Carlo _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development