[
https://jira.jboss.org/jira/browse/JBAS-7032?page=com.atlassian.jira.plug...
]
Stan Silvert commented on JBAS-7032:
------------------------------------
You can reproduce this by dropping the new ear into /deploy on jboss-5.1.0.GA.
The reason admin-console is using WBPhaseListener is because it is there. When
admin-console starts up, JSF sees the path /webbeans.deployer/lib-int/faces on its
classpath. JSF searches its classpath for META-INF/faces-config.xml files. When it see
the faces-config.xml for webbeans it installs the WBPhaseListener.
So I think the problem is that the WB deployer is putting itself on the classpath in such
a way that the admin-console sees it. admin-console shoudn't know anything about the
/webbeans.deployer/lib-int/faces directory.
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