On Tue, 13 Sep 2005 19:36:52 -0700, Michael A Chase wrote:
> The only things showing up in the context.log() output now are startup
> messages which I'm not worried about and exception messages from low-level
> libraries which I'd really like to see in the log4j logs.
I eventually found the com.e
On Tue, 13 Sep 2005 09:19:09 -0500, Jacob Kjome wrote:
>>> Quoting Michael A Chase <[EMAIL PROTECTED]>:
>>
Can anyone point me to some way to capture the logging done via
(ServletContext).log() so everything can go through log4j?
> Ahhh, yes. Of course you are right. I guess I hastily
Quoting Michael A Chase <[EMAIL PROTECTED]>:
> On Mon, 12 Sep 2005 09:05:18 -0500, Jacob Kjome wrote:
>
> > Quoting Michael A Chase <[EMAIL PROTECTED]>:
>
> >> Can anyone point me to some way to capture the logging done via
> >> (ServletContext).log() so everything can go through log4j?
> >>
> > G
On Mon, 12 Sep 2005 09:05:18 -0500, Jacob Kjome wrote:
> Quoting Michael A Chase <[EMAIL PROTECTED]>:
>> Can anyone point me to some way to capture the logging done via
>> (ServletContext).log() so everything can go through log4j?
>>
> Grab the LOG4J_SANDBOX_ALPHA3 tag of the logging-log4j-sandbo
Quoting Michael A Chase <[EMAIL PROTECTED]>:
> I'm not at work now so I don't have the exact version information, but I
> don't think it matters much.
>
> We are running a web application under OC4J which provides logging via a
> ServletContext com.evermind.http.Application. We've converted all o
I'm not at work now so I don't have the exact version information, but I
don't think it matters much.
We are running a web application under OC4J which provides logging via a
ServletContext com.evermind.http.Application. We've converted all our
code to use log4j, but we are still seeing errors fr
