On Sat, Nov 5, 2011 at 6:50 AM, wrote:
> Hi,
>
> To abort the construction of the page, you throw
> ResetResponseException or subclasses.
Yes,
RestartResponseException should be used instead of setResponsePage()
>
> Regards,
>
> Bernard
>
>
> On Fri, 4 Nov 2011 19:12:34 -0700 (PDT), you wrote:
Beautiful, thank you.
George
On Nov 5, 2011, at 12:46 AM, bht [via Apache Wicket] wrote:
> Hi,
>
> To abort the construction of the page, you throw
> ResetResponseException or subclasses.
>
> Regards,
>
> Bernard
>
>
> On Fri, 4 Nov 2011 19:12:34 -0700 (PDT), you wrote:
>
> >Hi,
> >
Hello,
I am trying to migrate from 1.4.18 to 1.5.2. I followed the suggestions on
https://cwiki.apache.org/WICKET/migration-to-wicket-15.html
I have a Wicket application with 6 tabs. After starting the server and a
browser-instance, I get:
[ WARN] 2011-11-05 17:00:26
org.apache.wicket.request.han
See https://issues.apache.org/jira/browse/WICKET-4163 for your first issue.
You can ignore it (it's harmless) or use the workaround until 1.5.3 is
released.
Your second issue rings a bell (maybe other people reported this recently).
It could also be related to
https://issues.apache.org/jira/br
I´m also having issues with
org.apache.wicket.request.handler.ComponentNotFoundException and
current 1.5.x trunk... I did not stop to look carefully at them yet.
Regards,
Ernesto
On Sat, Nov 5, 2011 at 5:28 PM, Bas Gooren wrote:
> See https://issues.apache.org/jira/browse/WICKET-4163 for your f
I think in my case WICKET-4197 was causing the problem.
Ernesto
On Sat, Nov 5, 2011 at 5:34 PM, Ernesto Reinaldo Barreiro
wrote:
> I´m also having issues with
> org.apache.wicket.request.handler.ComponentNotFoundException and
> current 1.5.x trunk... I did not stop to look carefully at them yet.
fixed. see wicket-4200
-igor
On Fri, Nov 4, 2011 at 10:59 PM, David Berkman wrote:
> Not sure why, but, in 1.5.2 (at least), the call order is such that
> prependJavascript is not called on AjaxRequestTarget until after
> constructResponseBody() has passed...
>
>
>
>
4197 only affects pages that are accessed once a session timed out. in
1.5.2 instead of always throwing a stale page exception wicket tries
to recreate the stale page if it was bookmarkable.
-igor
On Sat, Nov 5, 2011 at 12:30 PM, Ernesto Reinaldo Barreiro
wrote:
> I think in my case WICKET-4197
I'm sorry, but my initial question was how to debug my migrated application.
No matter what I do - for example I commented vast amounts of code, to
reduce the scope of the problem - nothing works. One click:
[ERROR] 2011-11-05 20:07:10 org.apache.wicket.request.cycle.RequestCycle:314
- Error
OK. I pulled the latest Snapshot, which is also broken in its own way
(prepended scripts are included as but still don't get
run). S, when is 1.5.3 due out, and is there a workaround, maybe via a
Listener, that would substitute for now?
David
-Original Message-
From: Igor Vaynberg [ma
there is a change in wicket-ajax.js which should run those changes. i
tried them in a quickstart and it worked...
-igor
On Sat, Nov 5, 2011 at 4:29 PM, David Berkman wrote:
> OK. I pulled the latest Snapshot, which is also broken in its own way
> (prepended scripts are included as but still do
On Sat, Nov 5, 2011 at 4:23 PM, hfriederichs wrote:
> I'm sorry, but my initial question was how to debug my migrated
> application.
>
> No matter what I do - for example I commented vast amounts of code, to
> reduce the scope of the problem - nothing works.
Can you go the opposite direction -
12 matches
Mail list logo
