[ http://jira.jboss.com/jira/browse/JBAS-861?page=history ]
Scott M Stark closed JBAS-861:
------------------------------
Resolution: Cannot Reproduce Bug
> EJB-jar w/o jboss.xml defaults to other EJB-jar's jboss.xml
> -----------------------------------------------------------
>
> Key: JBAS-861
> URL: http://jira.jboss.com/jira/browse/JBAS-861
> Project: JBoss Application Server
> Type: Bug
> Versions: JBossAS-3.2.6 Final
> Reporter: SourceForge User
> Assignee: Scott M Stark
>
>
> SourceForge Submitter: johnqueso .
> This bug was produced with JBoss 3.2.3 on WinXP Pro
> with JDK 1.4.1, although I have no reason to believe
> that it would be constrained to this environment.
> Somehow, if one of your EJB-jars (in an EAR) doesn't
> specify a jboss.xml descriptor, this descriptor is
> picked up from another EJB-jar in the EAR, which will
> result in the following error:
> 09:26:14,746 ERROR [XmlFileLoader] failed to load
> jboss.xml. There could be a syntax error.
> org.jboss.deployment.DeploymentException: Error in
> jboss.xml for Bean SubscriptionList: found in jboss.xml
> but not in ejb-jar.xml
> Basically, here is the setup:
> \EAR
> --\EJB1
> ----\META-INF\jboss.xml
> ----\META-INF\ejb-jar.xml
> --\EJB2
> ----\META-INF\ejb-jar.xml
> Now, when JBoss deploys the EAR file, it gets through
> the initialization of EJB1 just fine. However, when it
> gets to EJB2, it reads the ejb-jar.xml and initializes
> the ApplicationMetaData , and then tries to augment it
> from the jboss.xml file. Both of these are read with
> calls similar to:
> getClassloader().getResource("META-INF/ejb-jar.xml");
> getClassloader().getResource("META-INF/jboss.xml");
> In this case, EJB2 has no jboss.xml, and therefore the
> classloader hierarchy being used by the XMLFileLoader
> seems to move up a step and look at the wider EAR.
> Since the last EJB, EJB1 was placed in this
> classloader, it immediately finds META-INF/jboss.xml
> from _that_ jar, and loads it. This results in searches
> for the EJB's defined in EJB1 inside the
> ApplicationMetaData which was setup based on the
> ejb-jar.xml file in EJB2.
> I know that this is not the desired behavior, but I'm
> not well enough versed in the internals of JBoss to
> come up with an adequate patch. I'm not even sure
> where the defaults are stored for the case where an EJB
> deployed in isolation doesn't contain a jboss.xml file.
> I'm sure you all have a default scenario, to make JBoss
> as user-friendly as possible, but in the case of an
> EAR, this logical path will never be traversed.
> For my initial postings/musings/explorations on this
> bug, see the Forum:
> http://jboss.org/index.html?module=bb&op=viewtopic&t=44884
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
