I've run 1.2.13 and 14 in WAS 6.1 on windows and aix with no issues.
So the only other factors might be related to Z... but I'd imagine
those would be more likley to be in using existing in log4j configs
(e.g. a file appender with a unix style path, etc) without changes but
not in log4j itself...
ALL
Our company has plans to migrate to Websphere Application Server 6.1 on zOS,
we are currently using version 1.2.8 of log4j
I wanted to understand whether this version will still work on WAS6.1 on zOS
or we will have to upgrade to later version on log4j?
Regards
Ravish Naje
The Royal Bank
Using separate classloaders might work.
On 8/6/07, Nicholas Hogg <[EMAIL PROTECTED]> wrote:
> Hi,
>
> This is my first post to this list - I have the following problem:
>
> For a project I am working on I am required to use a 3rd party jar.
> This jar uses log4j-1.1.3, where as my project uses log
Hi,
This is my first post to this list - I have the following problem:
For a project I am working on I am required to use a 3rd party jar.
This jar uses log4j-1.1.3, where as my project uses log4j-1.2.13. As
I'm sure you are aware there are classes (Category) in 1.1.3 that are
not backwards