Welcome to IBM WebSphere TM Studio 3.5 Fixpack 3 (V3.5.3). This ReadMe contains information about installing and using IBM WebSphere Studio 3.5.3. This fixpack will upgrade your copy of IBM WebSphere Studio Entry, Professional, or Advanced Edition from version 3.5.2 to version 3.5.3.
This file includes information about:
This fixpack is not cumulative. Before you can install Fixpack 3, you must already have Studio Fixpack 2 (V3.5.2) installed. If you do not have Fixpack 2 already installed, you may download it from the Studio support page or request an updated CD. Studio V3.5.2 Advanced and Professional edition CDs are available upon request from the Studio fixpack support page.
To install this fixpack you need:
To verify that you have Studio V3.5.2 installed:
This fixpack corrects the following problems:
| APAR | Description |
|---|---|
| PQ45345 | If servlets are in a package, update from VisualAge for Java 3.5 places .class files in the wrong folder and that results in wrong version of file being checked in and published (Defect 6749-KP) |
| Defect | Description |
|---|---|
| 5514-SC | Applet Designer remains the registered editor for .app and .class files after uninstalling just Applet Designer |
| 6378-ST | When checking in an HTML file, the <code>
tag incorrectly gets changed from <code dir="rtl"> to
<code> dir="rtl"> |
| 6468-BH | Wizard generated code for JSP 1.1 does not include
the contentType attribute of the JSP page directive causing problems for
character encoding other than ISO-8859-1. To define the contentType as character encoding other than IS0-8859-1, refer to the instructions below. |
| 6621-AW | When inserting more than 1 image rollover on a page, the image mouseover and mouseout paths are incorrect |
| 6663-AW | Applet codebase path is incorrect when published to server. Publishing the file changes the codebase to the location of the .html file |
| 6670-KP | When using the dynamic view in ClearCase Version Control, instead of the recommended snapshot view, Studio will crash when attempting to execute an Update with Latest Version |
| 6745-KP | The Pervasive Studio Sample has broken links which cause it to fail |
| 6753-VT | During installation, Studio may loop when attempting to update the registry because a denial of access will lead to a buffer overflow |
| 6758-KP | When the parser encounters the document object with theForm and action properties (document.theForm.action), it incorrectly parses the code before the object instead of after the object |
| 6760-KP | If studio is installed in a directory with spaces in the path, Studio will generate corrupted WAR files |
| 6770-KP | The JavaScript parser corrupts code when .action
links to a string that begins with an &, such
as: theForm.action= URLString + "?color=" + color + "&name=" + name; |
| 6784-JZ | The JavaScript parser corrupts links when the
variable is concatenated with the target filename, such as
appDir+"toc.html" Sample code: parent.TOCFrame.document.location=appDir+"toc.html"; |
| 6783-YD | Due to registry changes, Studio cannot detect Microsoft SourceSafe V6.0 |
This fixpack corrects the following Page Designer problems:
| Defect | Description |
|---|---|
| 6478-KP | When attempting to checkout or open a file that is already checked out by another user, Page Designer creates a new file instead of retrieving a read-only copy of the file based on the last checked in version |
| 6748-KP | In the Source view, two accelerator keys, Ctrl+left arrow or Ctrl+right arrow, do not work |
| 6772-KP | In the Source view, using Shift+Insert puts Page Designer in overstrike mode |
| 6774-JA | Page Hits error Invalid jsp: include tag is issued for the CounterServletOutputPage.jsp. The error only occurs when running JSP 1.1 |
| 6780-HM | Cannot input period characters in HTML Source View |
In this fixpack, wizard generated JSP 1.1 files include the contentType attribute in the JSP page directive. The Studio wizards use the charset value of the configuration file (studiocodegencfg.xml) to assign the JSP page directive contentType value. The charset in the configuration file is defined as ISO-8859-1. If you require a different contentType value, you must edit the charset attribute in the studiocodegencfg.xml file. This file is located in the Studio bin directory.
Note: The studiocodegencfg.xml file is the Studio wizard configuration file for generating JSPs. It is crucial that you do not corrupt it. Before editing the studiocodegencfg.xml file, create a backup of it.
To modify the contentType attribute of the JSP page directive for character encoding other than ISO-8859-1:
Refer to the World Wide Web Consortium (W3C) site for common character encoding: http://www.w3.org/International/
Find the most up-to-date information about Studio: Release Notes, Frequently Asked Questions (FAQs), and White Papers at the IBM WebSphere Studio pages.
For the most recent information about known problems and considerations, and defect corrections refer to the Release Notes in the Related Information section on the IBM WebSphere Studio Support page.
The most current Studio Guide is available on the IBM WebSphere Studio Library page. The Studio Guide is available in either HTML or PDF format.
IBM, the IBM logo and WebSphere are trademarks of IBM Corporation in the U.S., other countries, or both.
Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the US, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Other company, product, and service names may be trademarks or service marks of others.
Portions copyright (c) Blue Sky Software Corporation. All rights reserved.
Portions copyright (c) Microsoft Corporation. All rights reserved.