log.runtimeexception is already doing log.error(e.getMessage(), e);
and he is still not seeing the stacktrace...
-igor
On Mon, Jun 29, 2009 at 9:41 AM, mbrictson<
matt@...> wrote:
>
> If you simply call log.error(e), your log will only contain e.toString(),
> which does not include the stack trace. You need to use the 2-arg version of
> log.error() if you want the full trace.
>
> Try this:
>
> log.error("An uncaught runtime exception occurred", e);
>
>
> jelevy wrote:
>>
>> Igor,
>> Can you give me some direction on how to go about getting the "e".
>>
>> In my own RequestCycle I've done the following:
>>
>> @Override
>> protected void logRuntimeException(RuntimeException e) {
>> super.logRuntimeException(e);
>> log.error(e);
>> }
>>
>>
> --
> View this message in context:
http://www.nabble.com/Mysterious-NullPointerException-tp24094116p24257631.html> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
users-unsubscribe@...
> For additional commands, e-mail:
users-help@...
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@...
For additional commands, e-mail:
users-help@...