It doesn't matter where the exception is thrown, as it is logged with
error level. You should enable all error level messages, doesn't
matter from which class.

-Matej

On 9/5/07, Jan Stette <[EMAIL PROTECTED]> wrote:
> Great, thanks.  Do you know which class to enable logging for in the log4j
> configs, and at which level, to get this?  Enabling all Wicket logging is of
> course quite verbose...
>
> Thanks,
> Jan
>
> On 05/09/07, Matej Knopp <[EMAIL PROTECTED]> wrote:
> >
> > Yeah, it does. Just check your logs, because this happens after page
> > is rendered, so if an exception is thrown, you won't see it in
> > browser.
> >
> > -Matej
> >
> > On 9/5/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> > > It is checked automatically when a statefull page is stored at the end
> > > of the request in development mode.
> > >
> > > Martijn
> > >
> > > On 9/5/07, Jan Stette <[EMAIL PROTECTED]> wrote:
> > > > I'm looking for a way to make sure that our Wicket pages are
> > serialized and
> > > > de-serialized while in development mode, to catch any mistakes as
> > early as
> > > > possible.  The "Pro Wicket" book mentions a log setting in
> > HttpSessionStore
> > > > but I don't think this is relevant anymore for Wicket 1.3 (we're on
> > 1.3 beta
> > > > 3).
> > > >
> > > > A javadoc comment at the top of the IDebugSettings interface talks
> > about the
> > > > "serializeSessionAttributes" setting but I can't see a reference to
> > this in
> > > > the code.  I've had a search through the mailing list archives but
> > it's not
> > > > clear to me what the current status is for this.  Could someone
> > enlighten
> > > > me?
> > > >
> > > > Many thanks,
> > > > Jan
> > > >
> > >
> > >
> > > --
> > > Buy Wicket in Action: http://manning.com/dashorst
> > > Apache Wicket 1.3.0-beta3 is released
> > > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to