On JRun 3.1, we get this when invoking Axis:
org/apache/log4j/Logger
java.lang.NoClassDefFoundError: org/apache/log4j/Logger
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at
allaire.jrun.servlet.JRunServletLoader.loadServletInstance(../servlet/JRunServletLoader.java:197)
at
allaire.jrun.servlet.JRunServletLoader.loadServletInstance(../servlet/JRunServletLoader.java:161)
at
allaire.jrun.servlet.JRunServletLoader.loadServlet(../servlet/JRunServletLoader.java:149)
at allaire.jrun.servlet.JRunSE.getServletReference(../servlet/JRunSE.java:1706)
at allaire.jrun.servlet.JRunSE.runServlet(../servlet/JRunSE.java:1232)
at
allaire.jrun.servlet.JRunRequestDispatcher.forward(../servlet/JRunRequestDispatcher.java:89)
at allaire.jrun.servlet.JRunSE.service(../servlet/JRunSE.java:1553)
at allaire.jrun.servlet.JRunSE.service(../servlet/JRunSE.java:1543)
at allaire.jrun.servlet.JvmContext.dispatch(../servlet/JvmContext.java:364)
at allaire.jrun.http.WebEndpoint.run(../http/WebEndpoint.java:115)
at allaire.jrun.ThreadPool.run(../ThreadPool.java:272)
at allaire.jrun.WorkerThread.run(../WorkerThread.java:75)
This is running with an axis.jar built with log4j1.2, in a webapp where log4j1.1.3 is
available.
Interestingly, this does NOT happen when using the SimpleAxisServer, which is run
outside of an app server context. Perhaps this is somehow a JRun problem, although
I'm still confused as to how it could happen at all.
Hey Axis+Tomcat users - do you guys see problems like this with the nightly build
axis.jar and the log4j-core from xml-axis/java/lib?
--Glen
> -----Original Message-----
> From: Ceki G�lc� [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 08, 2002 1:04 PM
> To: Log4J Developers List; '[EMAIL PROTECTED]'
> Subject: RE: Interop with Log4j
>
>
>
> Log4j 1.2alpha is perfectly backward compatible with 1.1.3. It's not
> maybe or perhaps. Please provide exact details about the
> nature of the problem. Thank you, Ceki
>
> At 11:40 08.02.2002 -0500, Glen Daniels wrote:
>
> >Hi all!
> >
> >I think this is a result of the change to make Category extend
> >Logger. All of our code uses Category, and so using code
> compiled with
> >log4j 1.2 with log4j 1.1.3 causes some problem with Logger not being
> >found. Sorry I can't be more detailed myself. Are you guys
> aware of any
> >problems like this?
> >
> >--Glen
> >
> > > -----Original Message-----
> > > From: Tom Jordahl [mailto:[EMAIL PROTECTED]]
> > > Sent: Friday, February 08, 2002 11:36 AM
> > > To: '[EMAIL PROTECTED]'
> > > Cc: '[EMAIL PROTECTED]'
> > > Subject: RE: Interop with Log4j
> > >
> > >
> > > Tom Jordahl wrote:
> > > > The latest log4j from CVS has made a incompatible change
> > > from the previous
> > > > release version.
> > >
> > > Sam Ruby wrote:
> > > > Have you communicated this to the log4j development team?
> > > Such changes
> > > > would eventually impact Axis users... I can tell you that
> > > the log4j team
> > > > takes backwards compatibility very seriously and
> > > agressively address any
> > > > issues brought to their attention.
> > >
> > > I have not in fact communicated with the log4j team. Hi guys!
> > >
> > > Here is what I know: If you try to use the nightly build
> > > axis.jar with the log4j.jar checked in to our CVS tree, it
> > > will fail due to a missing log4j class. I apologize for not
> > > having the class name handy.
> > >
> > > --
> > > Tom Jordahl
> > > Macromedia
> > >
> >
> >--
> >To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
Ceki G�lc�
