On my current project all the J2EE apps have been running on Glassfish and has been running well in my opinion. Today I have been instructed to port all our J2EE apps from Glassfish to WebSphere. This is simply because the client had a bad experience with SUN App Server clustering a year ago, and for that reason we must port. I suggested that we rather port to WAS CE (Geronimo) and use it as a path to move to WAS 7.
The installation of WASCE as well as the Eclipse 3.4 Server Adapter was straight forward, but all came to a halt when tried to create a web application with WASCE set as its target runtime. Eclipse kept returning a NullPointerException. After checking the internal logs, it came down to a JAXB Exception. After few hours of trial and error, I realized the Server Adapter plugin is failing because my Eclipse has not been started on the IBM JDK. It seems that the SUN JAXB Provider keeps failing the code in the WASCE Server Adapter plugin but the IBM JDK Provider accepts it. This on its own gets me worrying already.
So after setting my Eclipse ini configuration to start using the IBM JDK things started to work. Problem is that all my project have been compiled on the SUN JDK 1.6, so I will have to recompile and re-test especially since some of my modules are complex multi-threaded concurrent applications.
With this experience, my opinion of IBM's acquisition of SUN is becoming more pessimistic. I can say out of experience that IBM has even written a Java applet for its internal staff that ONLY runs on Windows and ONLY runs on Internet Explorer. So much for the "write once, run anywhere" goal.
[ add comment ] ( 1 view ) | permalink |
( 2.9 / 323 )
Calendar
