It could be there's a bug in the earliest 1.4 releases, but I couldn't find a report of it. Is it possible your path or class path is actually pointing to a JDK 1.3 or earlier? Can you see and use other 1.4 features like, say, java.util.regex.Pattern?
Is there something I have to do to make it reevaluate the code in light of this change?
Also, the most recent item in that list is for WAS v5.1. Is there a way to update this list to include 5.1.1 (JDK 1.4.2)? Keeping in mind that WAS is actually on the server and not on my development box with WSAD.
I also have the Sun 1.5 JDK installed locally. Is it possible to add that JDK here and still target WAS with my EAR projects?
Joined: Dec 31, 2004
Well, WSAD is based on Eclipse. Although you changed the list of installed JDK you still have to make the changes in your class path.
At least in my Eclipse environment (and I almost sure is the same in WSAD) you right click on the project root and choose Build Path->Configure Build Path.
There in the Libraries tab make sure that you are using the right JDK library. If not, remove the current library and add one of the new ones you just configured.
Does that help?
Joined: Jun 18, 2006
I finally resolved this problem. In testing, I created a simple "console" application with a main() method. I could use the String.split() method from this project. However, when working with an EJB project, the split method was unavailable and produced errors.
The steps to fix it were:
1. Select Window > Preferences > J2EE. Then select "Enable server targeting support" 2. Select Project > Properties > J2EE. From the Target server combo box, select WebSphere Application Server v5.1.
This caused the EJB project to use the 1.4 JRE and resolved all the String.split() calls.