[JBoss JIRA] Commented: (JBAS-7032) Getting invalid deployment on what appears to be valid, a webbeans ear file.
by John Ament (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-7032?page=com.atlassian.jira.plug... ]
John Ament commented on JBAS-7032:
----------------------------------
just wondering, can you provide a demo jboss-app.xml that works around this?
> 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
17 years
[JBoss JIRA] Updated: (JBAS-7032) Getting invalid deployment on what appears to be valid, a webbeans ear file.
by Shelly McGowan (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-7032?page=com.atlassian.jira.plug... ]
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
17 years
[JBoss JIRA] Commented: (JBAS-7032) Getting invalid deployment on what appears to be valid, a webbeans ear file.
by Stan Silvert (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-7032?page=com.atlassian.jira.plug... ]
Stan Silvert commented on JBAS-7032:
------------------------------------
No, I haven't tried it with the WBINT-16 fix.
I don't know exactly how the resource creeps in. I can only conclude that it leaks from the deployment of WhatsUpDawg.ear. So I'm guessing that when the WBDeployer puts /webbeans.deployer/lib-int/faces on the classpath then that makes it visible to all deployments.
Isolation of admin-console doesn't solve the problem since we can't ask everyone to isolate their apps just because a WebBeans app is running in the same AS instance.
> 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
17 years
[JBoss JIRA] Commented: (JBAS-7032) Getting invalid deployment on what appears to be valid, a webbeans ear file.
by Ales Justin (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-7032?page=com.atlassian.jira.plug... ]
Ales Justin commented on JBAS-7032:
-----------------------------------
Did you try this against my latest WB fix (WBINT-16)?
Or why exactly does admin-console get that faces/ added from WBUrlIntegrationDeployer?
Or how does that resource creep in?
btw: did we fix that admin-console CL isolation issue?
(by having proper jboss-web.xml)
> 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
17 years
[JBoss JIRA] Updated: (JBAS-7032) Getting invalid deployment on what appears to be valid, a webbeans ear file.
by Stan Silvert (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-7032?page=com.atlassian.jira.plug... ]
Stan Silvert updated JBAS-7032:
-------------------------------
Attachment: PrintResourcePathContextListener.class
> 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
17 years
[JBoss JIRA] Updated: (JBAS-7032) Getting invalid deployment on what appears to be valid, a webbeans ear file.
by Stan Silvert (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-7032?page=com.atlassian.jira.plug... ]
Stan Silvert updated JBAS-7032:
-------------------------------
Attachment: PrintResourcePathContextListener.java
> 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
17 years
[JBoss JIRA] Commented: (JBAS-7032) Getting invalid deployment on what appears to be valid, a webbeans ear file.
by Stan Silvert (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-7032?page=com.atlassian.jira.plug... ]
Stan Silvert commented on JBAS-7032:
------------------------------------
I have verified that the analysis was correct. I created a ServletContextListener (attached) that finds faces-config.xml files in the same manner as JSF. When WhatsUpDawg.ear is deployed, admin-console finds the faces-config.xml file in /webbeans.deployer/lib-int/faces/META-INF/faces-config.xml. Here is the output:
13:29:12,581 INFO [STDOUT] ******************************************
13:29:12,583 INFO [STDOUT] ** Resource Paths for META-INF/faces-config.xml:
13:29:12,602 INFO [STDOUT] vfszip:/C:/jboss-5.1.0.GA.jdk6/jboss-5.1.0.GA/server/default/deploy/admin-console.war/WEB-INF/lib/org.jboss.seam-jboss-seam-2.1.0.SP1.jar/META-INF/faces-config.xml
13:29:12,607 INFO [STDOUT] vfsfile:/C:/jboss-5.1.0.GA.jdk6/jboss-5.1.0.GA/server/default/deployers/webbeans.deployer/lib-int/faces/META-INF/faces-config.xml
13:29:12,610 INFO [STDOUT] vfszip:/C:/jboss-5.1.0.GA.jdk6/jboss-5.1.0.GA/server/default/deploy/admin-console.war/WEB-INF/lib/jsf-facelets-1.1.15.B1.jar/META-INF/faces-config.xml
13:29:12,614 INFO [STDOUT] vfszip:/C:/jboss-5.1.0.GA.jdk6/jboss-5.1.0.GA/server/default/deploy/admin-console.war/WEB-INF/lib/jboss-seam-debug-2.1.0.SP1.jar/META-INF/faces-config.xml
13:29:12,619 INFO [STDOUT] vfszip:/C:/jboss-5.1.0.GA.jdk6/jboss-5.1.0.GA/server/default/deploy/admin-console.war/WEB-INF/lib/richfaces-impl-3.3.0.GA.jar/META-INF/faces-config.xml
13:29:12,624 INFO [STDOUT] vfszip:/C:/jboss-5.1.0.GA.jdk6/jboss-5.1.0.GA/server/default/deploy/admin-console.war/WEB-INF/lib/jboss-seam-ui-2.1.0.SP1.jar/META-INF/faces-config.xml
13:29:12,628 INFO [STDOUT] vfszip:/C:/jboss-5.1.0.GA.jdk6/jboss-5.1.0.GA/server/default/deploy/admin-console.war/WEB-INF/lib/richfaces-ui-3.3.0.GA.jar/META-INF/faces-config.xml
13:29:12,632 INFO [STDOUT] ******************************************
Without WhatsUpDawg.ear you get:
13:32:41,564 INFO [STDOUT] ******************************************
13:32:41,568 INFO [STDOUT] ** Resource Paths for META-INF/faces-config.xml:
13:32:41,602 INFO [STDOUT] vfszip:/C:/jboss-5.1.0.GA.jdk6/jboss-5.1.0.GA/server/default/deploy/admin-console.war/WEB-INF/lib/org.jboss.seam-jboss-seam-2.1.0.SP1.jar/META-INF/faces-config.xml
13:32:41,606 INFO [STDOUT] vfszip:/C:/jboss-5.1.0.GA.jdk6/jboss-5.1.0.GA/server/default/deploy/admin-console.war/WEB-INF/lib/jsf-facelets-1.1.15.B1.jar/META-INF/faces-config.xml
13:32:41,611 INFO [STDOUT] vfszip:/C:/jboss-5.1.0.GA.jdk6/jboss-5.1.0.GA/server/default/deploy/admin-console.war/WEB-INF/lib/jboss-seam-debug-2.1.0.SP1.jar/META-INF/faces-config.xml
13:32:41,617 INFO [STDOUT] vfszip:/C:/jboss-5.1.0.GA.jdk6/jboss-5.1.0.GA/server/default/deploy/admin-console.war/WEB-INF/lib/richfaces-impl-3.3.0.GA.jar/META-INF/faces-config.xml
13:32:41,622 INFO [STDOUT] vfszip:/C:/jboss-5.1.0.GA.jdk6/jboss-5.1.0.GA/server/default/deploy/admin-console.war/WEB-INF/lib/jboss-seam-ui-2.1.0.SP1.jar/META-INF/faces-config.xml
13:32:41,627 INFO [STDOUT] vfszip:/C:/jboss-5.1.0.GA.jdk6/jboss-5.1.0.GA/server/default/deploy/admin-console.war/WEB-INF/lib/richfaces-ui-3.3.0.GA.jar/META-INF/faces-config.xml
13:32:41,631 INFO [STDOUT] ******************************************
To see this result, just add the attached class to /admin-console/WEB-INF/lib/classes. Then put this in /admin-console/WEB-INF/web.xml:
<listener>
<listener-class>org.jboss.jbas7032.PrintResourcePathContextListener</listener-class>
</listener>
> 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: 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
17 years
[JBoss JIRA] Created: (JBXB-217) SchemaBindingValidator: extended XSD choice is not recognized
by Alexey Loubyansky (JIRA)
SchemaBindingValidator: extended XSD choice is not recognized
-------------------------------------------------------------
Key: JBXB-217
URL: https://jira.jboss.org/jira/browse/JBXB-217
Project: JBoss XML Binding (JBossXB)
Issue Type: Bug
Affects Versions: JBossXB-2.0.2.Beta1
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Fix For: JBossXB-2.0.2.GA
Xerces XSD model for something like
<xsd:complexType name="classloaderType" mixed="true">
<xsd:complexContent>
<xsd:extension base="classLoaderValueType"/>
</xsd:complexContent>
</xsd:complexType>
where classLoaderValueType is a choice will be represented by xerces as
sequence[choice[classLoaderValueType's choice content], sequence[]]
One of the confusing parts is the empty sequence at the end. Validator should be able to recognize a structure like this and treat it as a choice.
--
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
17 years