We're also in the process of migrating from 1.2 to 1.4. There are some optional packages that are now included in 1.4 such as JSSE and XML parsing, so don't bother to include them. However, you still need to include other packages such as the JavaMail package, and AFAIK, they should work as is. Even our application pretty much worked without having to be recompiled although there were a few hitches here and there during testing. For example, under 1.2, we were getting away with storing binary contents as Strings by doing new String(byte[]). Under 1.4, it replaces all the bytes that don't legitimately translate to printable characters into question marks. We ended up having to base 64 encode the byte array first. Also, we got into trouble with RMI. We don't create RMI objects by subclassing UnicastRemoteObject. Instead, we do it by exporting the object via the UnicastRemoteObject.exportObject(Remote). Well, under 1.2, we never bothered to invoke UnicastRemoteObject.unexportObject(Remote) on shutdown, so when we tried to do a shutdown while running under 1.4, the JVM just hung around and refused to shut down.
HTH! Stan -----Original Message----- From: Dan Patten [mailto:[EMAIL PROTECTED]] Sent: Monday, July 01, 2002 7:08 AM To: JDJList Subject: [jdjlist] Java 1.4 Conversion Questions We are contemplating moving our application to 1.4. We are currently at 1.3.1_03. We have a large 3-tier application which makes heavy use of JDBC/ODBC, RMI and Swing. Questions for those who have made the move. Are the performance gains noticeable for Swing and RMI? Are there any general pitfalls to watch for? Are there issues with use of jar files such as mail.jar, activation.jar and other 3rd party jar files? I am fuzzy on whether we can use these jar files as they are downloaded or whether we need to compile the source under 1.4 and create the jar files. We have just installed 1.4 on one of the development PCs and tried our first compile. Everything compiled without errors although there are some deprecation warnings. The server app seems to start OK. We can start the client app but when we login, which causes the first communication to the server app, we get a malformed URL Exception. We obviously don't have such a problem under 1.3. Has anyone experienced a similar issue? To change your membership options, refer to: http://www.sys-con.com/java/list.cfm To change your membership options, refer to: http://www.sys-con.com/java/list.cfm
