Eclipse Glassfish plugin v1.0.52 EAR deployment problem
I'm having a problem (more a feature than a bug) with deploying EAR to glassfish app server with glassfish eclipse plugin.
- eclipse java ee 20090920-1017
- glassfish eclipse plugin v1.0.52
- glassfish v3 final
I have test.ear with following structure:
- jpa.jar (contains META-INF/persistence.xml and entity classes inside 'db' package)
ejb1.jar is using jpa.jar persistence.xml to get entity manager for persistence unit
specified in jpa.jar and use its entity classes.
Scenario1 (works as expected)
When deploying test.ear directly from glassfish admin console, application works as expected (ejb1.jar can access jpa.jar classes and can use persistence unit defined in jpa.jar) - deployed folders are all exploded; jpa.jar is not exploded (there is actually a jpa.jar in deployed lib/ folder).
Scenario 2 (does not work as expected)
When deploying from eclipse all folders are exploded including jpa.jar inside lib folder, like this: lib/jpa.jar/META-INF/...
In this case ejb1.jar does not see persistence.xml which is now located in lib/jpa.jar/META-INF/persistence.xml.
How can I get the glassfish plugin not to explode jar files found in EAR/lib ?
Am I doing something wrong ?