Well, it's hard to say.  When you include a stack trace for an error, it's
helpful if you can get the full stack trace (with the exception and caused
by) because I can't tell which line actually put you into the catch.

But it seems like something is closing your response before you get to this
redirect method.  I'd put a breakpoint on the close method of the http
response to see if it's being closed before you get to this one.

--
Jeremy Thomerson
http://www.wickettraining.com



On Wed, Oct 7, 2009 at 2:05 AM, Eyal Golan <[email protected]> wrote:

> BTW,
> the 'null' is the message of the exception.
> Looking at the exception in the break-point: the exception is:
> org.mortbay.jetty.EofException
>
> thanks.
>
>
> Eyal Golan
> [email protected]
>
> Visit: http://jvdrums.sourceforge.net/
> LinkedIn: http://www.linkedin.com/in/egolan74
>
> P  Save a tree. Please don't print this e-mail unless it's really necessary
>
>
> On Wed, Oct 7, 2009 at 1:18 AM, Jeremy Thomerson
> <[email protected]>wrote:
>
> > null - should mean NullPointerException.... do you get the stacktrace to
> > see
> > where it's coming from?  Paste into reply....
> >
> > --
> > Jeremy Thomerson
> > http://www.wickettraining.com
> >
> >
> >
> > On Tue, Oct 6, 2009 at 12:41 PM, Eyal Golan <[email protected]> wrote:
> >
> > > Hi,
> > > I did some refactoring in an old Wicket code amd I get the warning
> > message
> > > in the subject:
> > > 2009-10-06 19:37:34,484 WARN
> > [org.apache.wicket.protocol.http.WebResponse]
> > > -
> > > redirect to ?wicket:interface=:5:::: failed: null
> > >
> > > I tried to debug, did some breakpointing etc. but could not understand
> > why
> > > do I get this.
> > > Can someone give me a hint on where to start looking and to understand
> > > what's going on?
> > >
> > > Thanks,
> > >
> > > Eyal
> > >
> > > Eyal Golan
> > > [email protected]
> > >
> > > Visit: http://jvdrums.sourceforge.net/
> > > LinkedIn: http://www.linkedin.com/in/egolan74
> > >
> > > P  Save a tree. Please don't print this e-mail unless it's really
> > necessary
> > >
> >
>

Reply via email to