[jboss-jira] [JBoss JIRA] Updated: (JBAS-7032) Getting invalid deployment on what appears to be valid, a webbeans ear file.

Tue Jul 14 16:43:29 EDT 2009

     [ https://jira.jboss.org/jira/browse/JBAS-7032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shelly McGowan updated JBAS-7032:
---------------------------------

RE: btw: did we fix that admin-console CL isolation issue? (by having proper jboss-web.xml)
The admin-console.war includes a jboss-web.xml with the following: 
<class-loading>
        <loader-repository>
            org.jboss.on:loader=embedded
            <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
        </loader-repository>
    </class-loading>

I have been looking at different app packaging to determine if there are other issues besides applications with web beans.  In addition to the web beans application, I have found that an EAR which includes SEAM/RF library jars in the EAR/lib directory *without* a jboss-app.xml (and EAR isolation is set to false by default in ear-deployer-jboss-beans.xml) also has the same problem; specifically, picking up another deployment's faces-config.xml .  Using Stan's ServletContextListener, the output with jboss-seam-booking (with jboss-app.xml removed):

2009-07-14 15:38:54,608 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/admin-console
2009-07-14 15:38:54,705 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (main) Initializing Mojarra (1.2_12-b01-FCS) for context '/admin-console'

2009-07-14 15:38:58,168 INFO  [STDOUT] (main) ******************************************
2009-07-14 15:38:58,168 INFO  [STDOUT] (main) ** Resource Paths for META-INF/faces-config.xml:
2009-07-14 15:38:58,201 INFO  [STDOUT] (main) vfszip:/work/EAP5/JBPAPP_5_0/build/output/jboss-5.0.0.Beta/server/default/deploy/admin-console.war/WEB-INF/lib/richfaces-impl-3.3.0.GA.jar/META-INF/faces-config.xml
2009-07-14 15:38:58,202 INFO  [STDOUT] (main) vfszip:/work/EAP5/JBPAPP_5_0/build/output/jboss-5.0.0.Beta/server/default/deploy/jboss-seam-booking.ear/jboss-seam.jar/META-INF/faces-config.xml
2009-07-14 15:38:58,202 INFO  [STDOUT] (main) vfszip:/work/EAP5/JBPAPP_5_0/build/output/jboss-5.0.0.Beta/server/default/deploy/admin-console.war/WEB-INF/lib/jboss-seam-ui-2.1.0.SP1.jar/META-INF/faces-config.xml
2009-07-14 15:38:58,202 INFO  [STDOUT] (main) vfszip:/work/EAP5/JBPAPP_5_0/build/output/jboss-5.0.0.Beta/server/default/deploy/admin-console.war/WEB-INF/lib/richfaces-ui-3.3.0.GA.jar/META-INF/faces-config.xml
2009-07-14 15:38:58,202 INFO  [STDOUT] (main) vfszip:/work/EAP5/JBPAPP_5_0/build/output/jboss-5.0.0.Beta/server/default/deploy/admin-console.war/WEB-INF/lib/org.jboss.seam-jboss-seam-2.1.0.SP1.jar/META-INF/faces-config.xml
2009-07-14 15:38:58,202 INFO  [STDOUT] (main) vfszip:/work/EAP5/JBPAPP_5_0/build/output/jboss-5.0.0.Beta/server/default/deploy/admin-console.war/WEB-INF/lib/jsf-facelets-1.1.15.B1.jar/META-INF/faces-config.xml
2009-07-14 15:38:58,202 INFO  [STDOUT] (main) vfszip:/work/EAP5/JBPAPP_5_0/build/output/jboss-5.0.0.Beta/server/default/deploy/admin-console.war/WEB-INF/lib/jboss-seam-debug-2.1.0.SP1.jar/META-INF/faces-config.xml

Setting EAR isolation to true in ear-deployer-jboss-beans.xml or providing a jboss-app.xml, the faces-config.xml from the jboss-seam-booking app is not found and both apps work together.    

> Getting invalid deployment on what appears to be valid, a webbeans ear file.
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-7032
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7032
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Deployers
>         Environment: JBoss AS 5.1
> JDK 1.6 u 13
> OpenSuSe 11.1 / SLES 10.2
>            Reporter: John Ament
>            Assignee: Shelly McGowan
>            Priority: Blocker
>             Fix For: JBossAS-5.2.0.Beta1
>
>         Attachments: PrintResourcePathContextListener.class, PrintResourcePathContextListener.java, WhatUpDawg.ear, WhatUpDawg.ear
>
>
> The best description I can give is from the forum.
> Basically, I have an EAR that appears to be completely valid, it's 2 war's and 1 ejb module.  It's built using web beans.  I get the described stack trace when either deploying via the UI or just dropping the EAR file in deploy.  However, I get different results.  When I drop the ear in and restart, it loads perfectly (my app) but embedded jopr fails.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira