I was given to understand that Struts-el needed Servlet 2.3, and so
that's why I suggested having it in 1.2.   But my main purpose was to
create a common definition of what was going to be in each release (and
have it track as things change), so it should reflect the shared belief
of the developers. 

David Karr -- care to chime in on whether Struts-el needs Servlet
2.3/JSP 1.2?

Steve

> -----Original Message-----
> From: Eddie Bush [mailto:ekbush@;swbell.net]
> Sent: Thursday, October 17, 2002 11:29 AM
> To: Struts Developers List
> Subject: Re: Tiles Refactorings for 1.1 compatability
> 
> 
> Byrne, Steven wrote:
> 
> >Here's the draft roadmap  that I wrote up.
> >
> >Struts 1.1
> >  * Servlet 2.2 / JSP 1.1 based
> >  * tiles & validator first class citizens
> >  * tiles module aware
> >  * validator module aware
> >  * Struts-el tag lib at contrib status
> >  * [need help here] ??? factored out into jakarta commons
> >  * resources factored out into commons-resources?
> >
> >Struts 1.2   January 2003 [duration: 2 months? ]  
> >  * Servlet 2.3 / JSP 1.2 based
> >
> -1
> 
> >  * Struts-el tag lib integrated
> >  * Support for distributed struts components within a single
> >application
> >    (either by just having a list of them or by using some assembling
> >    technology)
> >  * tiles JSTL aware
> >
> ? What is the problem with Tiles' JSTL awareness?
> 
> >  * 1.1 bug fixes
> >
> This would be about the only thing here IMHO.
> 
> >  * [need help here] ??? factored out into jakarta commons
> >
> >Struts 2.0   Q2 2003 [duration: ??? months ]
> >  * Servlet 2.4 / JSP 2.0
> >
> -1 - 2.0 will be 2.3 /1.2
> 
> >  * JSF integration
> >
> Right.
> 
> >[I'm not sure whether to tie these items in with the above roadmap or
> >not]
> >
> >Struts 1.2
> >  * investigate and prototype alternative module 
> organizations including
> >      * arbitrary levels of nesting
> >
> This can be done now.
> 
> >      * locale based structuring 
> >      * inheritance of elements from base types
> >       * struts-config
> >       * tiles [already has this, but there may be ways to make it
> >cleaner]
> >       * validators
> >          * investigate adding identifier namespaces 
> >
> The "sharing" is the thing we're struggling with - more precisely the 
> timing of implementing it.  It has been suggested this would 
> happen in 
> 1.2, and I think that's acceptable.  I think (personally) 1.2 should 
> focus *only* on how we will give "more brains" to modules.  
> It should be 
> a *quick* turn-around - throwing in 2.3 / 1.2 will do nothing to aid 
> it's quick delivery, and Craig himself suggested those changes (along 
> iwth JSF) be slated for 2.0.  I like his idea.
> 
> -- 
> Eddie Bush
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail: 
> <mailto:struts-dev-help@;jakarta.apache.org>
> 
> 

--
To unsubscribe, e-mail:   <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>

Reply via email to