IBM WebSphere Studio Site Developer PTF 001 - General Fixes

for IBM WebSphere Studio Site Developer, Version 5.0.0.2



This refresh contains fixes for the following problems:

Server tools

  1. 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

  1. 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

  1. 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.

  2. 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

  1. 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.

  2. 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.

  3. 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

  1. 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.

  2. 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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. In WebSphere Studio Version 5.0, builds for moderate to large Web workspaces become quite slow. This problem is resolved after applying this fix.

  7. 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.

  8. 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.

  9. 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

  1. 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.

  2. 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.

Profiling tools

  1. 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.

  2. 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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  8. 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.

  9. 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

  1. 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.