IBM WebSphere Studio Application Developer Interim Fix 001
for IBM WebSphere Studio Application Developer, Version 5.0.1
This refresh contains fixes for the following problems:
- 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.
- APAR PQ74587: Data lost while editing JSPs with large client script.
- Taglibs in compile-time included JSPs aren't registered.
- 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.
- 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.
- 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".