"jaikiran" wrote : | When i had tested it, the jar file was exploded and at the root of the EAR. In your case, is the jar file in zip format or is it exploded? And are you seeing issues if you place a zipped jar file in the lib folder of the EAR (this is something i had not tried)? In https://jira.jboss.org/jira/browse/EJBTHREE-1254?focusedCommentId=1242828... I think my case is explained ;> anonymous wrote : After patch mentioned in forum thread (thanks jakiran ;>) On JBoss 4.2.1 there is additional problem (but close so comment here): | | If library from <jar-file> is also exploded and is situated in lib directory there is problem CNF from this library. | | Application.ear\lib\exploded-library-with-persistence-ob.jar has persistence.xml with | | {quote} | <jar-file>../exploded-library-lib-ob.jar</jar-file> | <jar-file>../../exploded-library-ob.jar</jar-file> | <jar-file>../library-ob.jar</jar-file> | {quote} | | Structure jars: | | Application.ear\lib\exploded-library-lib-ob.jar | Application.ear\exploded-library-ob.jar | Application.ear\lib\library-ob.jar | | On scanning persistence unit from exploded-library-with-persistence-ob.jar there is CNF while addind entity from Application.ear\lib\exploded-library-lib-ob.jar to PU. Scanning Application.ear\lib\library-ob.jar and Application.ear\exploded-library-ob.jar is OK. | | So Workaround is to move Application.ear\lib\exploded-library-lib-ob.jar to Application.ear. Any other options ? It is default structure for our project so I don't want be too invasive. Now I'm testing exploded deployment to boost developing. We are using maven2. My ear is exploded (Application.ear) My persistence library is in lib and is exploded (Application.ear\lib\exploded-library-with-persistence-ob.jar) When library is in lib and not exploded and referenced from <jar-file> there is no problem (Application.ear\lib\library-ob.jar). When library is in lib and exploded and referenced from <jar-file> there is CNF (Application.ear\lib\exploded-library-lib-ob.jar) When library is in root and exploded and referenced from <jar-file> there is no problem (Application.ear\exploded-library2-ob.jar) "jaikiran" wrote : | "skajotde" wrote : | | Thanks, I'll try java module in our maven build. | | | | Let us know how it goes. Thanks for clue ;> It resolved problem ;> For the moment I need only two jarModule exploded (ejb, war are exploded with no problem and are situated in root) so I revert to lib directory and I add Application.ear\lib\exploded-library-lib-ob.jar as java module to application.xml. Application deploys successful. <plugin> | <groupId>org.apache.maven.plugins</groupId> | <artifactId>maven-ear-plugin</artifactId> | <configuration> | <unpackTypes>ejb,war,sar,rar</unpackTypes> | <workDirectory>${basedir}/target/30-${project.build.finalName}.${packaging}</workDirectory> | <modules> | <!-- required changes from https://jira.jboss.org/jira/browse/EJBTHREE-1254 --> | <jarModule> | <groupId>pl.skajotde.tests</groupId> | <artifactId>exploded-library-with-persistence-ob.jar</artifactId> | <unpack>true</unpack> | </jarModule> | <jarModule> | <groupId>pl.skajotde.tests</groupId> | <artifactId>exploded-library-lib-ob.jar</artifactId> | <unpack>true</unpack> | <includeInApplicationXml>true</includeInApplicationXml> | </jarModule> | </modules> | </configuration> | </plugin> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174508#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...