Its working if i add the token as last input component it works as
expected. I wrote a few words [1] for the token usage.

[1] http://wiki.apache.org/shale/Token

On 11/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi

I second that (Should still be on a wiki page too)

Hermod

-----Original Message-----
From: Torsten Krah [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 07, 2006 12:35 PM
To: user@shale.apache.org
Subject: RE: Problem with Shale Token


This would be sufficient but i would like to see it in the tlddoc too.

Torsten

Am Dienstag, den 07.11.2006, 06:29 -0500 schrieb
[EMAIL PROTECTED]:
> Er, that's not javadoc - that's comments inside the method. If this was moved 
to
> the javadoc it would be sufficient IMHO.
>
>
> Quoting [EMAIL PROTECTED]:
>
> > Hi
> >
> > It does if you read the javadoc for org.apache.shale.component.Token in the
> > validate method:
> >     /**
> >      * <p>Perform superclass validations, then ensure that the specified
> > input
> >      * value is acceptable at this point in time.</p>
> >      *
> >      * @param context <code>FacesContext</code> for the current request
> >      */
> >     public void validate(FacesContext context) {
> >
> >         // If any of the other input components in this form triggered
> >         // validation errors, we do NOT want to validate the token component
> >         // here, because that would erase the saved token and prevent the
> >         // subsequent valid resubmit from succeeding.
> >         //
> >         // WARNING - for this test to be successful, the token component 
must
> >         // be the last input component child of the parent form to be
> >         // processed
> >         if (context.getMaximumSeverity() != null) {
> > .....
> >
> > I think that maybe the wiki should mention this also though.
> >
> >
> > Hermod
> >
> >
> >
> > -----Original Message-----
> > From: Torsten Krah [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, November 07, 2006 10:47 AM
> > To: user@shale.apache.org
> > Subject: Re: Problem with Shale Token
> >
> >
> > Ok its working.
> >
> > I did not know until now - that it have to be the last component - i put
> > it everytime in the front, now it works - the documentation should maybe
> > tell that.
> >
> > Torsten
> >
> > Am Montag, den 06.11.2006, 23:49 -0800 schrieb Craig McClanahan:
> > > On 11/6/06, Torsten Krah <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Token is broken for myfaces greater than 1.1.1.
> > > >
> > > > Look there: http://issues.apache.org/struts/browse/SHALE-287
> > > >
> > > > Torsten
> > > >
> > > > Am Montag, den 06.11.2006, 13:52 +0200 schrieb Adrian Mitev:
> > > > > Hi all! I have problem using s:token.
> > > > > I have form with input fields and required="true". When i leave the
> > > > > field empty, the page is redisplayed with error message. Then i fill
> > > > > the field with some text and click on the submit button. There i get
> > > > > error message from the token component. Any suggestions?
> > > > >
> > >
> > >
> > > OK, I have done a bunch of further investigation of this problem, 
including
> > > a new test app (built against MyFaces 1.1.4 and the current trunk code of
> > > Shale, equivalent to the 20061107 nightly build).  As far as I can tell,
> > the
> > > current code works correctly.  I've attached the current version of the
> > test
> > > application (shale-test-core.war) to the relevant bug report[1].  PLEASE 
do
> > > everything you can to cause this app to misbehave with regards to token
> > > processing, so we can shake out any remaining problems.  But, I assert, 
the
> > > problems with the token component in the Shale 1.0.3 release have been
> > > repaired.  If there are positive reports of lack of ability to break the
> > > test app, or no comment at all for a few days, I'm going to close this
> > issue
> > > as having been fixed.
> > >
> > > Craig
> > >
> > > [1] http://issues.apache.org/struts/browse/SHALE-287
> >
> >
> > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> >
> > This email with attachments is solely for the use of the individual or
> > entity to whom it is addressed. Please also be aware that DnB NOR cannot
> > accept any payment orders or other legally binding correspondence with
> > customers as a part of an email.
> >
> > This email message has been virus checked by the anti virus programs used
> > in the DnB NOR Group.
> >
> > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> >
> >



--
Seeing is believing

Reply via email to