[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9053) seam-registration examle from wolf test repo is incorrectly deployed

[Fred Bricon (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-9053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614651#comment-12614651 ] 

Fred Bricon commented on JBIDE-9053:
------------------------------------

I tested the project on Helios SR2 + JBT 3.2.1CR3 + m2e 1.0 + m2e-wtp 0.13 (both m2e features being installed with JBT 3.2.1CR3 \o/) and EAP 5.1.
The deployed EAR has the same contents as a CLI generated .ear. However, the deployed app won't work out of the box, because the deployed EAR use the project name (register-ear.ear), and not the expected finalName as defined in the pom (jboss-seam-registration.ear). This is both a m2e-wtp and WTP limitation. 

In order to deploy the app, there are 4 solutions :
1 - open the Server configuration, go to the Deployment tab and change the deployment location to jboss-seam-registration.ear
2 - refactor the artifactId of registration-ear to jboss-seam-registration 
3 - Modify the examples :
    * registration-ear/pom.xml : change the finalName to <finalName>registration-ear</finalName>
    * registration-web/src/main/webapp/WEB-INF/component.xml : change pattern to <core:init jndi-pattern="registration-ear/#{ejbName}/local"/> 

4 - Modify the examples : 
    * registration-web/pom.xml : change the jndiName property to <jndiPattern>registration-ear/#{ejbName}/local</jndiPattern> 
    * registration-web/pom.xml : enable the webResource filtering (currently commented), 
    * registration-web/src/main/conf/component.xml : use <core:init jndi-pattern="${jndiPattern}"/>


> seam-registration examle from wolf test repo is incorrectly deployed 
> ---------------------------------------------------------------------
>
>                 Key: JBIDE-9053
>                 URL: https://issues.jboss.org/browse/JBIDE-9053
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 3.2.1.CR1
>         Environment: JBossTools 3.2.1 CR1 org.eclipse.m2e.core (0.12.1.20110112-1712), org.maven.ide.eclipse.wtp 0.11.1.20101108-1810 or  0.12.0.20110421-1500
>            Reporter: Libor Zoubek
>            Assignee: Fred Bricon
>              Labels: m2eclipse, upstream
>             Fix For: 3.2.1.CR3, 3.3.0.M3
>
>         Attachments: seam-registration.zip
>
>
> I am testing wolf repository (maven repo of EAP 5.1). There are several example projects. These examples depend on maven artifacts shipped by wolf repo. There is a problem with example called webapp-seam-registration. This example can be built and deployed using maven CLI (mvn install jboss:deploy). But .. when I import it into JBoss Tools using 'Import existing maven project' and then deploy it on EAP 5.1 I get deployment errors. I was comparing the deoplyed EARs and found out, that the problem is, that application.xml (contained in registration-ear project) does not contain {noformat}<module><ejb>jboss-seam.jar</ejb></module>{noformat}
> Deployment from CLI works fine ->application.xml has proper content

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira