3.2 allows for control of the class loading behavior at the ejb-jar, war, sar and ear levels and this is defined in the various dtds in the dist under
docs/dtds. The META-INF/jboss.xml config for the ejb-jar would be something
like:


<?xml version='1.0' encoding='UTF-8' ?>

<!DOCTYPE jboss PUBLIC
   "-//JBoss//DTD JBOSS 3.2//EN"
   "http://www.jboss.org/j2ee/dtd/jboss_3_2.dtd";>

<jboss>
   <loader-repository>
      jboss.test:ejb-jar=log4j113-ejb.jar
   </loader-repository>
</jboss>

--
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx

Oisin Kim wrote:
Thanks Danny and Janardhan,

I totally agree with you (Danny) regarding how this may seem confusing
to mere mortals ;-)

Is there a way to change either the behaviour of the classloader or do
this same setting for the deployment of ejb-jars and other j2ee
components - it seems very silly to add a perfectly deployable ejb-jar
to an empty ear just to define the classloader used.

You saved me hours of toil guys, thanks,

Thanks in advance for any more advice on this!

Oisin




-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to