1.2 all the way. There are decent 1.2 or 1.3 JDK/JVM implementations for
pretty well every significant platform (that also has a good 1.1 VM, in any
case), and as for the Servlet/JSP engines, all the ones that do JSP taglibs
run fine under 1.2... There are obviously still lots of people running
things like WebLogic 4.5 or WebSphere 3, under JDK 1.1, but those platforms
can't support Struts in any case, and I also doubt anybody is going to
develop new code there...
> -----Original Message-----
> From: Craig R. McClanahan [mailto:Craig.McClanahan@eng.sun.com]
> Sent: September 25, 2000 9:01 PM
> To: struts-dev@jakarta.apache.org
> Subject: Re: Use of Hashtable vs HashMap
>
>
> Robert Leland wrote:
>
> > C
>
> Reading between the lines here :-), was this going to be a question
> about why Hashtable is used instead of HashMap? The answer is pretty
> simple -- the ability to run on JDK 1.1 platforms.
>
> A couple of months ago, I posed a question about dropping JDK 1.1
> compatibility, especially in light of the fact that the new
> servlet 2.3
> and JSP 1.2 specs require Java2. There was some definite
> sentiment that
> people wanted JDK 1.1 support to continue for a while. What
> that meant
> for Struts is that I couldn't use cool Java2 things in the basic
> infrastructure -- only in particular custom tags where there
> was also a
> JDK1.1 alternative. (Note that you need Java2 to compile Struts
> itself.)
>
> In the time since that discussion, we've seen more and more
> announcements of JDK 1.2 and/or 1.3 implementations for nearly every
> platform of interest. So, I'd like to pose the question again and see
> how people feel now.
>
> For Struts 1.0, should we go for a Java2 minimum requirement to run
> Struts-based applications?
>
> Craig
>
> ====================
> See you at ApacheCon Europe <http://www.apachecon.com>!
> Session VS01 (23-Oct 13h00-17h00): Sun Technical Briefing
> Session T06 (24-Oct 14h00-15h00): Migrating Apache JServ
> Applications to Tomcat
>
>
|