Hi Johan,
While I was extracting the form tag from the markup, I found the cause
of the problem. The form was inside another form (with the opening tag
far above, which is why I did not noticed it). The outside form had no
wicket id nor even an action tag, and I suppose it had been put there at
Can you give me the complete form tag thats in the html?johanOn 10/11/06, Pierre-Yves Saumont <[EMAIL PROTECTED]
> wrote:No ideas or further experiments to try to solve this issue ? ;-)
Pierre-YvesPierre-Yves Saumont a écrit :> Here is the request parameter object:>> [RequestParameters> parameters=
No ideas or further experiments to try to solve this issue ? ;-)
Pierre-Yves
Pierre-Yves Saumont a écrit :
> Here is the request parameter object:
>
> [RequestParameters
> parameters={rightColumn_pagePanel_dialogBoxExpiries_tabs_panel_dialogBoxContent_selectExpiriesForm:hf:0=,
>
> submit-butt
Here is the request parameter object:
[RequestParameters
parameters={rightColumn_pagePanel_dialogBoxExpiries_tabs_panel_dialogBoxContent_selectExpiriesForm:hf:0=,
submit-button=[[ button text ]]} onlyProcessIfPathActive=false]
Inside it, all values are null, false or 0, except the parameters m
You can set a break point at the beginning of
DefaultRequestTargetResolverStrategy#resolve and see where it returns.
In your debugger, you can also look at the RequestParameters object to
find out how Wicket interprets the request.
Eelco
On 10/10/06, Pierre-Yves Saumont <[EMAIL PROTECTED]> wrote
I am not sure I understand what you mean. (To be honest, I am sure I
don't). From the debugger, how can I find the answer to this question?
Pierre-Yves
Eelco Hillenius a écrit :
> So, where does it resolve to then (what is the request target it
> thinks it has to execute)?
>
> Eelco
>
>
> On
So, where does it resolve to then (what is the request target it
thinks it has to execute)?
Eelco
On 10/10/06, Pierre-Yves Saumont <[EMAIL PROTECTED]> wrote:
> I put breakpoints on Form#onFormSubmitted and
> AbstractCompoundRequestCycleProcessor#resolve. Those breakpoint are
> reached for other
I put breakpoints on Form#onFormSubmitted and
AbstractCompoundRequestCycleProcessor#resolve. Those breakpoint are
reached for other forms that I navigate through to reach the page that
is causing trouble. In the form that has the problem,
AbstractCompoundRequestCycleProcessor#resolve is reached
That's pretty weird yes. Can you confirm the action attribute of the
form element is generated correctly? Do you have any validation
errors? You could set a break point in Form#onFormSubmitted and see
whether the request arrives there at all. If it doesn't, somehow the
call back doesn't work (the a
orge.net
> Cc:
> Subject: Re: [Wicket-user] onSubmit not called in a form
>
> I am testing this on a stripped down version of my app. The java code is:
>
> class SelectExpiriesForm extends Form {
>public SelectExpiriesForm(String id, IModel model) {
> super(id,
: Tue 10-10-2006 10:25
To: wicket-user@lists.sourceforge.net
Cc:
Subject:Re: [Wicket-user] onSubmit not called in a form
I am testing this on a stripped down version of my app. The java code is:
class SelectExpiriesForm extends Form {
public SelectExpiriesForm(String id, IModel
>
> -Original Message-
> From: [EMAIL PROTECTED] on behalf of Pierre-Yves Saumont
> Sent: Mon 09-10-2006 17:18
> To: wicket-user@lists.sourceforge.net
> Cc:
> Subject: [Wicket-user] onSubmit not called in a form
>
> Hi,
>
> I have a form and on a page
PROTECTED] on behalf of Pierre-Yves Saumont
Sent: Mon 09-10-2006 17:18
To: wicket-user@lists.sourceforge.net
Cc:
Subject:[Wicket-user] onSubmit not called in a form
Hi,
I have a form and on a page and I believe a click on the submit button
should cause a call to the onSubmit
Well, it's a bit tricky without seeing code! Maybe take a look at
http://www.wicket-library.com/wicket-examples/compref?wicket:bookmarkablePage=:wicket.examples.compref.FormPage
and compare?
/Gwyn
On 09/10/06, Pierre-Yves Saumont <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a form and on a page a
Hi,
I have a form and on a page and I believe a click on the submit button
should cause a call to the onSubmit method. (No onSubmit in the button,
all default settings). By default, I suppose after the call to onSubmit
Wicket should redisplay the same page. Instead of this, onSubmit is not
cal
15 matches
Mail list logo