It's Nabble that removes the < param > tags
On Thu, Feb 4, 2010 at 5:10 PM, Cimballi wrote:
> :D Ok, I just noticed than the mailing list engine, or maybe google,
> removes the < param > tag...
>
> Cimballi
>
>
>
-
To unsubscri
Hum, it's strange because in fact at fatal level you should only have
fatal log messages...
On Thu, Feb 4, 2010 at 5:33 PM, DavidZaz wrote:
>
> As an update, I changed the level in my struts.xml to FATAL and the logging
> started working. This behavior confuses me since I don't have any loggers
exception, the log4j
>>>> logger
>>>> does not print the exception to my appender. As a test, I wrote the
>>>> following code into one of my actions:
>>>>
>>>> org.apache.log4j.Logger myLogger =
>>>> org.apache.lo
pplication and throw an unhandled exception, the log4j
>>> logger
>>> does not print the exception to my appender. As a test, I wrote the
>>> following code into one of my actions:
>>>
>>> org.apache.log4j.Logger myLogger =
>>> org.apache.log4
age");
>>
>> The "Test Message" did appear in my log, but I don't understand why
>> struts
>> will not provide the same behavior through its exception interceptor.
>>
>> Does anyone have any ideas about what I am doing wrong?
>> --
>>
rg.apache.log4j.Logger.getLogger("error.unhandled");
> myLogger.warn("Test Message");
>
> The "Test Message" did appear in my log, but I don't understand why struts
> will not provide the same behavior through its exception interceptor.
>
>
g?
--
View this message in context:
http://old.nabble.com/Problem-with-Exception-Interceptor-tp27459864p27459864.html
Sent from the Struts - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: user-unsubscr...@struts
7 matches
Mail list logo
