Hi, there,
I have the following composition:
WebPage ...
... DataView CustomProvider extends SortableDataProvider
... PagingNavigator DataView
The ERROR? I found is this:
When clicking on any of the navigation buttons (PagingNavigator), my
CustomProvider implementation is managed by Wicket
digital signature, and in case OK
it should navigate to Page3.. but not. Internally it also does a
setResponse(Page3)... but after the constructor endes, nothing
happens... it executes and renders, and the flow dies at Page2.
Any idea what can be wrong here?
Dankeschen!
Manu
you shouldnt be calling setresponsepage inside constructors
try RestartResponseException
Yes, RestartResponseException forced it to response fine.
Anyway, it's a shame setResponse sometimes fails in constructors, I
already have other web-flows working fine with it. That's because I
have some
available, and I cannot think of a good end-user reason why this
couldn't be called. The getMarkupId method can in fact be called in
if it is possible to make every method work at constructor, of course
this is not necessary.
It's a good idea to shield people from errors that aren't
Dear Sirs,
The scenario is the following:
- Page1 Form1 (innerClass) input1(String)... inputN(String)
- Page2 Link/Button (whatever for going back to Page1 - has a reference
object of Page1)
...
- PageN Link/Button (idem)
It happens that, when flowing-back from Page2, or... PageN, to
all models have
been updated with proper values - and then navigate to page2.
-igor
On 4/24/07, manu [EMAIL PROTECTED] wrote:
Dear Sirs,
The scenario is the following:
- Page1 Form1 (innerClass) input1(String)... inputN(String)
- Page2 Link/Button (whatever for going back to Page1
Dear people,
I have found the following strange behavior in wicket-1.2.6:
Since long time ago I've been using wicket-1.2.5, and testing a
webPage where there's an applet with the following codebase:
param name=codebase value=lib /
Yesterday, I decided to update to wicket-1.2.6, and then, while
Dear Sirs,
I updated to Wicket 1.2.6 and I have found the following behavior when
using BookmarkablePageLink (which was not happening before in Wicket
1.2.5). The code example is:
private class Link1 extends BookmarkablePageLink {
private static final long serialVersionUID = 1L;
Hi, Sirs,
I have the following webPages variableFlow:
Flow1: Page1 Page2 Page3 Page4 Page5 Page6
Flow2: Page1 Page3 Page4 Page6
As expressed in this flows, sometimes, depending on internal
conditions, Page1 flows directly to Page3, jumping over Page2, and so
it happens with Page4 to