[
http://jira.jboss.com/jira/browse/JBAS-2026?page=all ]
Dimitris Andreadis closed JBAS-2026.
------------------------------------
Fix Version/s: JBossAS-5.0.0.Beta2
JBossAS-4.2.0.GA
Resolution: Done
Assignee: Dimitris Andreadis
Thanks Fabiano. The problem actually appeared for RAR, WEB and EJB modules with non-ear
parents.
I've fixed a little differently by introducing a FactoryUtils class.
Better late than never :)
Wrong placeholder ear created
-----------------------------
Key: JBAS-2026
URL:
http://jira.jboss.com/jira/browse/JBAS-2026
Project: JBoss Application Server
Issue Type: Patch
Security Level: Public(Everyone can see)
Components: Management services
Affects Versions: JBossAS-4.0.3RC1, JBossAS-4.0.2 Final
Environment: jxm, twiddle
Reporter: Fabiano C. de Oliveira
Assigned To: Dimitris Andreadis
Priority: Minor
Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA
Attachments: management.patch
When a WarModule is created a placeholder ear is Always created. When a module that have
a child WarModule but is NOT a ear module a ear placeholder is created but this ear in
truth dont exist.
Just take a look in the ServiceModule jbossweb-tomcat55.sar. The JMX-Console show it like
a ServiceModule and a like a J2EEApplication.
This patch just take a look if the parent module is a EAR, otherwise WebModule use the
J2EEServer as the parent.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira