You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Robert Zeigler <rd...@artsci.wustl.edu> on 2010/04/21 22:42:56 UTC
EventContext interface change from 5.1 to 5.2
EventContext.java:
/**
* Extracts the value of each context value as a string.
*
* @return context values
* @since 5.2.0
*/
String[] toStrings();
Do we really want to add this method to the EventContext interface? Or
would it, perhaps, be better to have an EventContext2 interface? It's
not a huge deal, except that I was annoyed when I just upgraded a
project from 5.1 to 5.2.0-SNAPSHOT and my project ceased compiling. I
don't think it's /that/ uncommon to provide a custom implementation of
EventContext. It would be nice if people can upgrade from 5.1 to 5.2
and still be able to at least compile their project. Deprecation
warnings are acceptable, but flat out not compiling? :)
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: EventContext interface change from 5.1 to 5.2
Posted by Robert Zeigler <ro...@scazdl.org>.
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 <hlship@gmail.com
> > 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: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: EventContext interface change from 5.1 to 5.2
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Thu, 22 Apr 2010 05:53:33 -0300, Howard Lewis Ship <hl...@gmail.com>
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: EventContext interface change from 5.1 to 5.2
Posted by Howard Lewis Ship <hl...@gmail.com>.
Good point ... I had placed EventContext is that category of
interfaces "consumed but not implemented", but must have been wrong.
On Wed, Apr 21, 2010 at 1:42 PM, Robert Zeigler
<rd...@artsci.wustl.edu> wrote:
> EventContext.java:
> /**
> * Extracts the value of each context value as a string.
> *
> * @return context values
> * @since 5.2.0
> */
> String[] toStrings();
>
> Do we really want to add this method to the EventContext interface? Or would
> it, perhaps, be better to have an EventContext2 interface? It's not a huge
> deal, except that I was annoyed when I just upgraded a project from 5.1 to
> 5.2.0-SNAPSHOT and my project ceased compiling. I don't think it's /that/
> uncommon to provide a custom implementation of EventContext. It would be
> nice if people can upgrade from 5.1 to 5.2 and still be able to at least
> compile their project. Deprecation warnings are acceptable, but flat out
> not compiling? :)
>
> Robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org