Regarding the required environment for using Struts: The servlet 2.3 spec is now 2 
years old. There seem to be agreement, that it is still too early to switch to that 
platform.

There also seem to be agreement, that the required platform for Struts 1.x should be 
servlet 2.2/JSP1.1.

If the Servlet 2.4/JSP2.0 is not yet finalized, when will it be possible to use this 
as a minimum requirement for trus? 3 years from now?

The corollary of this will be, that if JSP2.0 /JSF should be the required platform for 
Struts 2.x, then
it will be necessary to stick with Struts 1.x/Servlet2.2/JSP1.1 for another 
approximately 3 years.

IMO this would be a very bad idea. Wouldn't it be better to switch the versioning to 
2.x, maybe next summer, and then switch to Servlet2.3/JSP1.2? This should leave space 
for a couple af "cleanup" releases in between.

Kent


Craig R. McClanahan <[EMAIL PROTECTED]> wrote:
> On Fri, 29 Aug 2003, David Graham wrote:
> 
> > Date: Fri, 29 Aug 2003 10:26:54 -0700 (PDT)
> > From: David Graham <[EMAIL PROTECTED]>
> > Reply-To: Struts Developers List
> <[EMAIL PROTECTED]>,
> >      [EMAIL PROTECTED]
> > To: Struts Developers List
> <[EMAIL PROTECTED]>
> > Subject: RE: Support for non-JSTL tags (was RE: DO NOT
> REPLY [Bug 21465]
> >     -     Enhancement of the html:link tag)
> >
> > --- Rick Hightower <[EMAIL PROTECTED]> wrote:
> > > I am not a voter, but I think....
> > >
> > > Comments below...
> > >
> > >
> > > Rick Hightower
> > > Chief Technology Officer
> > > Trivera Technologies
> > > http://www.triveratech.com
> > > 520 290 6855 (Phone)
> > > 520 977 8605 (Mobile)
> > >
> > >
> > > -----Original Message-----
> > > From: Steve Raeburn [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, August 27, 2003 9:20 PM
> > > To: Struts Developers List
> > > Subject: Support for non-JSTL tags (was RE: DO NOT REPLY
> [Bug 21465] -
> > > Enhancement of the html:link tag)
> > >
> > > I'm not singling Vic out for this (honest) but...
> > >
> > > The standard advice we are now giving everyone is "use
> JSTL", which I
> > > wholeheartedly agree with and have said myself. However,
> I think we need
> > > to
> > > make sure that we still adequately support non-JSTL
> solutions and
> > > continue
> > > to consider bug fixes/enhancements to Struts tags EVEN
> where it would
> > > duplicate JSTL functionality because Struts still
> supports JSP
> > > 1.1/Servlet2.2.
> > >
> > > ************ I don't think fixing non-JSTL tags should
> take priority. I
> > > think deprecated tags like logic:iterate, and their ilk
> should receive
> > > very
> > > little attention. BTW I am going to make a concerted
> effort to
> > > contribute to
> > > this project. Please excuse me while I am new if I make
> any snafu. (I
> > > have
> > > some stuff and ideas in the works. Mostly bug fix type
> ideas.)
> > >
> > > I haven't considered whether this particular enhancement
> would fall into
> > > the
> > > category of something we should do, it just prompted me
> to raise the
> > > issue.
> > >
> > > If we've reached the stage where the recommendations we
> are making
> > > *require*
> > > JSTL, then I think it's time to be honest about the
> required platform
> > > for
> > > Struts and up it to 1.1/2.3
> > >
> > > **************** I think Struts 1.2 and higher should
> *require* JSTL
> > > tags,
> > > and overlapping Struts tags should be deprecated (aren't
> they already).
> > > If
> > > this is not feasible for Struts 1.2, then Struts 1.3 or
> 1.5 or
> > > 1.whatever.
> >
> >
> > What's the rush?  Why does Struts 1.x need to require
> JSTL?  They are
> > independent technologies that can be used together if the
> developer
> > chooses.  The Struts tags work in their current form and I
> agree that
> > enhancing them is time better spent elsewhere.  But fixing
> bugs is still
> > necessary so that the tags are as stable as possible for
> the people still
> > stuck on Servlet 2.2 containers.
> >
> 
> I don't think it's even necessary to *deprecate* the old
> tags.  There are
> lots of existing apps that use them, and it is rather
> unfriendly to force
> people to change all their pages to update to a later Struts
> build.
> 
> We should be fixing bugs in the existing tags ... but I
> don't see much use
> in adding a whole bunch of new ones.
> 
> I'm -1 on making Struts 1.2.x dependent on Servlet 2.3 / JSP
> 1.2.  If
> we're going to maintain backwards compatibility in this
> sequence, we need
> to maintain the same base platform as well.
> 
> > IMO, Struts 2.x should attempt to get out of the taglib
> business
> > altogether.  Until then, we should just let the tags be
> and maintain
> > Struts 1.x as Servlet 2.2 minimum requirement.
> 
> Earlier, we had talked about using Servlet 2.4 and JSP 2.0
> as the basis
> for Struts 2.x, and I still like that approach, because
> these specs are
> close to being finalized, and will certainly be final before
> we need them.
> 
> The interesting part of this is going to be the timing -- I
> would
> anticipate we'll continue doing production quality releases
> of 1.2.x,
> while starting to do some experimental builds in 2.x, in
> overlapping
> times.  But that's dependent on what the committers are
> willing and able
> to work on, of course.
> 
> >
> > David
> 
> Craig (whose time will free up later on as JavaServer Faces
> gets done)
> 
> ------------------------------------------------------------
> ---------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 


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

Reply via email to