|Exploded EAR and Glassfish [message #924379]
||Wed, 26 September 2012 20:00
| Steve Hostettler
Registered: September 2012
I have a simple ear that is composed of an EJB jar and a war file. I use maven for dependency management.
and the glassfish application server.
Every fine as long as I have the ejb project (open) in my workspace. The problems start when one of the ear dependency is pulled as a jar as for instance with the following configuration:
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-resource deploy-path="/" source-path="/target/m2e-wtp/ear-resources"/>
<wb-resource deploy-path="/" source-path="/src/main/application" tag="defaultRootSource"/>
<dependent-module archiveName="MavenEnterpriseApp-web-1.0-SNAPSHOT.war" deploy-path="/" handle="module:/resource/MavenEnterpriseApp-web/MavenEnterpriseApp-web">
<dependent-module archiveName="MavenEnterpriseApp-ejb-1.0-SNAPSHOT.jar" deploy-path="/" handle="module:/classpath/var/M2_REPO/com/mycompany/MavenEnterpriseApp-ejb/1.0-SNAPSHOT/MavenEnterpriseApp-ejb-1.0-SNAPSHOT.jar">
then I get the following error message:
Expected to find an expanded directory for submodule MavenEnterpriseApp-ejb-1.0-SNAPSHOT.jar but found a JAR. If this is a directory deployment be sure to expand all submodules.
this might not be the correct forum to ask my question but to be honest I struggling to find out where the problem is : wtp, m2e, m2e-wtp, glassfish connector, ...
I would like to be sure where to look at before starting to debug the plugins.
So far I was able to narrow down the problem to wtp + glassfish connector. That is no m2e and m2e-wtp,
Any idea of how to solve (or even to understand) the problem
Powered by FUDForum
. Page generated in 0.14977 seconds