tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Hatcher <e...@ehatchersolutions.com>
Subject Re: 3.0 to 3.1 transition
Date Wed, 30 Mar 2005 18:34:56 GMT
On Mar 30, 2005, at 12:50 PM, Howard Lewis Ship wrote:
> Although the release number (3.1? 4.0?) is still up in the air, I've
> made some changes to ease the transition from 3.0 to 3.1.
> IRequestCycle.getRequestContext() is back.
> RequestContext is back in a more limited form (all the stuff about
> cookies and parameters is gone, it's just a wrapper for access ot
> HttpSession, HttpServletRequest and HttpServletResponse).

Is there an issue with bringing it all back?

> AbstractComponent.getSpecification() and 
> AbstractComponent.getMessages()
> are concrete again, meaning that BaseComponent and BasePage (and
> subclasses thereof) don't have to be abstract unless they define
> abstract methods (in  other words, back to 3.0 status quo).


Now if we can just do away with the abstract silliness altogether I'll 
be ecstatic!


To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org

View raw message