> -----Original Message----- > From: Steve Short [mailto:[EMAIL PROTECTED] > Sent: 03 July 2003 17:10 > To: James Users List > Subject: RE: Anyone still using JDK 1.3?
... > Moving forward is a problem because we run James inside app > servers such > as WebLogic and WebSphere, and it is our customers not us that dictate > which JVM they use. > > Steve And where are the two major J2EE vendors at in terms of JDK support? Here... BEA WebLogic Server v8.1 requires JDK 1.4.1 v7.1 requires JDK 1.3.1 or JDK 1.4.1 v6.1 requires JDK 1.3.1 IBM Websphere Application Server v5 requires JDK 1.3.1 v4 requires JDK 1.3.1 Note that "requires" means that this is the level of JDK that the vendor states will work. There is no guarantee that a higher level will work. I don't have any figures, but my hunch is that BEA WebLogic Server v6.x and IBM Websphere Application Server v4 are the most widely deployed in production environments. This implies that it could be 12 months or more before JDk 1.4 becomes widespread in such environments. If James is to maintain compatability with the the major J2EE environments and their users, we aren't dropping 1.3.1 support soon. These users are not typically early adopters, so are unlikely to be frustrated if James 3 moves to JDK 1.4. This reinforces my earlier argument. Stick with JDK 1.3.1 for James 2, move to JDK 1.4.1 for James 3. -- Steve
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
