Hi Mike,
Event names are deduced either from the declared methods which return a
Resolution or from the HandlesEvent annotation, so I suppose Mick could do this
as well:
@HandlesEvent("save")
@HandlesEvent("update")
@HandlesEvent("delete")
@DefaultHandler
public Resolution defaultHandler() {
String event = context.getEventName();
}
otherwise how would Stripes know which parameter name was an 'event' and not a
simple property of the ActionBean?
Cheers,
DaveMark
From: Mike McNally <emmecin...@...>
Subject: Re: ActionBeanConext.getEventName() does not return the correct event
when called from the default handler
Newsgroups: gmane.comp.java.stripes.user
Date: 2010-01-08 15:07:42 GMT (1 hour and 3 minutes ago)
Yes, but the question still stands: why is it that the
ActionBeanContext doesn't make available the event name as requested
by the client, instead of (or in addition to) the effective event name
determined by the framework?
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
