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 <[email protected]> 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: [email protected] > For additional commands, e-mail: [email protected] > > -- 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: [email protected] For additional commands, e-mail: [email protected]
