Hi
I've possibly encountered an issue with the
AjaxSelfUpdatingTimerBehavior. Suddently Ajax stops working, a browser
refresh fixes the problem. If you need more details please tell.
Snip from code:
webMarkupContainer.add(new
AjaxSelfUpdatingTimerBehavior(Duration
Forgot to show that I of course did set these:
webMarkupContainer.setOutputMarkupId(true);
webMarkupContainer.setOutputMarkupPlaceholderTag(true);
2010/10/1 nino martinez wael :
> Hi
>
> I've possibly encountered an issue with the
> AjaxSelfUpdatingTimerBehavior.
ticket please
+ quckstart ;-)
On Fri, Oct 1, 2010 at 11:59 AM, nino martinez wael <
nino.martinez.w...@gmail.com> wrote:
> Forgot to show that I of course did set these:
>
>webMarkupContainer.setOutputMarkupId(true);
>webMarkupContainer.setOutputMarkupPlaceholderT
Im trying to reproduce atm, but so far not having any luck with a
clean archetype.. I'll dig some more into it monday..
2010/10/1 Martin Grigorov :
> ticket please
> + quckstart ;-)
>
> On Fri, Oct 1, 2010 at 11:59 AM, nino martinez wael <
> nino.martinez.w...@gmail.com> wrote:
>
>> Forgot to sho
Dug some deeper, and it turns out that there was something different
that threw an exception causing problems..
I guess it would be nice if the user was somehow alerted that he had a
broken session somehow, but cant figure out if it's wickets
responsibility or the applications..
-Nino
2010/10/2
Hi Nino,
If there is an error then Wicket will show either the configured
InternalErrorPage in DEPLOYMENT mode or the developer friendly page with the
details for the error. This is valid for both Ajax and non-Ajax requests.
If this is not the case then please create a ticket.
On Tue, Oct 5, 2010
ticket with quickstart :
https://issues.apache.org/jira/browse/WICKET-3101
2010/10/5 Martin Grigorov
> Hi Nino,
>
> If there is an error then Wicket will show either the configured
> InternalErrorPage in DEPLOYMENT mode or the developer friendly page with
> the
> details for the error. This is
