http://wicket.apache.org/quickstart.html
On 11/3/07, Chris Colman <[EMAIL PROTECTED]> wrote:
> Is there a page with guidelines on making a wicket quickstart?
>
> > why dont you submit a quickstart and then we can figure out why its
> > happening
> >
> > -igor
> >
> >
> > On 11/2/07, Chris Colman <
Is there a page with guidelines on making a wicket quickstart?
> why dont you submit a quickstart and then we can figure out why its
> happening
>
> -igor
>
>
> On 11/2/07, Chris Colman <[EMAIL PROTECTED]> wrote:
> > Could it be because the form page is bookmarkable?
> >
> > > thats odd, all th
Ok, I'll do that. The problem probably won't happen in the quickstart
form ;)
>
> why dont you submit a quickstart and then we can figure out why its
> happening
>
> -igor
>
>
> On 11/2/07, Chris Colman <[EMAIL PROTECTED]> wrote:
> > Could it be because the form page is bookmarkable?
> >
> > >
why dont you submit a quickstart and then we can figure out why its happening
-igor
On 11/2/07, Chris Colman <[EMAIL PROTECTED]> wrote:
> Could it be because the form page is bookmarkable?
>
> > thats odd, all the values should be preserved, thats our rawinput that
> > all formcomponents have. D
Could it be because the form page is bookmarkable?
> thats odd, all the values should be preserved, thats our rawinput that
> all formcomponents have. Do you have a repeater/listview around your
> formcomponents.
>
> On 11/1/07, Chris Colman <[EMAIL PROTECTED]> wrote:
> > I've created a form and
> what servlet container are you using? i think this problem popped up
> on weblogic before and was due to a combination of a weblogic bug and
> the particular servlet mapping that was used.
Tomcat 5.5.20
>
> does the behavior happen to all form components or just some
> particular one?
All com
what servlet container are you using? i think this problem popped up
on weblogic before and was due to a combination of a weblogic bug and
the particular servlet mapping that was used.
does the behavior happen to all form components or just some
particular one? try it without that funky onerror()
> can you make sure your servlet mapping is of form /foo/*
>
> -igor
Yes it's of that form.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Fri, 02 Nov 2007, Chris Colman wrote:
> private String captchaInput = new String("fred");
private String captchaInput = "fred";
> public final void onError()
> {
> super.onError();
>
> // update model fields so the user doesn
can you make sure your servlet mapping is of form /foo/*
-igor
On 11/1/07, Chris Colman <[EMAIL PROTECTED]> wrote:
> > i dont know what goes wrong then for you because if i test this:
> >
> > http://wicketstuff.org/wicket12/forminput/
> >
> > that that works fine. If you make a validation error
> i dont know what goes wrong then for you because if i test this:
>
> http://wicketstuff.org/wicket12/forminput/
>
> that that works fine. If you make a validation error on 1 the rest
keep
> there values.
The only difference I can see so far is that my form page is an
'extended' page where th
i dont know what goes wrong then for you because if i test this:
http://wicketstuff.org/wicket12/forminput/
that that works fine. If you make a validation error on 1 the rest keep
there values.
On 11/1/07, Chris Colman <[EMAIL PROTECTED]> wrote:
>
> Oh yeah, I'm using Wicket 1.2.6 if that ha
Oh yeah, I'm using Wicket 1.2.6 if that has any bearing on the
situation.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> thats odd, all the values should be preserved, thats our rawinput that
> all formcomponents have. Do you have a repeater/listview around your
> formcomponents.
>
Hmmm, I don't know why my form doesn't preserve it. Here's the source of
the form. Can you spot anything that I'm doing wrong?
// -[
thats odd, all the values should be preserved, thats our rawinput that
all formcomponents have. Do you have a repeater/listview around your
formcomponents.
On 11/1/07, Chris Colman <[EMAIL PROTECTED]> wrote:
> I've created a form and set up some validators on various fields. When
> there is an err
I've created a form and set up some validators on various fields. When
there is an error and the page is redisplayed showing the errors none of
the previous values that the user typed in are there.
Is there an easy way to preserve the values already entered by the user?
I tried overriding onError
16 matches
Mail list logo