IBM WebSphere Studio Application Developer PTF 001 - General Fixes
for IBM WebSphere Studio Application Developer, Version 5.0.0.2
This refresh contains fixes for the following problems:
EJB tools
-
In WebSphere Studio Version 5.0, updating the key shape of a CMP bean causes the EJB life cycle methods
(for example, ejbRemove()) to be overwritten with the default implementations. With this fix, the life
cycle methods remain untouched when the key shape of a CMP entity bean is changed.
-
In WebSphere Studio Version 5.0, a PrimitiveType array is not viewed as primitive, and is
therefore fully qualified, resulting in Java compilation errors. This problem is resolved after
applying this fix.
-
In WebSphere Studio Version 5.0, when working with a local reference, editing the link causes both the
local-home and the local reference to be switched. Also, when changing a link by selecting the
Browse button, the change is not actually saved, so it will appear that it has reverted to the
original value when you access it again. Both of these issues are resolved after applying this fix.
-
In WebSphere Studio Version 5.0, when you try to set a join key on a secondary table mapping, the
Property view freezes and a null pointer exception error message is displayed. Additionally, no
foreign key is selected by default as the join key when adding a secondary table map to a leaf table
in a root-leaf inheritance structure. Both of these problems are now corrected. The proper foreign key
is automatically selected as the join key, and you can now edit the join key field from the Property
view if no selection is made.
-
In WebSphere Studio Version 5.0, attempting to add more than two parameters to a finder query may
result in the code being generated with only one parameter. This problem is resolved after applying
this fix.
-
In WebSphere Studio Version 5.0, when exporting an EAR with a WAR containing a Web library project(WLP),
the path to the WLP JAR has an unnecessary leading "/". This causes problems when you try to install
the WAR on WebSphere Application Server. This fix removes the leading "/" on export.
-
In WebSphere Studio Version 5.0, regenerating a EJB may result in an inheritance hierarchy restructuring.
For example, you have created 2 CMPs, A and B (with Java bean classes ABean and BBean respectively).
If you have B EJB inherit from A EJB, this causes BBean to extend ABean. You then create a new Java class,
CJava that extends ABean, and update BBean so that it extends CJava. You now have the following Java
class inheritance structure:
ABean
|
CJava
|
BBean
Now add a new CMP field to EJB B - BBean now extends ABean instead of CJava. This fix resolves the
issue of introducing additional Java classes within an EJB inheritance structure which do not belong to
an EJB (for example, like CJava).
-
In WebSphere Studio Version 5.0, imported classes are not fully accessible. For example, if you follow
these steps:
-
Create a new EJB project and create an imported_classes class directory by clicking
Properties > Java Build Path > Libraries > Advanced.
-
Import an EJB's class files, then open the New Enterprise Bean wizard.
None of the class files will become red when selected, and reflection will not occur. This fix enables the
bean types to be reflected.
-
In WebSphere Studio Version 5.0, there is a performance problem when performing J2EE exports through
headless Ant. This fix modifies the incremental build to be more selective and only invoke the Java builder.
-
After applying this fix, the Migration wizard will now, by default, fix fully qualified schema URI's in the
map and database files of 1.2 EJB projects from WebSphere Studio Version 4.x. If you do not migrate these
projects from Version 4.x, you will not be able to deploy them on WebSphere Application Sever.
Note: If you export your EJB projects from Version 4.x and import them into Version 5.0, these files will be
fixed automatically. The problem this fix address only occurred previously if you loaded a Version 4.x EJB
project from a shared repository into Version 5.0.
-
In WebSphere Studio Version 5.0, if an EJB QL finder is modified using the wizard from the EJB Deployment
Descriptor editor, the parameters within the query element will be serialized in reverse order. This issue
is resolved after applying this fix.
EJB deployment
-
In WebSphere Studio Version 5.0, there is a performance problem when incremental builds are performed
through Ant. This fix modifies the incremental build to be more selective and only invoke the Java builder.
-
In WebSphere Studio Version 5.0, a StringIndexOutOfBoundsException occurs for data mapped to a BLOB or
CLOB column that has zero length. This issue is resolved in this fix.
-
In WebSphere Studio Version 5.0, an incorrect data start position is generated in the Persister class
(for example, in the EJSJDBCPersisterCMPXxxxxxBean.hydrate() method for CLOBs and BLOBs). After applying
this fix the data start position will be generated correctly.
-
In WebSphere Studio Version 5.0, when creating an SQL statement to implement the EJB QL for the finder,
the following message is displayed:
java.security.PrivilegedActionException
<<java.lang.ClassNotFoundException: VapStringToBooleanConverter>>
WQRY0123E: An error occurred while executing dataFrom method of converter [VapStringToBooleanConverter].
Query='select object(o) from MileageDetail o where o.validFlag = false'
This problem is resolved after applying this fix.
Server tools
-
In WebSphere Studio Version 5.0, the run-time classpath for the Universal Test Client is incorrect
when running on remote WebSphere servers. This may cause some user classes to be inaccessible from
the test client, which will cause problems when you are trying to test. Once this fix has been
applied, re-publish to the remote server to update the classpath.
-
In WebSphere Studio Version 5.0, the Tomcat server cannot be started in profiling mode. This
issue is resolved after applying this fix.
Web Services tools
-
In WebSphere Studio Version 5.0, a NullPointerException occurs when attempting to browse the dwCommunity categories
from the Web services explorer. This fix prevents the NullPointerException from occurring.
Web tools
-
In WebSphere Studio Version 5.0, the migration of Version 4.0 Web projects results in the Java build output
folder location being migrated incorrectly. The Java build output folder is set to Web Content/classes, when
it should be Web Content/WEB-INF/classes. This fix resolves this problem.
-
In WebSphere Studio Version 5.0, adding an EJB Reference to a Web deployment descriptor causes an XML
validation error on DBCS machines. This error is resolved with this fix.
-
When working with multiple servlets in WebSphere Studio Version 5.0, creating a filter mapping to any servlet
but the first one will result in an error when trying to re-open the servlet in an editor. The problem is
corrected with this fix.
Data tools
-
In WebSphere Studio Version 5.0, the readme stated that if repeated error dialogs are encountered while editing
database metadata, the product should be shut down and restarted. This problem is now resolved with this fix.
-
In WebSphere Studio Version 5.0, the readme provided a workaround for dealing with database metadata in Web
projects. The workaround consisted of a number of steps that were required to successfully migrate a Web project
containing database metadata, such that the database metadata could be recreated. The migration problems have
now been fixed, and only a single migration step is required to work with existing 4.0.3 database metadata
in WebSphere Studio 5.0. Migrating a Web project is a mandatory step if your Web project contains database
metadata.
-
In WebSphere Studio Version 5.0, connecting to an Oracle database via DB Explorer would result in the table columns
of type FLOAT or TIMESTAMP being incorrectly processed and appearing as type INTERVAL in the DB Server pane. This
problem has now been fixed, and column types of type FLOAT or TIMESTAMP are retained.
XML tools
-
In WebSphere Studio Version 5.0, signing an XML document using a digital signature (right-click an XML
file and click XML Security > Digital Signature) causes a NullPointerException when the
digital signature is about to be created. This problems has been resolved with this fix.
-
In WebSphere Studio Version 5.0, using the XML editor to enter text at the bottom of a large XML file
could be quite slow. This performance issue has now been addressed.
Struts tools
-
In WebSphere Studio Version 5.0, the Attributes view is not available for a <logic:iterate> tag nested
within a <logic:iterate> tag. This problem is resolved after applying this fix.
-
In WebSphere Studio Version 5.0, the Action Mapping wizard suggests a name for the Action class that
causes problems when saving the file in DBCS environments. This problem is resolved after applying this fix.
-
In WebSphere Studio Version 5.0, the Web Structure view is not updated when saving a JSP with changes such
as addition or removal of a link in the JSP. This problem is resolved after applying this fix.
-
In WebSphere Studio Version 5.0, certain links (such as stylesheet links) cause a NullPointerException in
the Struts indexer, and an incorrect broken link marker on the link. This problem is resolved after
applying this fix.
-
In WebSphere Studio Version 5.0, the TradeSample example application is not translated for supported DBCS
languages. This problem is resolved after applying this fix.
-
In WebSphere Studio Version 5.0, builds for moderate to large Web workspaces become quite slow. This problem
is resolved after applying this fix.
-
In WebSphere Studio Version 5.0, the DB2 install script for the TradeSample example application fails in
DBCS environments. This problem is resolved after applying this fix.
-
In WebSphere Studio Version 5.0, opening the Struts Cheat Sheet in some DBCS environments may cause errors.
This problem is resolved after applying this fix.
-
In WebSphere Studio Version 5.0, deleting a project results in a NullPointerException in the Struts indexer.
The problem is resolved with this fix.
Source editor
-
In WebSphere Studio Version 5.0, performing the "clean up" function on some JSP documents produces a
ClassCastException. This exception is written to the .log file, but is not otherwise apparent. After
this exception occurs, the source page will be frozen, not taking input or displaying changes. This
fix prevents the ClassCastException from occurring.
-
In WebSphere Studio Version 5.0, performing the "clean up" or "convert to XHTML" functions on some
documents, unexpected (and possibly invalid) tags are sometimes produced. For example, <jsp:useBean /%gt;
gets converted to:
<jsp:useBean />
<jsp:useBean></jsp:useBean>
<jsp:useBean></jsp:useBean>
This issue is resolved with this fix.
Component Test tools
-
In WebSphere Studio Version 5.0 on Windows 2000, Japanese characters are missing from labels in the
Component Test perspective. This fix resolves the problem.
Profiling tools
-
In WebSphere Studio Version 5.0, importing a WebSphere Application Server binary activity log file onto a
non-English machine results in no records being shown in the Profiling perspective. This issue is resolved
with this fix.
-
In WebSphere Studio Version 5.0, an empty agent is displayed in the Monitors view on machines set to the
Eastern Time time zone. The agent is properly displayed after applying this fix.
Visual Editor for Java
-
In WebSphere Studio Version 5.0, extending an abstract class is not supported. This fix instantiates
the first non-abstract class in the inheritance hierarchy.
-
In WebSphere Studio Version 5.0, when adding an element to a JSplitpane (with one free side) in the
Graph viewer the element is not always added to the free side. After applying this fix, the element
is added to the correct part of the JSplitpane.
-
In WebSphere Studio Version 5.0, the JOption border property editor does not allow you to change
the colour for the titled border. This fix resolves this issue.
-
In WebSphere Studio Version 5.0, duplicate code may be generated when changing property values where
errors exist in the source. This fix resolves this issue.
-
In WebSphere Studio Version 5.0, there is a problem with the Java visual editor and VM recycling. VM
recycling occurs when a class uses another class that has changed. This fix resolves various errors
that may occur during VM recycling.
-
In WebSphere Studio Version 5.0, incorrect code may be generated for a class that ends with an inline
comment. After applying this fix, this problem is resolved.
-
In WebSphere Studio Version 5.0, if there is code after a method's return statement the Property manager
and Editor no longer reflect changes in the code. This issue is resolved after applying this fix.
-
In WebSphere Studio Version 5.0, when opening the Visual Editor for Java in the J2EE perspective, the property
sheet is not always brought to the foreground automatically. After applying this fix, this issue is resolved.
-
Adding an import statement to fix compile errors may not be picked up by the snippet update engine. After
applying this fix, the issue is resolved.
Page Designer
-
In WebSphere Studio Version 5.0, when dragging and dropping to insert an item from the Library view into the
Design view, the item may be dropped to the previous location (not the location where you dropped the item
operation). The issue is resolved by this fix.