Eg: I created a version of "InPlaceEditor" that allows the user of the
component to specify arbitrary additional context. What this means,
however, is that I don't know the exact method signature for the event
handler, so instead I accept an EventContext. The value from the
editor is placed into the request via a request parameter, and my
component triggers a new event with the original context + value.
This is easily accomplished by wrapping the original context and
delegating to it for everything but the parameter for value. Maybe
there's a better way to do this now... the code is a year old. But
anybody upgrading is going to be upgraded with "old" code and "old"
paradigms... I'm just trying to keep us honest about our claims to
increased backwards compatibility between tapestry versions. :)
Robert
On Apr 22, 2010, at 4/227:37 AM , Thiago H. de Paula Figueiredo wrote:
On Thu, 22 Apr 2010 05:53:33 -0300, Howard Lewis Ship <[email protected]
> wrote:
Good point ... I had placed EventContext is that category of
interfaces "consumed but not implemented", but must have been wrong.
Robert, why exactly have you implemented EventContext?
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant,
developer, and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
