Thanks.
One more thing, i noticed that the fix now forces the event listener method
to return a StreamResponse. If not a ClassCastException is thrown.
Shouldn't the component treat the same cases of return types from event
listener methods as Tapestry does ? In my current usecase for example i want
to return an embedded component but i can't do that using the OnEvent
component.

On Tue, Dec 9, 2008 at 2:47 PM, Sven Homburg <[EMAIL PROTECTED]>wrote:

> done! named 5.0.18-SNAPSHOT but compiled against Tapestry 5.0.17
>
> 2008/12/9 Hugo Palma <[EMAIL PROTECTED]>
>
> > Can you guys upload a SNAPSHOT release or something with this fix ?
> >
> > On Mon, Dec 1, 2008 at 9:31 PM, Sven Homburg <[EMAIL PROTECTED]
> > >wrote:
> >
> > > changes submitted into trunk
> > >
> > > 2008/12/1 Harald Geritzer <[EMAIL PROTECTED]>
> > >
> > > >
> > > > seems t5components/onEvent changed its behaviour and always sends
> back
> > > the
> > > > field's value as repsonse. is there a way to get the old behaviour
> > back?
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
> > > --
> > > with regards
> > > Sven Homburg
> > > http://www.chenillekit.org
> > > http://tapestry5-components.googlecode.com
> > >
> >
>
>
>
> --
> with regards
> Sven Homburg
> http://www.chenillekit.org
> http://tapestry5-components.googlecode.com
>

Reply via email to