Hey Cosmin,

You are right, this would be the name of the event, not the name of 
the event handler method. But, in the absence of the @HandlesEvent
annotation, the default is that the name of the method == name of event.
I only tend to use @HandlesEvent in the rare cases where the name of
the method is not suitable as the name of the event.

Indeed, this should be on the main website. There was a discussion
on the mailing list:

http://www.nabble.com/Another-quick-poll-to17326251.html

and a JIRA issue:

http://www.stripesframework.org/jira/browse/STS-568

But, yeah, that's not a replacement for documenting it on the main
Stripes website. Updating the docs for Stripes 1.5 is a "work in progress".

Cheers,
Freddy
http://www.stripesbook.com

- Hey Freddy,
- 
- Thanks for the prompt response. This seems like a lot better idea. Too 
- bad it isn't documented on the stripesframework.org website (or at least 
- I couldn't find it anywhere). So I am guessing that this event name will 
- actually translate in the method name and not the name of the event to 
- handle?
- I was expecting that the method marked with @HandlesEvent("execute") to 
- be the one correlated with <s:hidden name="_eventName" value="execute"/>
- rather than the method called execute.
- 
- Thanks again,
- Cosmin



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users

Reply via email to