|
wdsci-l-bounces@xxxxxxxxxxxx wrote on 06/22/2005 11:05:22 AM: > I think that only WAS 5.0 is run on Java 1.3. WAS 5.1 is, or has a PTF to > bring it to Java 1.4. Right. That is why I did not notice it first, because I am using WAS 5.1 internally. The problem came up with a customer on WAS 5.0. > As far as I know RAD 6 will create J2EE 1.3 and 1.4 projects. I'm not > sure about 1.2 but since even WAS 5.0 will run J2EE 1.3 that is probably > not a big problem? When you create a project you select the target server > platform, the default is WAS 6.0. I don't know if the target server is > used somehow to define how the jsp's are compiled or not but if you put a > scriptlet in the jsp that has 1.4 constructs..... The problem is that even if you choose an older version of J2EE, by default it will still use the newer compiler classes. This would not cause problems with JSP, but if you write Java code, and use the StringBuffer class you get this silent problem. This was a good article that explained it: http://www.itjungle.com/mgo/mgo072303-story01.html Unlike using some new JDK 1.4 class, this is a very silent problem that would be hard to detect. It is the same code that you could have been using since java 1.2, but Java 1.4 will compile it to use new features not available on older versions of Java. > Just for interest I have Subclipse now running on WDSC 5.1.2 (Eclipse 2.1) > and WDSC 6.0 (Eclipse 3.something). Both connecting to a remote (Linux) > server with svn+ssh. Great! Now just get those repositories migrated to OS/400 :). Mark _____________________________________________________________________________ Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs. _____________________________________________________________________________
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.