> 2) Normally, what I do in these situations, is to encapsulate the
> events with a custom event. That hides the details of component from
> users of the component, so even if, eg, form component events change,
> or if I change the guts of the component to operate differently, I can
> still keep that "public" contract via the custom event.
I like this solution. Implemented it with custom events and everything works
:-) Thanks for the pointer!
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
