On Wed, Apr 8, 2009 at 1:44 PM, Newman, John W <[email protected]> wrote:
> The source of the event name has always caused a bit of confusion for me -
> the backend code around this was cleaned up recently, but IMO this,
>
> * <p>
> * Failing that, search for a parameter in the request whose name
> matches one of the named
> * events handled by the ActionBean. For example, if the ActionBean can
> handle events foo and
> * bar, this method will scan the request for foo=somevalue and
> bar=somevalue. If it finds a
> * request parameter with a matching name it will return that name. If
> there are multiple
> * matching names, the result of this method cannot be guaranteed and a
> * {...@link StripesRuntimeException} will be thrown.
> * </p>
>
> should not exist anymore..
>
That's just a case of comments not keeping up with code changes. As of
Stripes 1.5, the _eventName parameter overrides everything else, even if
there otherwise would be multiple events indicated.
Don't forget about the enter key =) also prototype.js needed a patch to get
> submits into form.serialize()...
>
>
As of Prototype 1.6 (maybe 1.5?), you can specify in your Ajax.Updater or
Ajax.Request options { submit: "theEventName" } to specify which submit
button to include when serializing the form.
-Ben
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
