Hello,
What you describe is how JBoss was/is working in the 2.x releases. In 3.0,
the CL mechanism has been totally revamped (UnifiedClassLoader, UCL).
Consequently, your code will use the JBoss lo4j JAR even if you provide
yours in your JAR.
Take a look at the recent threads on JBoss-dev explaining how to create an
EAR that owns its own UCL that will allow you do to that.
Cheers,
Sacha
> -----Message d'origine-----
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]De la part de Nick
> Pierpoint
> Envoy� : mardi, 4 juin 2002 11:56
> � : [EMAIL PROTECTED]
> Objet : [JBoss-user] Distributing LOG4J with an application
>
>
> Hello all.
>
> Now that Log4J is distributed with JBoss, I seem to be having problems
> with my applications that bundle the Log4J JAR.
>
> As I understood any JARs loaded with a deployed application would use a
> Class loader that took precedence over the JBoss application Class
> loader. However, when I tried to use the current release of Log4J (1.2.3
> - where 'Logger' is used in preference to 'Category') I noticed that I
> could *only* access the Log4J classes in the version in the JBoss
> application class path (i.e. in the 'lib' directory) - my bundled Log4J
> JAR was *not* being used.
>
> Have I misunderstood how Class loading works in JBoss?
>
> Can I still bundle Log4J with my Application, or do I have to create a
> 'special' to for JBoss - please tell me I don't have to do that :-) ??
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
