******************************************************** (c) Copyright 1999 International Business Machines Corp. All rights reserved. ******************************************************** ** IBM WebSphere Studio FixPack 2 for Entry Edition ** ******************************************************** This fixpack will upgrade your copy of IBM WebSphere Studio Entry Edition from version 3.0 or 3.0.1 to version 3.0.2. FixPack 2 contains all files updated in FixPack 1 so you do not need to install FixPack 1 prior to installing FixPack 2. This fixpack only upgrades the Entry Edition of IBM WebSphere Studio. This fixpack corrects several problems in Studio, Page Designer, and Applet Designer. This file contains information about: >> Known problems >> Problems that are corrected by the fixpack >>>>>>>>>>>>>>>> KNOWN PROBLEMS >>>>>>>>>>>>>>>> >> HTML links appear broken In the Relations View, links within an HTML file to a servlet sometimes appear to be broken. This problem does not affect publication. Studio will correct the links when you publish the files to a publishing server. To make the links appear correctly in the Relations View, check out the .html file and then check it back in. >> Using "Allow Update" in the Database Wizard There is a known problem in the WebSphere Application Server 3.0 JSP 1.0 processor that causes database values which are NULL to be displayed as 'null' instead of an empty string ''. This could cause problems when choosing "Allow update" in the Database Wizard because updated data might be corrupted, or more likely, the servlet that does the update will not run due to a NumberFormatException. At the present time, we recommend using 'Allow update' only in conjunction with JSP 0.91. >> Using explicit drive letters with shared projects Because Studio files contain absolute file paths, if a shared project is created with a specific drive letter, all people who access the project must use that same drive letter on their system. You can avoid this by creating your projects with UNC names instead of drive letters, unless you are using PVCS as your version control system. To switch a project from a drive letter to a UNC name, you must archive the project and then open the archive in a new location using a UNC name. >> Need full package names in Quick Tour 4 - JAR wizard You need to enter the full package name for the FireworksEvent and FireworksListener classes when preparing to publish the JAR file in Step 8. If you do not use the full package name, you will get a "Class not found" error message. In this step, type WebSphereSamples.Fireworks.FireworksEvent (instead of FireworksEvent)and type WebSphereSamples.Fireworks.FireworksListener (instead of FireworksListener). >> Need SCC Hot fix 3 for VisualAge TeamConnection Version 3.0 Studio does not include TeamConnection's SCC interface DLL. If you have TeamConnection version 3.02 or earlier, you must get the latest DLL from their Web site. Hot fix 3 for VisualAge TeamConnection contains this DLL. >> Publishing to the AS/400 In order to correctly set the code page on files published to the AS/400, we recommended that you map the network drive using Client Access or NetServer, and then publish the files using the "File system publish" option of Studio. The code pages of the files published to the AS/400 are determined by the configuration of Client Access or NetServer. >>>>>>>>>>>>>>>>>> CORRECTED PROBLEMS >>>>>>>>>>>>>>>>>> The following problems are corrected with fixpack 2: Studio Defect# Description ------- ------------------------------------------------------------ 4025-SH Jar Wizard fails on Fireworks.class if FireworksEvent.class and FireworksListener.class are not also checked out 4291-TA Garbage string at VisualAge Java Export dialog 4393-CM Broken links after building html with JavaBean wizard 4404-HM URLs in inline CSS style information are broken 4406-PJ Application Server jar files not present on JSP compile CLASSPATH 4407-PJ Publishing view ignores other servers if default is deleted 4427-KL Message not translated from English to Korean: "Only .class files can be used to start an editor in VisualAge for Java." 4436-KL Need to support multiple VisualAge for Java installs 4449-CM Errors about insufficient disk space while installing VAJ 4463-CM Importing JSP file loses some JavaScript 4467-MK Improperly generating PageDesigner metadata in JSP page 4469-MK BeanInfo is cached too much in Page Designer 4473-MK Generating incorrect code for VisualAge Navigator Beans 4479-MK Broken links when Database Wizard is used and allow update is checked 4446-CM Compile fails for file that is checked out under version control Page Designer Defect# Description ------- ------------------------------------------------------------ 4343-MN Could not set Bean property to the value of another bean property 4418-MN Crash when reading compressed bitmaps from CnP, DnD, and Twain 4459-HM Hang when CSS data contains many URLs 4500-TA BLACK background when a JSP is used to specified as color name Applet Designer Defect# Description ------- ------------------------------------------------------------ 4483-SC Published applet that uses Method bean fails to run in browser with class not found error in Java Console The following problems were corrected with fixpack 1: Studio Defect# Description ------- ------------------------------------------------------------ 4312-SK Custom wizard icons do not show up in File View or Relations view 4316-TA Projects migrated from Studio 1.0 are set for Application Server 3 instead of Application Server 2 4318-SK Rename does not work when "Keep views in sync" is turned off 4319-MY Link to Studio Guide is pointing to the English version not the German Version on German Windows 4320-MY Box (EOF) characters at the end of German Studio Guide files 4323-DW Crash if JVM cannot be created instead of an error message 4327-SC Autopublish does not occur when a virtual folder is changed to non-virtual 4329-LR Beta is still in the about dialog strings on Korean Windows 4361-MM Error in YourCo Sample survey results returned page 4363-MK Improperly detecting Enterprise JavaBean init properties 4364-HM URLs in