If we want to access the event source, then it should be accessible through context.
But honestly I'm wondering if there is a use case for accessing event source. On Wed, Jul 20, 2011 at 9:00 AM, Taha Hafeez <tawus.tapes...@gmail.com>wrote: > Hi Thiago !! > > As you had reported the issue, do you find the below mentioned > solution to be something we can work on > > regards > Taha > > On Tue, Jul 12, 2011 at 5:06 AM, Taha Hafeez <tawus.tapes...@gmail.com> > wrote: > > Hi > > I was looking at https://issues.apache.org/jira/browse/TAP5-146 and had > an > > idea. What if you could push a service (say EventContext, or some other > name > > as it is already in use) onto the environment which contains the > component > > triggering the action. This can easily be done > > in ComponentEventRequestHandlerImpl and AjaxComponentEventRequestHandler. > So > > we would be able to do something like > > @Environmental > > private EventContext context; > > void onMyEvent() > > { > > context.getSource() ... > > } > > regards > > Taha > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Best regards, Igor Drobiazko http://tapestry5.de
