On Jan 22, 2007, at 10:13 AM, [EMAIL PROTECTED] wrote:
Hi,
Log4j works in objects that implements Serializable?
If so, how this is possible? If a client receives an object from
the server that
implements Serializable, how the client knows how to interpret log4j
instructions?
Sincerely,
Pe
At 10:13 AM 1/22/2007, you wrote:
>Hi,
>
>Log4j works in objects that implements Serializable?
>
>If so, how this is possible? If a client receives an object from the
>server that
>implements Serializable, how the client knows how to interpret log4j
>instructions?
>
Log4j Loggers are not Serializ
If you want to find the ClassLoader of a class, just do
.class.getClassLoader(). Just be careful when using PARENT_LAST in
WAS 5.x, because you sometimes get strange behavior, e.g. in my particular
case, I got javax.sql.DataSource loaded by a descendant classloader of the
actual WebSphere implement
I don't quite understand. Do you want to serialize log4j classes?
Anytime that you serialize an object both the client and server need
all classes that the object uses. If the object has a log4j Logger
than both the client and server should have log4j.jar in the
classpath.
On 1/22/07, [EMAIL PR
Hi,
Log4j works in objects that implements Serializable?
If so, how this is possible? If a client receives an object from the server that
implements Serializable, how the client knows how to interpret log4j
instructions?
Sincerely,
Pedro
-
Mistery solved... we are using an old version of a e-spreadsheet software
that had a log4j-related bug. Their software basically turned off logging,
and it is documented here:
http://esupport.actuate.com/es/download/actuate7sp1updatedocs/readme.pdf
Thanks for your help,
Cristian Jansenson
Thanks a TON Ian, this worked for me finally! :-)
yahoo.com> writes:
>
> This is a simple mistake I've made many a time before. The value of
> log4j.configuration needs to be a URL. So the following will work:
>
> java -Dlog4j.configuration=file:./log4j.xml
>
> -Ian
I used something like
