This is how Trigger component is implemented. The original intention was to provide a way to trigger events e.g. for rendering of JavaScript using JavaScriptSupport service.
What is your use case? Maybe there is another way to do it? On Tue, Jun 21, 2011 at 2:47 PM, Matias Blasi <matias.bl...@gmail.com>wrote: > Thanks Igor! > > Is this a "Trigger Component API" limitation or there is any technical > limitation I am missing? > If it is a API issue, it should be great to have a context parameter into > the Trigger component, do you? > > Regards, > MatÃas. > > > >> Nope, it's not possible. An event *triggered* by *Trigger* > *component*may only >> > have MarkupWriter as *context* >> > > >> On Tue, Jun 21, 2011 at 12:46 AM, Matias Blasi <mati...@gmail.com > >wrote: > > Hi all! > > I am using the *trigger* *component* to fire an event. Is there any way to > pass a *context* for that event? As far as I understand, the *trigger* * > component* should have a '*context*' parameter, is that correct? > > Regards, Matias. > -- Best regards, Igor Drobiazko http://tapestry5.de
