IBM WebSphere Studio Application Developer Interim Fix 003

for IBM WebSphere Studio Application Developer, Version 5.0.1



This refresh contains fixes included in the Interim Fix 001 as well as fixes for the following problems:

  1. (Windows only) APAR PQ77106: Page Designer fails to preview when JavaScript is faulty.

  2. APAR JR18487: Exception when running a headless ANT application:
    com.ibm.etools.wft.util.WFTWrappedException
    at com.ibm.etools.ejb.ant.EJBDeploy.execute(EJBDeploy.java:118)
    at org.apache.tools.ant.Task.perform(Task.java:217)
    at org.apache.tools.ant.Target.execute(Target.java:184)
    at org.apache.tools.ant.Target.performTasks(Target.java:202)
    at org.apache.tools.ant.Project.executeTarget(Project.java:601)
    [...]

  3. Added fixes to RunAnt to save the workspace when complete so it will not cause a refresh when the workspace is opened in the UI. Added task compileWorkspace which does a javac on all projects in the workspace in the proper order. Added quiet property to ProjectBuild to avoid writing to the console output when running in the UI.

  4. APAR JR18726: WAR import mismatch for source/class. If a .war file contains the following files:
    /WEB-INF/source/util/foo.xml
    /WEB-INF/source/bar/util/foo.xml
    /WEB-INF/classes/util/foo.xml
    /WEB-INF/classes/bar/util/foo.xml
    WAR Import is erroneously matching /WEB-INF/source/util/foo.xml with /WEB-INF/classes/util/foo.xml upon import. That leaves /WEB-INF/source/bar/util/foo.xml without a match, so it is not copied over to the JavaSource directory, and when a rebuild is done, /WEB-INF/classes/bar/util/foo.xml is deleted and never regenerated. Better matching of source and class files has been implemented to prevent this problem from occurring.

  5. APAR JR18846: For 1.1 Container Managed entity beans, if no fields are added to the predicate for (used for Optimistic Locking) then no locking is being done. After applying this fix, all available fields are added to the overqualified predicate if no fields are physically defined.

  6. APAR JR18245: Fix to EJB QL generation where defined converters were not being used when the converter was on a column of the abstract schema name other than the first abstract schema name used in the EJB QL statement.


Fixes included in the Interim Fix 001:


  1. APAR JR18499: Running the JSP Validator can interfere with other plugins that also use the Xerces environment. This problem can occur when running other functions after validating JSPs and can be difficult to track down. Symptoms usually involve errors or messages involving Xerces classes such as: ClassCastException: org.apache.xerces.parsers.StandardParserConfiguration.

  2. APAR PQ74587: Data lost while editing JSPs with large client script.

  3. Taglibs in compile-time included JSPs aren't registered.

  4. APAR JR18470: Use of a non-IBM JRE causes failures when deploying EJB's. During the rmic stubs/skeletons generation phase, the deploy tool fails with the following message:
    "com.ibm.etools.rmic.RMICException: RMIC Command returns RC = 1".
    This fix allows the use of a non-IBM JRE but forces the use of the IBM specific rmic compiler during the stubs/skeleltons generation phase.

  5. When an Entity Bean has an attribute that is a dependent value object (DVO), modifying the DVO for business logic reasons in the application will cause the dependent value object held by the Entity Bean to be changed.The only way to change the value of a DVO must be to invoke the setter on the Entity Bean. However, due to this problem, when a client EJB calls the setter on the Entity Bean, the Entity Bean saves a reference to the DVO. Similarly, when a client EJB calls the getter, the client gets a reference to the DVO in the Entity Bean. In both scenarios, subsequent changes to the DVO made by the client will be persisted when the Entity Bean is persisted, even though the setter may not have been invoked again. This problem occurs only when Enterprise Java Beans are accessed locally.

  6. APAR JR18488: When using WSAD 5.0. 1 and DB2 V8.1 fixpack 2, the following error occurs when getting a new connection:
    "The procedure entry point sqloGetDecimalSeparatorFromCc could not be located in the dynamic link library db2locale.dll".