You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Arbi Sookazian (JIRA)" <ji...@codehaus.org> on 2010/03/24 19:01:38 UTC
[jira] Commented: (MECLIPSE-649) generated application.xml is
invalid - EAR fails to deploy
[ http://jira.codehaus.org/browse/MECLIPSE-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215157#action_215157 ]
Arbi Sookazian commented on MECLIPSE-649:
-----------------------------------------
This problem is reproducible with Maven 2.2.1 as well...
> generated application.xml is invalid - EAR fails to deploy
> ----------------------------------------------------------
>
> Key: MECLIPSE-649
> URL: http://jira.codehaus.org/browse/MECLIPSE-649
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: M2Eclipse support
> Affects Versions: 2.0
> Environment: Windows XP, Eclipse 3.5.2.SR2, JBoss AS 4.2.2.GA, Maven 2.0.8, Java 1.5, m2eclipse 0.10.0
> Reporter: Arbi Sookazian
> Priority: Minor
> Attachments: application.xml
>
>
> See attached application.xml. Note that some of the ejb modules have ".ejb" instead of the correct and expected ".jar" extensions. The location of the application.xml generated by m2eclipse is: \myModule\src\main\application\META-INF
> EAR fails to deploy on JBoss 4.2.2.GA.
> The mvn build (when I run 'mvn clean install') is using a "bad" application.xml presumably generated by m2eclipse when the EAR is constructed (i.e. both packaged and exploded EAR versions have the bad application.xml). The contents of the bad application.xml look like this:
> <module>
> <ejb>com.echo.cis.ejb.dao-1.5.1-SNAPSHOT.ejb</ejb>
> </module>
> <module>
> <ejb>com.echo.cis.editors-1.5.1-SNAPSHOT.ejb</ejb>
> </module>
> <module>
> <ejb>com.echo.cis.crud.dao-1.5.1-SNAPSHOT.ejb</ejb>
> </module>
> <module>
> <ejb>/com.echo.cis.ejb.dao-1.5.1-SNAPSHOT.jar</ejb>
> </module>
> <module>
> <ejb>/com.echo.cis.crud.dao-1.5.1-SNAPSHOT.jar</ejb>
> </module>
> Note the ".ejb" extensions on some of the ejb modules above. The files exist in the EAR with .jar extensions so JBoss AS throws following exception when I deploy the EAR:
> 09:46:55,671 ERROR [MainDeployer] Could not initialise deployment: file:/C:/java/jboss-4.2.2.GA/server/default/deploy/com.echo.cis.gui.ear-1.5.1-SNAPSHOT.ear/
> org.jboss.deployment.DeploymentException: url file:/C:/java/jboss-4.2.2.GA/server/default/deploy/com.echo.cis.gui.ear-1.5.1-SNAPSHOT.ear/com.echo.cis.services.merchant-1.5.1-SNAPSHOT.ejb could not be opened, does it exist?
> When I delete the "bad" application.xml in foo/src/main/application/META-INF directory and run 'mvn clean install' again, the application.xml in the packaged or exploded EAR is correct (i.e. all ejb module now have .jar extensions, not .ejb).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira