Craig mentioned lumping the 2.3 compliance conversion and JSF into one release - probably 2.0. Find his bucket post from yesterday :-)
So far as servlet spec 2.4 is concerned, I have no clue. What platform will our users be on? We don't want to upgrade ourselves out of a user-base. Yes, many of us will be able to switch - but there will be many forced to stay on 2.3 spec containers too - just like a lot of folks are stuck on 2.2 spec containers now. I don't have awareness enough of what everyone's flexibility is like wrt switching containers to have input on this really though.
I would very much like to see David's work incorporated as a "first-class citizen". I can't say how handy I find that set of tools! Anyone that has used them understands - anyone who hasn't doesn't.
So far as Validator/Tiles are concerned, they will be there in 1.1F, if I have any say about it (speaking with my code, as Ted suggested!). Validator, I believe, is there. If you experience problems with it's "module-friendliness" just yell. That's mine. I intend to have to fix anything I missed or messed up. I don't think there will be problems with it in that regard though ;-)
My suggested order of operation would be:
1.1F - finish what we're doing
1.2 - clean-up wrt modules
... and after that - whatever. It's very important that we clean up our mess though. While I don't anticipate the code-base to change much in 1.2, I do expect to see a lot more functionality in it.
Byrne, Steven wrote:
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.
-- 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>
