What are people's feelings about supporting Servlet 2.2 in post 1.1?  Is
it time that we can say in 1.2 and beyond that servlet 2.3 is required?

I was thinking about the roadmap, and realizing that while a Struts
version that was JSF aware was probably a ways off, a version with JSTL
incorporated into it (and here I'm thinking about Mr. Karr's work) as a
first class citizen would not be as far off, and we may not want to hold
up incorporating that technology waiting for JSF integration.

That makes me think that it would be a good thing to say that in 1.2
Servlet 2.3 is required.  Remember, 1.2 will be a few months out from
now, so it doesn't seem that at that time 2.3/JSP 1.2 would be that bad
of a thing to say is the lower end of what is supported?

Comments?

I'm going to write up a draft roadmap tomorrow and send it around for
comments.  If you want to provide input into it, please speak up now so
I can incorporate your ideas.  Right now I can think of two basic
buckets:

1.2 
   Servlet 2.3 / JSP 1.2 based (assuming no objections
   JSTL tag library incorporated as a first class citizen
   Support for distributed struts components within a single application
(either by just having
      a list of them or by using some assembling technology)
   1.1 bugs fixes

2.0
   Servlet 2.4 based (?)
   JSF integration

This presumes that 1.1 has Tiles and Validator in place as first class
citizens and working properly with sub applications.

> -----Original Message-----
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 16, 2002 2:33 PM
> To: Struts Developers List; [EMAIL PROTECTED]
> Subject: Re: RE: Tiles Refactorings for 1.1 compatability
> 
> 
> 
> IMHO, any rational roadmap for post-1.1 is going to have to 
> lump proposed
> changes into at least two buckets:
> 
> * Those that can be implemented on Servlet 2.2 / JSP 1.1,
>   including refactoring of existing functionality (but
>   with a continued emphasis on backwards compatibility).
> 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to