]
Jason T. Greene updated JBAS-7032:
----------------------------------
Priority: Major (was: Blocker)
This is NOT a blocker, because the correct solution is to use isolation, which will be on
by default in 5.2.
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
Fix For: JBossAS-5.2.0.Beta1
Attachments: jboss-app.xml, 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: