subject:"WicketRuntimeException"

gt; Hi all,
>> >>> >> >>
>> >>> >> >> I think such question occurs from time to time on this list,
>> but I
>> >>> >> >> have never found a good answer how to solve such problem in
>> general.
>> >>> >> >> The problem is similar to my last question:
>> >>> >> >>
>> >>> >> >>
>> >>> >>
>> >>>
>> http://apache-wicket.1842946.n4.nabble.com/How-to-handle-click-on-disabled-links-ListenerInvocationNotAllowedException-td4666287.html
>> >>> >> >> but now there is a situation when link was removed from page
>> (not
>> >>> >> >> disabled).
>> >>> >> >>
>> >>> >> >> So page was rendered in a browser, on the server component tree
>> was
>> >>> >> >> changed, but user clicks a link in a browser before this changes
>> >>> will
>> >>> >> >> be pushed to it. It leads to an exception:
>> >>> >> >>
>> >>> >> >> org.apache.wicket.WicketRuntimeException: Component 'xxx' has
>> been
>> >>> >> >> removed from page.
>> >>> >> >> at
>> >>> >> >>
>> >>> >>
>> >>>
>> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:178)
>> >>> >> >> at
>> >>> >> >>
>> >>> >>
>> >>>
>> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
>> >>> >> >> at
>> >>> >> >>
>> >>> >>
>> >>>
>> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
>> >>> >> >> at
>> >>> >> >>
>> >>> >>
>> >>>
>> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
>> >>> >> >> at
>> >>> >> >>
>> >>> >>
>> >>>
>> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
>> >>> >> >> at
>> >>> >> >>
>> >>> >>
>> >>>
>> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
>> >>> >> >> at
>> >>> >> >>
>> >>> >>
>> >>>
>> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
>> >>> >> >> at
>> >>> >> >>
>> >>> >>
>> >>>
>> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
>> >>> >> >> at
>> >>> >> >>
>> >>> >>
>> >>>
>> org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
>> >>> >> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
>> >>> >> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>> >>> >> >>
>> >>> >> >> How it should be properly handled in application? Unfortunately
>> this
>> >>> >> >> is not a dedicated exception to catch somewhere, but a common
>> >>> >> >> WicketRuntimeException.
>> >>> >> >>
>> >>> >> >> --
>> >>> >> >> Best regards,
>> >>> >> >> Daniel
>> >>> >> >>
>> >>> >> >>
>> >>> -
>> >>> >> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> >>> >> >> For additional commands, e-mail: users-h...@wicket.apache.org
>> >>> >> >>
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> -
>> >>> >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> >>> >> > For additional commands, e-mail: users-h...@wicket.apache.org
>> >>> >> >
>> >>> >>
>> >>> >>
>> -
>> >>> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> >>> >> For additional commands, e-mail: users-h...@wicket.apache.org
>> >>> >>
>> >>> >>
>> >>>
>> >>> -
>> >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> >>> For additional commands, e-mail: users-h...@wicket.apache.org
>> >>>
>> >>>
>> >>
>> >>
>> >> --
>> >> Regards - Ernesto Reinaldo Barreiro
>> >>
>> >
>> >
>> >
>> > --
>> > Regards - Ernesto Reinaldo Barreiro
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>



-- 
Regards - Ernesto Reinaldo Barreiro

Re: How to handle click on removed links - WicketRuntimeException (Component 'xxx' has been removed from page)?

87.html
> >>> >> >> but now there is a situation when link was removed from page (not
> >>> >> >> disabled).
> >>> >> >>
> >>> >> >> So page was rendered in a browser, on the server component tree
> was
> >>> >> >> changed, but user clicks a link in a browser before this changes
> >>> will
> >>> >> >> be pushed to it. It leads to an exception:
> >>> >> >>
> >>> >> >> org.apache.wicket.WicketRuntimeException: Component 'xxx' has
> been
> >>> >> >> removed from page.
> >>> >> >> at
> >>> >> >>
> >>> >>
> >>>
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:178)
> >>> >> >> at
> >>> >> >>
> >>> >>
> >>>
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
> >>> >> >> at
> >>> >> >>
> >>> >>
> >>>
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
> >>> >> >> at
> >>> >> >>
> >>> >>
> >>>
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
> >>> >> >> at
> >>> >> >>
> >>> >>
> >>>
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
> >>> >> >> at
> >>> >> >>
> >>> >>
> >>>
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
> >>> >> >> at
> >>> >> >>
> >>> >>
> >>>
> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
> >>> >> >> at
> >>> >> >>
> >>> >>
> >>>
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
> >>> >> >> at
> >>> >> >>
> >>> >>
> >>>
> org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
> >>> >> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
> >>> >> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> >>> >> >>
> >>> >> >> How it should be properly handled in application? Unfortunately
> this
> >>> >> >> is not a dedicated exception to catch somewhere, but a common
> >>> >> >> WicketRuntimeException.
> >>> >> >>
> >>> >> >> --
> >>> >> >> Best regards,
> >>> >> >> Daniel
> >>> >> >>
> >>> >> >>
> >>> -
> >>> >> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >>> >> >> For additional commands, e-mail: users-h...@wicket.apache.org
> >>> >> >>
> >>> >> >
> >>> >> >
> >>> >> >
> -
> >>> >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >>> >> > For additional commands, e-mail: users-h...@wicket.apache.org
> >>> >> >
> >>> >>
> >>> >>
> -
> >>> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >>> >> For additional commands, e-mail: users-h...@wicket.apache.org
> >>> >>
> >>> >>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >>> For additional commands, e-mail: users-h...@wicket.apache.org
> >>>
> >>>
> >>
> >>
> >> --
> >> Regards - Ernesto Reinaldo Barreiro
> >>
> >
> >
> >
> > --
> > Regards - Ernesto Reinaldo Barreiro
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
Regards - Ernesto Reinaldo Barreiro

Re: How to handle click on removed links - WicketRuntimeException (Component 'xxx' has been removed from page)?

Sorry, but for me all these solutions are hacks :).
I want to use standard components (eg. AjaxLink) to do simple things.
I don't want to think everywhere how to handle such scenarios. It
should be handled properly on a framework level. I think there is
always possibility that component state on server and DOM tree on
client browser are inconsistent (and not necessary because of push
requests). Maybe it should be a dedicated exception on such situation
("Component 'xxx' has been removed from page.") at least or maybe we
can invent a better solution in core?

--
Daniel

On Fri, Jul 4, 2014 at 4:11 PM, Ernesto Reinaldo Barreiro
 wrote:
> Maybe you could even just push JSON to client side and generate items
> content at client side which is going to be way faster
>
>
> On Fri, Jul 4, 2014 at 4:06 PM, Ernesto Reinaldo Barreiro <
> reier...@gmail.com> wrote:
>
>> Why don't you try routing all the click to a part of you application that
>> is always available? E.g.
>>
>> 1- You have a list of items that are pushed... They are in a certain
>> container that is "always" there... At client and server side
>> 2- The items are pushed but instead of normal AJAX link you use link to
>> the parent never changing container passing ID of item. This way click will
>> never fail and it is still sort of object oriented...
>>
>>
>>
>> On Fri, Jul 4, 2014 at 3:59 PM, Daniel Stoch 
>> wrote:
>>
>>> On Fri, Jul 4, 2014 at 3:14 PM, Martin Grigorov 
>>> wrote:
>>> > Hi,
>>> >
>>> > You can use Atmopshere to hide/disable the client side too, not just the
>>> > server side.
>>>
>>> Of course, I already do that.
>>> But user can click the link after state was changed on the server side
>>> but before these changes are pushed to client browser.
>>>
>>> --
>>> Daniel
>>>
>>>
>>> >
>>> > Martin Grigorov
>>> > Wicket Training and Consulting
>>> > https://twitter.com/mtgrigorov
>>> >
>>> >
>>> > On Fri, Jul 4, 2014 at 1:46 PM, Daniel Stoch 
>>> wrote:
>>> >
>>> >> On Fri, Jul 4, 2014 at 12:33 PM, Sven Meier  wrote:
>>> >> >> So page was rendered in a browser,
>>> >> >> on the server component tree was changed
>>> >> >
>>> >> >
>>> >> > What triggers the change to the component tree? On which thread? Are
>>> you
>>> >> > using websockets?
>>> >> >
>>> >> > Sven
>>> >>
>>> >> In general this thread is not initialized by user action but by
>>> >> application. So yes, it can be push from a server (eg. using
>>> >> Atmosphere - this is my case) or by ajax self updating behavior.
>>> >>
>>> >> --
>>> >> DS
>>> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> > On 07/04/2014 12:13 PM, Daniel Stoch wrote:
>>> >> >>
>>> >> >> Hi all,
>>> >> >>
>>> >> >> I think such question occurs from time to time on this list, but I
>>> >> >> have never found a good answer how to solve such problem in general.
>>> >> >> The problem is similar to my last question:
>>> >> >>
>>> >> >>
>>> >>
>>> http://apache-wicket.1842946.n4.nabble.com/How-to-handle-click-on-disabled-links-ListenerInvocationNotAllowedException-td4666287.html
>>> >> >> but now there is a situation when link was removed from page (not
>>> >> >> disabled).
>>> >> >>
>>> >> >> So page was rendered in a browser, on the server component tree was
>>> >> >> changed, but user clicks a link in a browser before this changes
>>> will
>>> >> >> be pushed to it. It leads to an exception:
>>> >> >>
>>> >> >> org.apache.wicket.WicketRuntimeException: Component 'xxx' has been
>>> >> >> removed from page.
>>> >> >> at
>>> >> >>
>>> >>
>>> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:178)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.apache.wicke

Re: How to handle click on removed links - WicketRuntimeException (Component 'xxx' has been removed from page)?

Maybe you could even just push JSON to client side and generate items
content at client side which is going to be way faster


On Fri, Jul 4, 2014 at 4:06 PM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:

> Why don't you try routing all the click to a part of you application that
> is always available? E.g.
>
> 1- You have a list of items that are pushed... They are in a certain
> container that is "always" there... At client and server side
> 2- The items are pushed but instead of normal AJAX link you use link to
> the parent never changing container passing ID of item. This way click will
> never fail and it is still sort of object oriented...
>
>
>
> On Fri, Jul 4, 2014 at 3:59 PM, Daniel Stoch 
> wrote:
>
>> On Fri, Jul 4, 2014 at 3:14 PM, Martin Grigorov 
>> wrote:
>> > Hi,
>> >
>> > You can use Atmopshere to hide/disable the client side too, not just the
>> > server side.
>>
>> Of course, I already do that.
>> But user can click the link after state was changed on the server side
>> but before these changes are pushed to client browser.
>>
>> --
>> Daniel
>>
>>
>> >
>> > Martin Grigorov
>> > Wicket Training and Consulting
>> > https://twitter.com/mtgrigorov
>> >
>> >
>> > On Fri, Jul 4, 2014 at 1:46 PM, Daniel Stoch 
>> wrote:
>> >
>> >> On Fri, Jul 4, 2014 at 12:33 PM, Sven Meier  wrote:
>> >> >> So page was rendered in a browser,
>> >> >> on the server component tree was changed
>> >> >
>> >> >
>> >> > What triggers the change to the component tree? On which thread? Are
>> you
>> >> > using websockets?
>> >> >
>> >> > Sven
>> >>
>> >> In general this thread is not initialized by user action but by
>> >> application. So yes, it can be push from a server (eg. using
>> >> Atmosphere - this is my case) or by ajax self updating behavior.
>> >>
>> >> --
>> >> DS
>> >>
>> >> >
>> >> >
>> >> >
>> >> > On 07/04/2014 12:13 PM, Daniel Stoch wrote:
>> >> >>
>> >> >> Hi all,
>> >> >>
>> >> >> I think such question occurs from time to time on this list, but I
>> >> >> have never found a good answer how to solve such problem in general.
>> >> >> The problem is similar to my last question:
>> >> >>
>> >> >>
>> >>
>> http://apache-wicket.1842946.n4.nabble.com/How-to-handle-click-on-disabled-links-ListenerInvocationNotAllowedException-td4666287.html
>> >> >> but now there is a situation when link was removed from page (not
>> >> >> disabled).
>> >> >>
>> >> >> So page was rendered in a browser, on the server component tree was
>> >> >> changed, but user clicks a link in a browser before this changes
>> will
>> >> >> be pushed to it. It leads to an exception:
>> >> >>
>> >> >> org.apache.wicket.WicketRuntimeException: Component 'xxx' has been
>> >> >> removed from page.
>> >> >> at
>> >> >>
>> >>
>> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:178)
>> >> >> at
>> >> >>
>> >>
>> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
>> >> >> at
>> >> >>
>> >>
>> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
>> >> >> at
>> >> >>
>> >>
>> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
>> >> >> at
>> >> >>
>> >>
>> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
>> >> >> at
>> >> >>
>> >>
>> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
>> >> >> at
>> >> >>
>> >>
>> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
>> >> >> at
>> >> >>
>> >>
>> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
>

Re: How to handle click on removed links - WicketRuntimeException (Component 'xxx' has been removed from page)?

Why don't you try routing all the click to a part of you application that
is always available? E.g.

1- You have a list of items that are pushed... They are in a certain
container that is "always" there... At client and server side
2- The items are pushed but instead of normal AJAX link you use link to the
parent never changing container passing ID of item. This way click will
never fail and it is still sort of object oriented...



On Fri, Jul 4, 2014 at 3:59 PM, Daniel Stoch  wrote:

> On Fri, Jul 4, 2014 at 3:14 PM, Martin Grigorov 
> wrote:
> > Hi,
> >
> > You can use Atmopshere to hide/disable the client side too, not just the
> > server side.
>
> Of course, I already do that.
> But user can click the link after state was changed on the server side
> but before these changes are pushed to client browser.
>
> --
> Daniel
>
>
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
> >
> > On Fri, Jul 4, 2014 at 1:46 PM, Daniel Stoch 
> wrote:
> >
> >> On Fri, Jul 4, 2014 at 12:33 PM, Sven Meier  wrote:
> >> >> So page was rendered in a browser,
> >> >> on the server component tree was changed
> >> >
> >> >
> >> > What triggers the change to the component tree? On which thread? Are
> you
> >> > using websockets?
> >> >
> >> > Sven
> >>
> >> In general this thread is not initialized by user action but by
> >> application. So yes, it can be push from a server (eg. using
> >> Atmosphere - this is my case) or by ajax self updating behavior.
> >>
> >> --
> >> DS
> >>
> >> >
> >> >
> >> >
> >> > On 07/04/2014 12:13 PM, Daniel Stoch wrote:
> >> >>
> >> >> Hi all,
> >> >>
> >> >> I think such question occurs from time to time on this list, but I
> >> >> have never found a good answer how to solve such problem in general.
> >> >> The problem is similar to my last question:
> >> >>
> >> >>
> >>
> http://apache-wicket.1842946.n4.nabble.com/How-to-handle-click-on-disabled-links-ListenerInvocationNotAllowedException-td4666287.html
> >> >> but now there is a situation when link was removed from page (not
> >> >> disabled).
> >> >>
> >> >> So page was rendered in a browser, on the server component tree was
> >> >> changed, but user clicks a link in a browser before this changes will
> >> >> be pushed to it. It leads to an exception:
> >> >>
> >> >> org.apache.wicket.WicketRuntimeException: Component 'xxx' has been
> >> >> removed from page.
> >> >> at
> >> >>
> >>
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:178)
> >> >> at
> >> >>
> >>
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
> >> >> at
> >> >>
> >>
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
> >> >> at
> >> >>
> >>
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
> >> >> at
> >> >>
> >>
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
> >> >> at
> >> >>
> >>
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
> >> >> at
> >> >>
> >>
> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
> >> >> at
> >> >>
> >>
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
> >> >> at
> >> >>
> >>
> org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
> >> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
> >> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> >> >>
> >> >> How it should be properly handled in application? Unfortunately this
> >> >> is not a dedicated exception to catch somewhere, but a common
> >> >> WicketRuntimeException.
> >> >>
> >> >> --
> >> >> Best regards,
> >> >> Daniel
> >> >>
> >> >> -
> >> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >> >> For additional commands, e-mail: users-h...@wicket.apache.org
> >> >>
> >> >
> >> >
> >> > -
> >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >> > For additional commands, e-mail: users-h...@wicket.apache.org
> >> >
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >> For additional commands, e-mail: users-h...@wicket.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
Regards - Ernesto Reinaldo Barreiro

Re: How to handle click on removed links - WicketRuntimeException (Component 'xxx' has been removed from page)?

On Fri, Jul 4, 2014 at 3:14 PM, Martin Grigorov  wrote:
> Hi,
>
> You can use Atmopshere to hide/disable the client side too, not just the
> server side.

Of course, I already do that.
But user can click the link after state was changed on the server side
but before these changes are pushed to client browser.

--
Daniel


>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
>
> On Fri, Jul 4, 2014 at 1:46 PM, Daniel Stoch  wrote:
>
>> On Fri, Jul 4, 2014 at 12:33 PM, Sven Meier  wrote:
>> >> So page was rendered in a browser,
>> >> on the server component tree was changed
>> >
>> >
>> > What triggers the change to the component tree? On which thread? Are you
>> > using websockets?
>> >
>> > Sven
>>
>> In general this thread is not initialized by user action but by
>> application. So yes, it can be push from a server (eg. using
>> Atmosphere - this is my case) or by ajax self updating behavior.
>>
>> --
>> DS
>>
>> >
>> >
>> >
>> > On 07/04/2014 12:13 PM, Daniel Stoch wrote:
>> >>
>> >> Hi all,
>> >>
>> >> I think such question occurs from time to time on this list, but I
>> >> have never found a good answer how to solve such problem in general.
>> >> The problem is similar to my last question:
>> >>
>> >>
>> http://apache-wicket.1842946.n4.nabble.com/How-to-handle-click-on-disabled-links-ListenerInvocationNotAllowedException-td4666287.html
>> >> but now there is a situation when link was removed from page (not
>> >> disabled).
>> >>
>> >> So page was rendered in a browser, on the server component tree was
>> >> changed, but user clicks a link in a browser before this changes will
>> >> be pushed to it. It leads to an exception:
>> >>
>> >> org.apache.wicket.WicketRuntimeException: Component 'xxx' has been
>> >> removed from page.
>> >> at
>> >>
>> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:178)
>> >> at
>> >>
>> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
>> >> at
>> >>
>> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
>> >> at
>> >>
>> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
>> >> at
>> >>
>> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
>> >> at
>> >>
>> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
>> >> at
>> >>
>> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
>> >> at
>> >>
>> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
>> >> at
>> >>
>> org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
>> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
>> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>> >>
>> >> How it should be properly handled in application? Unfortunately this
>> >> is not a dedicated exception to catch somewhere, but a common
>> >> WicketRuntimeException.
>> >>
>> >> --
>> >> Best regards,
>> >> Daniel
>> >>
>> >> -
>> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> >> For additional commands, e-mail: users-h...@wicket.apache.org
>> >>
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> > For additional commands, e-mail: users-h...@wicket.apache.org
>> >
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: How to handle click on removed links - WicketRuntimeException (Component 'xxx' has been removed from page)?

2014-07-04 Thread Martin Grigorov

Hi,

You can use Atmopshere to hide/disable the client side too, not just the
server side.

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov


On Fri, Jul 4, 2014 at 1:46 PM, Daniel Stoch  wrote:

> On Fri, Jul 4, 2014 at 12:33 PM, Sven Meier  wrote:
> >> So page was rendered in a browser,
> >> on the server component tree was changed
> >
> >
> > What triggers the change to the component tree? On which thread? Are you
> > using websockets?
> >
> > Sven
>
> In general this thread is not initialized by user action but by
> application. So yes, it can be push from a server (eg. using
> Atmosphere - this is my case) or by ajax self updating behavior.
>
> --
> DS
>
> >
> >
> >
> > On 07/04/2014 12:13 PM, Daniel Stoch wrote:
> >>
> >> Hi all,
> >>
> >> I think such question occurs from time to time on this list, but I
> >> have never found a good answer how to solve such problem in general.
> >> The problem is similar to my last question:
> >>
> >>
> http://apache-wicket.1842946.n4.nabble.com/How-to-handle-click-on-disabled-links-ListenerInvocationNotAllowedException-td4666287.html
> >> but now there is a situation when link was removed from page (not
> >> disabled).
> >>
> >> So page was rendered in a browser, on the server component tree was
> >> changed, but user clicks a link in a browser before this changes will
> >> be pushed to it. It leads to an exception:
> >>
> >> org.apache.wicket.WicketRuntimeException: Component 'xxx' has been
> >> removed from page.
> >> at
> >>
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:178)
> >> at
> >>
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
> >> at
> >>
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
> >> at
> >>
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
> >> at
> >>
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
> >> at
> >>
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
> >> at
> >>
> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
> >> at
> >>
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
> >> at
> >>
> org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> >>
> >> How it should be properly handled in application? Unfortunately this
> >> is not a dedicated exception to catch somewhere, but a common
> >> WicketRuntimeException.
> >>
> >> --
> >> Best regards,
> >> Daniel
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >> For additional commands, e-mail: users-h...@wicket.apache.org
> >>
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: How to handle click on removed links - WicketRuntimeException (Component 'xxx' has been removed from page)?

I have added the appropriate information in that thread.

On Fri, Jul 4, 2014 at 12:47 PM, Ernesto Reinaldo Barreiro
 wrote:
> Sven's question goes straight to the point: do you know what is causing the
> mismacth?
>
>
> On Fri, Jul 4, 2014 at 12:44 PM, Daniel Stoch 
> wrote:
>
>> This is a popular answer on such querstions ("use veil" and so on) :).
>> But it is not the case here, because we do not know whet to block here.
>> Beside this, in general I think it is not a good solution.
>>
>> It works for me in many applications.
>
>
>> On Fri, Jul 4, 2014 at 12:30 PM, Ernesto Reinaldo Barreiro
>>  wrote:
>> > Block the UI?
>> >
>> >
>> > On Fri, Jul 4, 2014 at 12:13 PM, Daniel Stoch 
>> > wrote:
>> >
>> >> Hi all,
>> >>
>> >> I think such question occurs from time to time on this list, but I
>> >> have never found a good answer how to solve such problem in general.
>> >> The problem is similar to my last question:
>> >>
>> >>
>> http://apache-wicket.1842946.n4.nabble.com/How-to-handle-click-on-disabled-links-ListenerInvocationNotAllowedException-td4666287.html
>> >> but now there is a situation when link was removed from page (not
>> >> disabled).
>> >>
>> >> So page was rendered in a browser, on the server component tree was
>> >> changed, but user clicks a link in a browser before this changes will
>> >> be pushed to it. It leads to an exception:
>> >>
>> >> org.apache.wicket.WicketRuntimeException: Component 'xxx' has been
>> >> removed from page.
>> >> at
>> >>
>> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:178)
>> >> at
>> >>
>> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
>> >> at
>> >>
>> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
>> >> at
>> >>
>> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
>> >> at
>> >>
>> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
>> >> at
>> >>
>> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
>> >> at
>> >>
>> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
>> >> at
>> >>
>> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
>> >> at
>> >>
>> org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
>> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
>> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>> >>
>> >> How it should be properly handled in application? Unfortunately this
>> >> is not a dedicated exception to catch somewhere, but a common
>> >> WicketRuntimeException.
>> >>
>> >> --
>> >> Best regards,
>> >> Daniel
>> >>
>> >> -
>> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> >> For additional commands, e-mail: users-h...@wicket.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Regards - Ernesto Reinaldo Barreiro
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
>
> --
> Regards - Ernesto Reinaldo Barreiro

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: How to handle click on removed links - WicketRuntimeException (Component 'xxx' has been removed from page)?

Sven's question goes straight to the point: do you know what is causing the
mismacth?


On Fri, Jul 4, 2014 at 12:44 PM, Daniel Stoch 
wrote:

> This is a popular answer on such querstions ("use veil" and so on) :).
> But it is not the case here, because we do not know whet to block here.
> Beside this, in general I think it is not a good solution.
>
> It works for me in many applications.


> On Fri, Jul 4, 2014 at 12:30 PM, Ernesto Reinaldo Barreiro
>  wrote:
> > Block the UI?
> >
> >
> > On Fri, Jul 4, 2014 at 12:13 PM, Daniel Stoch 
> > wrote:
> >
> >> Hi all,
> >>
> >> I think such question occurs from time to time on this list, but I
> >> have never found a good answer how to solve such problem in general.
> >> The problem is similar to my last question:
> >>
> >>
> http://apache-wicket.1842946.n4.nabble.com/How-to-handle-click-on-disabled-links-ListenerInvocationNotAllowedException-td4666287.html
> >> but now there is a situation when link was removed from page (not
> >> disabled).
> >>
> >> So page was rendered in a browser, on the server component tree was
> >> changed, but user clicks a link in a browser before this changes will
> >> be pushed to it. It leads to an exception:
> >>
> >> org.apache.wicket.WicketRuntimeException: Component 'xxx' has been
> >> removed from page.
> >> at
> >>
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:178)
> >> at
> >>
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
> >> at
> >>
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
> >> at
> >>
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
> >> at
> >>
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
> >> at
> >>
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
> >> at
> >>
> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
> >> at
> >>
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
> >> at
> >>
> org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> >>
> >> How it should be properly handled in application? Unfortunately this
> >> is not a dedicated exception to catch somewhere, but a common
> >> WicketRuntimeException.
> >>
> >> --
> >> Best regards,
> >> Daniel
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >> For additional commands, e-mail: users-h...@wicket.apache.org
> >>
> >>
> >
> >
> > --
> > Regards - Ernesto Reinaldo Barreiro
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
Regards - Ernesto Reinaldo Barreiro

Re: How to handle click on removed links - WicketRuntimeException (Component 'xxx' has been removed from page)?

On Fri, Jul 4, 2014 at 12:33 PM, Sven Meier  wrote:
>> So page was rendered in a browser,
>> on the server component tree was changed
>
>
> What triggers the change to the component tree? On which thread? Are you
> using websockets?
>
> Sven

In general this thread is not initialized by user action but by
application. So yes, it can be push from a server (eg. using
Atmosphere - this is my case) or by ajax self updating behavior.

--
DS

>
>
>
> On 07/04/2014 12:13 PM, Daniel Stoch wrote:
>>
>> Hi all,
>>
>> I think such question occurs from time to time on this list, but I
>> have never found a good answer how to solve such problem in general.
>> The problem is similar to my last question:
>>
>> http://apache-wicket.1842946.n4.nabble.com/How-to-handle-click-on-disabled-links-ListenerInvocationNotAllowedException-td4666287.html
>> but now there is a situation when link was removed from page (not
>> disabled).
>>
>> So page was rendered in a browser, on the server component tree was
>> changed, but user clicks a link in a browser before this changes will
>> be pushed to it. It leads to an exception:
>>
>> org.apache.wicket.WicketRuntimeException: Component 'xxx' has been
>> removed from page.
>> at
>> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:178)
>> at
>> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
>> at
>> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
>> at
>> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
>> at
>> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
>> at
>> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
>> at
>> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
>> at
>> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
>> at
>> org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>
>> How it should be properly handled in application? Unfortunately this
>> is not a dedicated exception to catch somewhere, but a common
>> WicketRuntimeException.
>>
>> --
>> Best regards,
>> Daniel
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: How to handle click on removed links - WicketRuntimeException (Component 'xxx' has been removed from page)?

This is a popular answer on such querstions ("use veil" and so on) :).
But it is not the case here, because we do not know whet to block here.
Beside this, in general I think it is not a good solution.

On Fri, Jul 4, 2014 at 12:30 PM, Ernesto Reinaldo Barreiro
 wrote:
> Block the UI?
>
>
> On Fri, Jul 4, 2014 at 12:13 PM, Daniel Stoch 
> wrote:
>
>> Hi all,
>>
>> I think such question occurs from time to time on this list, but I
>> have never found a good answer how to solve such problem in general.
>> The problem is similar to my last question:
>>
>> http://apache-wicket.1842946.n4.nabble.com/How-to-handle-click-on-disabled-links-ListenerInvocationNotAllowedException-td4666287.html
>> but now there is a situation when link was removed from page (not
>> disabled).
>>
>> So page was rendered in a browser, on the server component tree was
>> changed, but user clicks a link in a browser before this changes will
>> be pushed to it. It leads to an exception:
>>
>> org.apache.wicket.WicketRuntimeException: Component 'xxx' has been
>> removed from page.
>> at
>> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:178)
>> at
>> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
>> at
>> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
>> at
>> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
>> at
>> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
>> at
>> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
>> at
>> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
>> at
>> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
>> at
>> org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>
>> How it should be properly handled in application? Unfortunately this
>> is not a dedicated exception to catch somewhere, but a common
>> WicketRuntimeException.
>>
>> --
>> Best regards,
>> Daniel
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
>
> --
> Regards - Ernesto Reinaldo Barreiro

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: How to handle click on removed links - WicketRuntimeException (Component 'xxx' has been removed from page)?

2014-07-04 Thread Sven Meier


So page was rendered in a browser,
on the server component tree was changed


What triggers the change to the component tree? On which thread? Are you using 
websockets?

Sven


On 07/04/2014 12:13 PM, Daniel Stoch wrote:

Hi all,

I think such question occurs from time to time on this list, but I
have never found a good answer how to solve such problem in general.
The problem is similar to my last question:
http://apache-wicket.1842946.n4.nabble.com/How-to-handle-click-on-disabled-links-ListenerInvocationNotAllowedException-td4666287.html
but now there is a situation when link was removed from page (not disabled).

So page was rendered in a browser, on the server component tree was
changed, but user clicks a link in a browser before this changes will
be pushed to it. It leads to an exception:

org.apache.wicket.WicketRuntimeException: Component 'xxx' has been
removed from page.
at 
org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:178)
at 
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
at 
org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
at 
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
at 
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
at 
org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
at 
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

How it should be properly handled in application? Unfortunately this
is not a dedicated exception to catch somewhere, but a common
WicketRuntimeException.

--
Best regards,
Daniel

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: How to handle click on removed links - WicketRuntimeException (Component 'xxx' has been removed from page)?

Block the UI?


On Fri, Jul 4, 2014 at 12:13 PM, Daniel Stoch 
wrote:

> Hi all,
>
> I think such question occurs from time to time on this list, but I
> have never found a good answer how to solve such problem in general.
> The problem is similar to my last question:
>
> http://apache-wicket.1842946.n4.nabble.com/How-to-handle-click-on-disabled-links-ListenerInvocationNotAllowedException-td4666287.html
> but now there is a situation when link was removed from page (not
> disabled).
>
> So page was rendered in a browser, on the server component tree was
> changed, but user clicks a link in a browser before this changes will
> be pushed to it. It leads to an exception:
>
> org.apache.wicket.WicketRuntimeException: Component 'xxx' has been
> removed from page.
> at
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:178)
> at
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
> at
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
> at
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
> at
> org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>
> How it should be properly handled in application? Unfortunately this
> is not a dedicated exception to catch somewhere, but a common
> WicketRuntimeException.
>
> --
> Best regards,
> Daniel
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
Regards - Ernesto Reinaldo Barreiro

How to handle click on removed links - WicketRuntimeException (Component 'xxx' has been removed from page)?

Hi all,

I think such question occurs from time to time on this list, but I
have never found a good answer how to solve such problem in general.
The problem is similar to my last question:
http://apache-wicket.1842946.n4.nabble.com/How-to-handle-click-on-disabled-links-ListenerInvocationNotAllowedException-td4666287.html
but now there is a situation when link was removed from page (not disabled).

So page was rendered in a browser, on the server component tree was
changed, but user clicks a link in a browser before this changes will
be pushed to it. It leads to an exception:

org.apache.wicket.WicketRuntimeException: Component 'xxx' has been
removed from page.
at 
org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:178)
at 
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
at 
org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
at 
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
at 
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
at 
org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
at 
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

How it should be properly handled in application? Unfortunately this
is not a dedicated exception to catch somewhere, but a common
WicketRuntimeException.

--
Best regards,
Daniel

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: WicketRuntimeException: Attempted to set property value on a null object

2012-12-01 Thread Sven Meier


Ah, silly Hibernate ;).

AFAICS sooner or later a Wicket component will have to write a value 
into the embedded address, so obviously it has to be there.
You can of course build a specialized model doing some magic here, but 
at the moment I don't know how that might look like.


Sven

On 12/01/2012 12:43 AM, Andrew Geery wrote:

The problem with doing that is that Hibernate detects that as a change
(a null object is not the same as an empty object) and does a database
update (see some of the comments on this:
https://issues.jboss.org/browse/HIBERNATE-50).

Andrew

On Fri, Nov 30, 2012 at 5:59 PM, Sven Meier  wrote:

d

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: WicketRuntimeException: Attempted to set property value on a null object

2012-11-30 Thread Andrew Geery

The problem with doing that is that Hibernate detects that as a change
(a null object is not the same as an empty object) and does a database
update (see some of the comments on this:
https://issues.jboss.org/browse/HIBERNATE-50).

Andrew

On Fri, Nov 30, 2012 at 5:59 PM, Sven Meier  wrote:
> d

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: WicketRuntimeException: Attempted to set property value on a null object

2012-11-30 Thread Sven Meier


Why not handle this in your domain objects already?

@Entity
public class Person {
...
  @Embedded
  private Address address;
...

  public Address getAddress() {
if (address == null) {
  address = new Address();
}

return address;
  }
}
 


Sven

On 11/30/2012 11:49 PM, Andrew Geery wrote:

I have a Person Hibernate/JPA entity with an @Embedded address object in it:

@Entity
public class Person {
...
   @Embedded
   private Address address;
...
}

I have a Panel with a Form for editing the Address
(EditAddressFormPanel) and a panel for editing the Person which uses
the Panel for editing (EditPersonFormPanel).

public class EditPersonFormPanel extends Panel {

   public EditPersonFormPanel(String cid, IModel model) {
 super(cid, model);
 // create the person form
 Form form = ...
 // add the address form panel to it
 form.add(new EditAddressFormPanel("address", new
PropertyModel(model, "address"));
 ...
   }

}

This works if the Person.address field is not null.  However, because
of the way that JPA works, the address field will be null if all of
the fields in the class are null.  For example, if a Person object was
persisted without an initial address (i.e., address = null).  When
this happens, 
org.apache.wicket.model.AbstractPropertyModel.getInnermostModelOrObject()
returns null and I ultimately get a WicketRuntimeException: Attempted
to set property value on a null object in PropertyResolver.setValue
because the object is null.

My question is how to deal this this correctly at the model level.  I
think IModel.setObject should create a new object if the incoming
object is null and IModel.getObject should return null if no fields
are set on the object to match how JPA/Hibernate handles this.

How do other people handle this problem?  Is there a good model to
extend from (maybe something like IWrapModel)?  Any examples?

Thanks
Andrew

PS I'm already using EntityModels
(http://wicketinaction.com/2008/09/building-a-smart-entitymodel/)

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

WicketRuntimeException: Attempted to set property value on a null object

2012-11-30 Thread Andrew Geery

I have a Person Hibernate/JPA entity with an @Embedded address object in it:

@Entity
public class Person {
...
  @Embedded
  private Address address;
...
}

I have a Panel with a Form for editing the Address
(EditAddressFormPanel) and a panel for editing the Person which uses
the Panel for editing (EditPersonFormPanel).

public class EditPersonFormPanel extends Panel {

  public EditPersonFormPanel(String cid, IModel model) {
super(cid, model);
// create the person form
Form form = ...
// add the address form panel to it
form.add(new EditAddressFormPanel("address", new
PropertyModel(model, "address"));
...
  }

}

This works if the Person.address field is not null.  However, because
of the way that JPA works, the address field will be null if all of
the fields in the class are null.  For example, if a Person object was
persisted without an initial address (i.e., address = null).  When
this happens, 
org.apache.wicket.model.AbstractPropertyModel.getInnermostModelOrObject()
returns null and I ultimately get a WicketRuntimeException: Attempted
to set property value on a null object in PropertyResolver.setValue
because the object is null.

My question is how to deal this this correctly at the model level.  I
think IModel.setObject should create a new object if the incoming
object is null and IModel.getObject should return null if no fields
are set on the object to match how JPA/Hibernate handles this.

How do other people handle this problem?  Is there a good model to
extend from (maybe something like IWrapModel)?  Any examples?

Thanks
Andrew

PS I'm already using EntityModels
(http://wicketinaction.com/2008/09/building-a-smart-entitymodel/)

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: WicketRuntimeException: "Submit Button ... is not enabled"

2012-10-16 Thread eugenebalt

Thanks Sven, that was it! They were clicking again while the form was still
processing.



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/WicketRuntimeException-Submit-Button-is-not-enabled-tp4651180p4653019.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: WicketRuntimeException: "Submit Button ... is not enabled"

2012-10-16 Thread Sven Meier

You're probably experiencing double clicks on your ajax buttons.
When the second request reaches the button, is is already disabled again.

Check this:
http://wicketinaction.com/2008/12/preventing-double-ajax-requests-in-3-lines-of-code/

Sven

On 10/16/2012 06:24 PM, eugenebalt wrote:

Hi,

Sorry, I have to bump thread back up again. We still have no clear idea how
to address this issue, which only happens sporadically on our production
server (and we can't reproduce it locally).

We have screens with Ajax Buttons which submit forms, but also disable/hide
these Ajax buttons. I am guessing, based on earlier answers, that sometimes,
the disable/hide happens *BEFORE* the Form Submit, and Wicket doesn't like
that. Wicket requires that all form fields be enabled and visible to ensure
form integrity.

The simplest question is, how do we turn off this check in Wicket, or how do
we guard against this error?

"Submit button is not visible" or "Submit button is enabled".

We can't rewrite our app from scratch, it has a lot of screens and a lot of
functionality, we do need to toggle these buttons when submitting the form.
Please, any help would be appreciated.

--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/WicketRuntimeException-Submit-Button-is-not-enabled-tp4651180p4653012.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: WicketRuntimeException: "Submit Button ... is not enabled"

2012-10-16 Thread eugenebalt

Hi,

Sorry, I have to bump thread back up again. We still have no clear idea how
to address this issue, which only happens sporadically on our production
server (and we can't reproduce it locally).

We have screens with Ajax Buttons which submit forms, but also disable/hide
these Ajax buttons. I am guessing, based on earlier answers, that sometimes,
the disable/hide happens *BEFORE* the Form Submit, and Wicket doesn't like
that. Wicket requires that all form fields be enabled and visible to ensure
form integrity.

The simplest question is, how do we turn off this check in Wicket, or how do
we guard against this error? 

"Submit button is not visible" or "Submit button is enabled".

We can't rewrite our app from scratch, it has a lot of screens and a lot of
functionality, we do need to toggle these buttons when submitting the form.
Please, any help would be appreciated.



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/WicketRuntimeException-Submit-Button-is-not-enabled-tp4651180p4653012.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: WicketRuntimeException: "Submit Button ... is not enabled"

2012-08-14 Thread Paul Bors

As an idea, I tend to keep the panel edit/view state as a boolean and then
toggle the label on the button and control the behavior of the button press
via an if-else statement in the onSubmit() of the button.

This helps because I only have a single Edit/Save button and I toggle from
labels to form fields on the fly controlling those components via
AjaxFallback*** implemented in a single refrechPanel() method that calls
setVisable(editMode) for all the components that are to toggle or hide.

Also you can do this to the DataTable rows when necessary similar to how the
Editable tree table works:
http://www.wicket-library.com/wicket-examples/ajax/tree/table/editable?3

I get away with all this because I have my own generic labeled form
component that can toggle from a label to a form component and have a
 html tag as well as an Help icon and feedback panel associated with
it.

~ Thank you,
  Paul Bors

-Original Message-
From: eugenebalt [mailto:eugeneb...@yahoo.com] 
Sent: Tuesday, August 14, 2012 12:16 PM
To: users@wicket.apache.org
Subject: Re: WicketRuntimeException: "Submit Button ... is not enabled"

It is true that we have multiple buttons on our form that we are
disabling/hiding selectively.

Our scenario: a panel that contains the button "Edit", and then when it's
clicked, the panel opens and "Edit" is replaced by two other visible buttons
- "Submit" and "Cancel". "Edit" is gone. We need this dynamic behavior to
enable rich, "self-changing" forms.

Example:

add(new Button ("editButton"){
  @Override
 public boolean isVisible() {
 return showeditbutton;
}
@Override
public void onSubmit() { 
  showeditbutton = false;// hide this one
  showsavebutton = true;   // show the others
  showcancelbutton = true;
}
}

These are global variables/flags on the form. 

So given this "self-changing form" requirement, what's the fastest way to
get rid of this intermittent "Not Enabled / Visible" error? Is there a way
to turn off this validation in Wicket?



--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/WicketRuntimeException-Submit-But
ton-is-not-enabled-tp4651180p4651233.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: WicketRuntimeException: "Submit Button ... is not enabled"

2012-08-14 Thread eugenebalt

It is true that we have multiple buttons on our form that we are
disabling/hiding selectively.

Our scenario: a panel that contains the button "Edit", and then when it's
clicked, the panel opens and "Edit" is replaced by two other visible buttons
- "Submit" and "Cancel". "Edit" is gone. We need this dynamic behavior to
enable rich, "self-changing" forms.

Example:

add(new Button ("editButton"){
  @Override
 public boolean isVisible() {
 return showeditbutton;
}
@Override
public void onSubmit() { 
  showeditbutton = false;// hide this one
  showsavebutton = true;   // show the others
  showcancelbutton = true;
}
}

These are global variables/flags on the form. 

So given this "self-changing form" requirement, what's the fastest way to
get rid of this intermittent "Not Enabled / Visible" error? Is there a way
to turn off this validation in Wicket?



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/WicketRuntimeException-Submit-Button-is-not-enabled-tp4651180p4651233.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: WicketRuntimeException: "Submit Button ... is not enabled"

2012-08-14 Thread Bertrand Guay-Paquet


No, they are interchangeable.

On 14/08/2012 11:42 AM, eugenebalt wrote:

Thanks a lot. In our case, we have an AjaxButton that maps to a "input
type=submit".

Would using the input type "Button" get rid of this problem?



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/WicketRuntimeException-Submit-Button-is-not-enabled-tp4651180p4651231.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: WicketRuntimeException: "Submit Button ... is not enabled"

2012-08-14 Thread eugenebalt

Thanks a lot. In our case, we have an AjaxButton that maps to a "input
type=submit".

Would using the input type "Button" get rid of this problem?



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/WicketRuntimeException-Submit-Button-is-not-enabled-tp4651180p4651231.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: WicketRuntimeException: "Submit Button ... is not enabled"

2012-08-13 Thread Bertrand Guay-Paquet


Hi,

When a form is submitted, it checks whether the submitting component is 
a Wicket component. If it is (your case), it makes sure that it's 
enabled and visible. I guess this is to prevent users manipulating with 
the form submission process. In any case, if any of the 2 conditions is 
not met, the exception is thrown.


This might or might not be caused by a race condition, but it would most 
likely be caused by disabling buttons (or their parents) in your code.


Bertrand

On 13/08/2012 10:40 AM, eugenebalt wrote:

We have an Ajax button which, when clicked, occasionally produces this
WicketRuntimeException:

  ERROR [WebContainer : 17] (RequestCycle.java:1521) - Submit Button
myPanel:editButton (path=myForm:myPanel:editButton) is not enabled
org.apache.wicket.WicketRuntimeException: Submit Button myPanel:editButton
(path=myForm:myPanel:editButton) is not enabled
 at
org.apache.wicket.markup.html.form.Form$2.component(Form.java:626)
 at
org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:878)
 at
org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:893)
 at
org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:893)
 at
org.apache.wicket.markup.html.form.Form.findSubmittingButton(Form.java:602)
 at
org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:875)
 at sun.reflect.GeneratedMethodAccessor2603.invoke(Unknown Source)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
 at java.lang.reflect.Method.invoke(Method.java:599)
 at
org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:182)
 at

Is there a race condition of some kind happening here? Thanks



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/WicketRuntimeException-Submit-Button-is-not-enabled-tp4651180.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

WicketRuntimeException: "Submit Button ... is not enabled"

2012-08-13 Thread eugenebalt

We have an Ajax button which, when clicked, occasionally produces this
WicketRuntimeException:

 ERROR [WebContainer : 17] (RequestCycle.java:1521) - Submit Button
myPanel:editButton (path=myForm:myPanel:editButton) is not enabled
org.apache.wicket.WicketRuntimeException: Submit Button myPanel:editButton
(path=myForm:myPanel:editButton) is not enabled
at
org.apache.wicket.markup.html.form.Form$2.component(Form.java:626)
at
org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:878)
at
org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:893)
at
org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:893)
at
org.apache.wicket.markup.html.form.Form.findSubmittingButton(Form.java:602)
at
org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:875)
at sun.reflect.GeneratedMethodAccessor2603.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at
org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:182)
at 

Is there a race condition of some kind happening here? Thanks



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/WicketRuntimeException-Submit-Button-is-not-enabled-tp4651180.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Cannot reproduce a WicketRuntimeException.

2011-12-19 Thread cosmindumy

Hi, I know it's off topic but I didn't want to create a separate topic for a
simple question.

I've got an error on production server and I cannot reproduce on my
development machine. The error says :
woUploadFilesContainer:calculateButton
(path=inputForm:stepTwoUploadFilesContainer:calculateButton) is not visible
org.apache.wicket.WicketRuntimeException: Submit Button
stepTwoUploadFilesContainer:calculateButton
(path=inputForm:stepTwoUploadFilesContainer:calculateButton) is not visible

Which can be the cause? The submit button is never hidden, but the container
that holds it.
Here is the button code:
calculateButton = new CalculateButton("calculateButton",
"/wos/stepTwoUploadFiles/calculate");
calculateButton.setDefaultFormProcessing(false);
add(calculateButton);

I suppose that this is the code where it enters from Form class from wicket
sources :
if (!component.isVisibleInHierarchy())
{
        throw new
WicketRuntimeException("Submit Button " +
   
submittingComponent.getInputName() + " (path=" +
   
component.getPageRelativePath() + ") is not visible");
}

Has anyone any idea? 

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Cannot-reproduce-a-WicketRuntimeException-tp4185488p4214363.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Cannot reproduce a WicketRuntimeException.

Actually it didn't work. I put setTimeout(..). to delay the hiding of loading
image but I still got the exception sometimes. 
Do you have any other ideea?

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Cannot-reproduce-a-WicketRuntimeException-tp4185488p4186479.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Cannot reproduce a WicketRuntimeException.

I put a setTimeout(..). I hope this will solve the problem. I didn't get this
error after puting setTimeout().
Thanks for your response.

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Cannot-reproduce-a-WicketRuntimeException-tp4185488p4186446.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Cannot reproduce a WicketRuntimeException.

Thanks for your idea. 
I manages to reproduce the error. It happens extremely rare. Here is the
situation. 
I have a AjaxSubmitLink that make an action. To prevent multiple submit, I
use a AjaxCallDecorate that calls a javascript that shows a loading image
over the whole form, so that the form is inaccessible. After the submit is
finished, on decorateOnSucces or decorateOnFailure the image is again hidden
and the form is again available. 
I think that the problem is when the user click on the link right after the
form is available again but the ajaxsubmitlink is not yet updated. 
How can I tell to javascript to wait just a little more before it hides
again the loading image? 
I hope is clear what I said.



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Cannot-reproduce-a-WicketRuntimeException-tp4185488p4186262.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Cannot reproduce a WicketRuntimeException.

I'm afraid I didn't understand what exactly do you mean. 
How can I reproduce this in the development machine? This doesn't happened
again. What should I update on client side?

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Cannot-reproduce-a-WicketRuntimeException-tp4185488p4185720.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Cannot reproduce a WicketRuntimeException.

2011-12-12 Thread Martin Grigorov

Hi,

The problem is that you have a stale link.
Initially you rendered this repeater and then you updated it in the
server side (the items inside have new ids) and you forgot to update
it in at the client side. Then the user clicks such stale link and the
server side cannot find an item with id == 0.

On Mon, Dec 12, 2011 at 11:37 AM, cosmindumy  wrote:
> On the production server I received an exception. The problem is that I
> cannot reproduce and I coudn't find the cause.
> Probably it must be something with browser setting, but I'm not sure.
> Has anyone an ideea which can be the cause? It says that the component is
> not found, but the component is there.
> This is some part of stack trace:
>
>
> org.apache.wicket.protocol.http.request.InvalidUrlException:
> org.apache.wicket.WicketRuntimeException: component
> inputForm:editQuoteContainer:rowPanel:repeater:1:addCombination not found on
> page
> com.lingo24.orderingsystem.customer.web.wicket.wos.estimator.EditQuoteDetails[id
> = 1], listener interface = [RequestListenerInterface
> name=IActivePageBehaviorListener, method=public abstract void
> org.apache.wicket.behavior.IBehaviorListener.onRequest()]
> at
> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:262)
> ..
> ..
> ..Caused by: org.apache.wicket.WicketRuntimeException: component
> inputForm:editQuoteContainer:rowPanel:repeater:1:addCombination not found on
> page
> com.lingo24.orderingsystem.customer.web.wicket.wos.estimator.EditQuoteDetails[id
> = 1], listener interface = [RequestListenerInterface
> name=IActivePageBehaviorListener, method=public abstract void
> org.apache.wicket.behavior.IBehaviorListener.onRequest()]
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/Cannot-reproduce-a-WicketRuntimeException-tp4185488p4185488.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Cannot reproduce a WicketRuntimeException.