logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siros Supavita" <si...@pathway-systems.com>
Subject Re: Interop with Log4j
Date Sat, 09 Feb 2002 08:34:51 GMT
Hi,

I'm not sure if my situation is the same thing you're discussing (sorry I
missed the first question).

I'm using log4j 1.2 alpha on my project. Using it with cactus 1.2 which is
built using log4j release (I believe it is 1.1.3), cause an
NoSuchMethodError to be thrown, when Cactus class try to make call to
Category.getInstance("classname"). I'm sure there is only one copy of log4j
in my classpath and it is 1.2 alpha.

I notice that the method is static and I believe Java use "static" reference
to resolve static method call at compile time. So I decide to get that
cactus class to re-compile with log4j 1.2 alpha, and the problem is gone. I
don't know the exact reason why, but I guess that it is something about
"static" reference to the method.

Do you have any ideas ?

Siros S.

----- Original Message -----
From: "Ceki Gülcü" <ceki@qos.ch>
To: "Log4J Developers List" <log4j-dev@jakarta.apache.org>;
<axis-dev@xml.apache.org>
Sent: Saturday, February 09, 2002 1:03 AM
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:tomj@macromedia.com]
> > Sent: Friday, February 08, 2002 11:36 AM
> > To: 'axis-dev@xml.apache.org'
> > Cc: 'log4j-dev@jakarta.apache.org'
> > 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:log4j-dev-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail: <mailto:log4j-dev-help@jakarta.apache.org>

--
Ceki Gülcü



--
To unsubscribe, e-mail:   <mailto:log4j-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-dev-help@jakarta.apache.org>





--
To unsubscribe, e-mail:   <mailto:log4j-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-dev-help@jakarta.apache.org>


Mime
View raw message