IBM^® Rational^® Software Architect Interim Fix 002

for Rational Software Architect, Version 6.0

(C) Copyright IBM Corporation 2000, 2004, 2005. All Rights Reserved.

Table of contents

1.0 Fixes contained in this release

This refresh contains fixes for problems in the following components:

• Documentation
• Enterprise Generation Language (EGL)
• Globalization
• J2EE development
• Model publishing
• Modeling
• Patterns
• Portal tools
• Rational database tools
• Team programming with Rational ClearCase
• Test and deployment tools
• UML diagrams
• UML to Java
• UML to EJB
• Visual Editor for Java
• Web services tools
• Web tools
• XML tools

Documentation

• This iFix contains the most up-to-date English documentation for Rational Software Architect.
• The broken links in the modeling cheat sheets have been fixed. All links now reference valid help topics.

Enterprise Generation Language (EGL)

The compile-time error whereby a spurious '$' was generated in diffhandlers in projects which used an EGL backend has been fixed. Diffhandlers now are generated correctly with a '.' in place of the '$' when referencing inner classes.

Globalization

This fixes many problems relating to missed or incorrect translations for the Japanese localization.

J2EE development

• A default module project name problem with EAR Import has been fixed. Incorrect logic was used to compute the project names such that duplicate project names were possible. For example, before the fix, if an EAR defined two module URIs as foo.1.jar and foo.2.jar, the project names for both were being computed as foo. With this fix, the project names are now computed as foo_1 and foo_2. The problem that caused EARs containing two module URIs like foo.1.jar and foo.2.jar to fail to deploy properly on WebSphere Application Server has also been fixed.
• The problem of Project Interchange Import (File > Import > Project Interchange) memory leak has been fixed. A similar memory leak when importing various Samples from the Samples Gallery has also been fixed.

Model publishing

The following problem has been fixed: Due to an issue with the default Web browser in Eclipse, when the Automatically display published output check box is selected, the generated HTML or PDF output might not display.

Modeling

• The problem has been fixed where full localization was not supported for user-created profiles of a model.
• The problem with the Architectural Discovery rule "Package Local Breakable" where the dependencies between packages are shown in the reverse direction has been fixed.
• The problem where errors are not corrected by the Quick Fix wizard on model validation errors, in the Problems view, has been fixed.
• The following problem has been fixed: When you perform an operation in one model that results in a change to another model, the related cross model reference is not resolved. An unresolved reference appears in a diagram as a circle with a red X through it.
• The following problem has been fixed: If a space or special character is used in the stereotype attribute's name in a profile, a model that has the profile applied might not open.
• The following problem has been fixed: Sharing a project through team support with open UML models is inconsistent with other file location altering actions, such as the Save As functionality. Certain source control settings are ignored.
• The following problem has been fixed: When you compare a model with its local history, and the model contains a pattern with template parameters that point to a deleted model, the comparison fails and an error is logged.
• The problem has been fixed where the export of a model with applied stereotypes, such as a model with documentation, to Ecore would fail and log an error.
• The following problem has been fixed: When you compare or merge versions of a model, certain combinations of deltas and user selections of Accept and Reject can cause data loss. For example, if you accept the move of an element into a new package, but reject the addition of the new package, the moved element is lost.

Patterns

• The problem with the pattern parameter HandleRequest from the Chain of Responsibility pattern has been fixed. The pattern parameter now generates the correct Java source code for the operation parameter type after a UML to Java transformation.
• The following problem has been fixed: When a UML model contains a pattern instance with a hard-coded reference to its associated pattern definition, and the model is imported into another instance of Rational Software Architect, if the hard-coded reference is no longer valid the model does not open.
• The following problem has been fixed: When deployed pattern plug-in projects have missing or re-versioned pattern .rmd files, or missing or deleted parameters from the pattern .rmd file when redeployed to the same location, the project’s .emx file might not open.
• A memory leak in the Pattern Explorer has been fixed.
• The problem has been fixed where, on non-English operating systems, the Model Explorer view displays pattern definitions.

Portal tools

Private and derived portal pages are now excluded in a portal project after importing from a portal server. These pages cannot be deployed and previously caused errors due to visibility and access control when deploying portal projects.

Rational database tools

• When this fix is installed, it allows the user to specify a schema in the SQL Wizard and SQL Query Builder. This user-specified schema will be assumed for all unqualified tables and tables qualified with this schema will have the schema removed after parsing. Instructions for activating this fix are included in a document entitled “Omitting the current schema qualifier in SQL statements” on the Rational Software Architect for WebSphere Support and downloads site
• SQLJ plugin has been changed to generate a unique default package name regardless of case.

Team programming with Rational ClearCase

• The problem where the disablement of the ClearCase SCM Adapter capability was not persistent between workbench sessions has been fixed.
• The problem where a dialog prompting for product instance location for the ClearCase Typemanager is presented to the user upon each new workspace creation even if ClearCase is not installed has been fixed.

Test and deployment tools

The following problems found in Application Server Toolkit V6.0 have been fixed:

• J2EE Ant Exports fail.
• Ant task regenerateAccessBean can not read accessbeandictionary.xml.
• EJBs implementing TimedObject fails with incremental deploy.
• Datastore does not support the access intent for Custom Finder.
• Internal error in mapping metadata - LINK is a reserved word.
• Composer fields IsNull value are not set in CacheImpl setter.
• CacheImpl is not setting is Null.
• Function set for SQLJ DB2 V8.2 fails customization.
• Configuration support for iSeries^TM.
• Empty list of predicate col names for EJB 1.1 root-leaf.
• Problems when deploying DB2 Reg. on top of an existing Reg.
• Cannot continue WS creation scenario when using HTTP Basic Authentication.
• WSDL2Java generates bad code
• Exception in client scenario if WSDL has no SOAP bindings.
• Missing noWrappedOperations to WSDK.
• Port CTC XSD bean fixes.
• Incorporate WebSphere Application Server 5.1.1.1 emitter upgrade.
• Two issues with using the Web Service creation wizard to generate a Web service that runs on WebSphere application server. Without this fix, there are two cases where the user will receive a WebSphere exception and be unable to proceed through the wizard.

UML diagrams

• The problem where a UML Class diagram containing a data model element from another project that could not be found resulted in many exceptions being logged, creation of large log file and potentially very long durations to open a diagram has been fixed.
• The following problem has been fixed: When working with the cascading style sheet (CSS) editor and a UML2 diagram editor for modeling or visualization, when the CSS editor is closed, several error exceptions are reported in the .log file and the following error message displays: "An error has occurred. See the error log for details." Clicking elsewhere in the product will cause the same sequence of error messages to display.
• The problem where the Component shape on a UML diagram did not show a stereotype image has been fixed
• The problem where occasionally the product would enter a deadlock when attempting to visualize a Java method in a UML Sequence Diagram has been fixed.
• The problem where the top portion of lifeline header names in a UML Sequence Diagram was truncated when using Korean text has been fixed.
• The problem where the top portion of operation names in Compartment shapes of a UML diagram was truncated when using Korean has been fixed.
• The problem that restricted the location of localized UML model profiles to a directory name containing "/profiles". This restriction has been removed.
• The problem where an attempt to save a UML modeling topic diagram (.tpx) as a UML visualization diagram (.dnx) fails and an error is logged has been fixed.
• The problem when creating an "extends" relationship between Java interfaces on a UML Class Diagram, if the super (target) interface is a binary Java type (available in the workspace through a referenced JAR), then unwanted method stubs are created in the (sub)interface has been fixed. These method stubs are for the methods declared in the super interface(s).
• This fixes a problem on a UML Class diagram when a method is dragged from a Java class and dropped on another class resulting in the method not being removed from the original class and a method with a blank body being created in the new class. The code body of the method was lost. This operation is not a supported operation and has been disabled.
• The problem where a Java "pull-up" refactor in the Java editor was not reflected in a UML Class diagram that visualized the class has been fixed.
• The problem where a compare or merge command launched externally by ClearCase^® on a modeling or visualization artifact failed on Windows Operating Systems set to a language that translates the user's "Application Data" directory has been fixed.
• The problem where changes to the Page Setup dialog for printing UML Diagrams were ignored has been fixed.
• The problem where UML Modeling editors would not recognize .xmi file types has been fixed.
• The problem where registration of new model types was not extensible has been fixed.
• The problem where navigating through a Browse Diagram of Java or UML classes always used the default relationship selections instead of the users last selection has been fixed.
• The default layout preference in the Diagram Navigator of 'Hierarchical' has been changed to 'Flat'.
• The problem where bookmarks on UML Sequence Diagrams would be deleted when geometric shapes were added to the diagram has been fixed.
• The problem where a refactor operation that would result in modification of a UML visualization class diagram would fail if the diagram file was under source control and not checked out has been fixed.
• The problem where changing the generalization (inheritance) relationship from one UML class or Java class on a UML Class Diagram can result in the diagram not showing the change that occurred in the underlying model or class has been fixed.
• The problem where errors occurred in some situations of deleting an Enterprise Java Bean project containing UML Class diagrams that are open has been fixed.
• The following problem has been fixed: In the Show Related Elements and Topic Diagrams features, the user might click a stopping condition in the stopping list for the purposes of traceability. When either the Implementation or Specifications item in the list is clicked, the correct result is not obtained.
• The problem has been fixed where a connector would disappear or not be shown on an Activity diagram if it crossed a partition.

UML to Java

The problem with UML to Java transformations removing methods that contain user-written code has been fixed.

Important: These transformations remove a method only if all of the following conditions are true:

• The method has an @generated tag.
• The method is not present in the corresponding UML class.
• The Java method does not have a block of code surrounded by the following comments: //begin-user-code and //end-user-code.

UML to EJB

The problem with UML to EJB transformations removing methods that contain user-written code has been fixed.

Important: These transformations remove a method only if all of the following conditions are true:

• The method has an @generated tag.
• The method is not present in the corresponding UML class.
• The Java method does not have a block of code surrounded by the following comments: //begin-user-code and //end-user-code.

Visual Editor for Java

The problem where the specification of a parameter or exception in a method declaration of a Java Interface class in the New Java Interface Wizard was ignored and not added to the generated interface has been fixed.

Web services tools

• When using the Web service wizards to process WSDL served from a site protected by HTTP Basic Authentication, the wizards will ask for a user ID and password, but will subsequently not allow you to proceed beyond the third page of the wizard (the server/runtime configuration page). This has been fixed for the WebSphere^® (J2EE) Web services scenarios. For Apache Axis and Apache or IBM SOAP scenarios, you will need to download a local copy of the WSDL to your workspace and then launch the wizard to process the local copy.
• When using the Web service wizard to create a URL or DADX Web service and client for a  v5 server, the wizard will fail part way through processing, at the point it first attempts to generate the Web service client. The failure occurs after clicking Next to leave the Binding Proxy Generation page, and is manifested by an error dialog with the message "IWAB0222E Error encountered while analyzing WSDL file" and a java.lang.NullPointerException in the dialog's details section. This problem occurs because the wizard attempts to retrieve the service's WSDL at a point when the server hosting the WSDL is in the stopped state. This has been fixed. The wizard will ensure the server is in the started state before attempting to retrieve the WSDL in order to generate the Web service client.
• If you launch a Web service wizard from the Web Services Explorer, the wizard dialog appears "on top" of all other windows on your desktop and cannot be minimized or positioned behind any other windows, including the main Rational^® Software Architect or Rational Web Developer workbench window. Furthermore, if an error occurs during processing by the wizard, the error dialog will appear behind the wizard; however, you will not be able to see or dismiss the error dialog and you will not be able to move or exit out of the wizard. The only workaround is to stop the Rational Software Architect or Rational Web Developer process. This has been fixed. The wizards launched from the Web Services Explorer no longer monopolize the desktop.
• When using the Java^TM beans for XML Schema wizard to generate Java beans from schema containing complexType extensions and abstract complexTypes, compilation errors in the generated Java may result due to duplicate methods and other Java symbols. This is now fixed. In addition, the Java code generated by the wizard for a schema may fail to properly deserialize XML instance documents containing prefixed elements. In particular, none of the child elements beneath an element with a prefix will be deserialized into Java objects. The result is an incomplete collection of Java objects corresponding to the instance document. This also is now fixed.
• If you create a Web service top down from WSDL and XML Schema, first change the schema then recreate your Web service. The wizard will not regenerate the Java beans and skeleton for your Web service; however, it will regenerate fresh deployment files, resulting in compilation errors due to the old Java beans and skeleton being out of synchronization with the new deployment files. The wizard has been fixed to regenerate all the Java classes, including the deployment, bean, and skeleton classes.
  Important: With the application of this fix, the wizard will replace your previous skeleton class and any business logic within it by a fresh skeleton (provided you have enabled file overwriting). To help protect against the loss of your business logic, your previous skeleton class will be copied to a backup file before it is overwritten. The backup file is stored in the same folder as your skeleton, and is named after your skeleton .java file but with the additional suffix ".bak". At most one such backup is produced.
• The Java2WSDL and WSDL2Java emitters within the Web services GUI tools in WebSphere Studio Application Developer have been upgraded based upon the Java2WSDL and WSDL2Java emitters from WebSphere Application Server 5.1.1 Cumulative Fix 1 (5.1.1.1) amended with a few additional emitter fixes.
  Important: After applying this upgrade, the code generated by the Web services tools may not compile against WebSphere Application Server v5.0.2, which is the level of the v5.0 Unit Test Environment (UTE) in Software Architect. Should this occur, apply WebSphere Application Server 5.0.2 Cumulative Fix 8 (5.0.2.8) to your UTE and to any other installed v5.0.2 servers as necessary.
• The WSDL2Java tool included with WebSphere Application Server features a "-noWrappedOperations" option used to trigger generation of request and response beans for top-level complexTypes and complexType elements referenced by WSDL operations. This option has not previously been available to users of Software Architect. It is now available via Window > Preferences > Web Services > Code Generation > IBM WebSphere runtime > Generate Java from WSDL using the no wrapped style.
• Software Architect does not handle WSDL and XML Schema include and import elements that use relative location URIs that reach across directories. The WSAD Web service wizards will generally fail with an error similar to this example: "IWAB0529E Error in resolving WSDL file ../myfolder/myfile.xsd, import WSDL file must have absolute URL or relative URL in the same directory". This limitation is now resolved, with the caveat that the top-level WSDL document must not attempt to refer, directly or indirectly, to any other WSDL or XML Schema document not located in, or beneath, the top-level WSDL document's directory. In other words, the root WSDL document must exist at the top of the tree of all WSDL and XML Schema documents upon which it depends.
• Given a schema complexType containing two or more elements of the same name, the Java beans for XML Schema wizard will generate a bean class with duplicate getters and setters with identical names and signatures, resulting in a Java compilation error. This has been fixed. The wizard will now generate single indexed getter and setter methods in which the index identifies the specific occurrence of the element to get or set.
• The problem that WSDL validator may report that a WSDL file is not valid if it contains an inline schema with a restriction pattern which includes a colon has been fixed.
• The problem that WSDL validator may report that an imported WSDL file is not valid when it is valid has been fixed.
• The problem that WSDL validator may report schemas imported by inline schemas as not valid when they are valid has been fixed.
• The problem in the WSDL Editor where Extensibility Elements in a WSDL file may appear twice has been fixed. A related problem of the inability to add Extensibility Elements under another Extensibility Element in a WSDL file has also been fixed.
• When a WebSphere Version 6 DB2^®-based UDDI registry is deployed on top of a Cloudscape-based one, there was a problem where the registry became inaccessible. This has been fixed.
• Creation of a WebSphere-based Web Service skeleton or client from a WSDL document that is protected via HTTP Basic Auth is no longer blocked.
• The problem where deploying a Web service results in the creation of a bad java.lang.tring_Deser deserializer class has been fixed.
• The exception which occurs when attempting to create a WebSphere-based Web service skeleton or client using a WSDL document that does not contain a SOAP binding has now been resolved.
• The -noWrappedOperations WSDL2Java option is now available in the WSDL2WebService and WSDL2Client commands.
• Some cases where the XSD to Java bean generator generated a Java bean with duplicate methods have been resolved.

Web tools

• Content assist was not proposing custom tag attributes in JSPs. This is now fixed.
• Variables declared by custom tags were not being recognized in JSPs. This is now fixed.
• The problem that when nothing is selected in a selectOne component, it will cause a validation error "Value is not valid" on submit has been fixed.
• The problem that when facesContext.getExternalContext().redirect() is called in an action of JSR 168 Faces portlet IllegalStateException occurs has been fixed.
• The http-method declaration of web.xml files for the Servlet 2.2 and 2.3 specifications were restricted to valid HTTP 1.1 methods as defined by the Servlet 2.4 specification. Since the values are less strictly defined by the 2.2, 2.3 DTDs, some customers had existing applications that were dependent on other protocols, such as WebDAV. The restriction was expanded to include these WebDAV values. Additionally, SIP protocol values were added in anticipation that existing customers may also be using those values. Servlet 2.4 applications will continue to be restricted by the XML Schema definition provided by the specification.
• In the Page Designer, changing alignment of the TABLE tag by the Properties View sometimes generates a page with an error. In XHTML pages, the align attribute of the DIV tag is invalid, but you can add a DIV tag with an invalid align attribute into a page as a parent of the TABLE tag by the Properties View. These problems have been fixed.
• In the Page Designer, jsp:setProperty tag doesn't have a 'name' attribute when the tag is inserted to a JSP page as a child node of jsp:useBean tag by the Properties view. The jsp:setProperty tag should have 'name' attribute of which value is the same as the value of 'id' attribute of the parent jsp:useBean tag. The absence of the 'name' attribute in the jsp:setProperty tag causes a compile error in the JSP page. This problem has been fixed.
• The problem that incorrect IDs generated by JSF runtime for nested data tables has been fixed.
• The problem where a tag library descriptor (.tld) file placed in the WEB-INF folder of a web project would not be recognized by the JSP compiler, links validator and source editor content assist has been fixed.
• The following problem has been fixed: An input date field with inputHelperAssist enabled and custom format set to a pattern that does not include a separator between day, month and year, e.g. ddMMMyyyy changes the year in the date entered to the current year when focus moves off the field e.g. entered value 01Jan1999 would change to 01Jan2005.
• The following problem has been fixed: A Data Grid containing a Web Style pager had a problem where navigating back to a previous page using a browser control (e.g. 'Back' button) would cause unexpected results e.g. click page sequence 1,3,5 then using back button to go back to page 1 and clicking an action within the Data Grid would cause page 3 to be displayed when it should stay at page 1.

XML tools

• In the J2EE XML specifications, some constraints are required to be enforced by vendors (opposed to being enforced by the governing DTD or XSD). Some of these were disabled with the V6 release, and we are now re-instating the applicable validation. You will not notice a change as this is required primarily by certification testing for J2EE specification compliance.
• The problem in XML editor that a drag and drop operation performed by holding the CTRL key may perform a move operation instead of a copy operation has been fixed.

2.0 Known limitations, problems, and workarounds

The solution to the problem described in the Model publishing section causes another issue where, on some Linux operating systems, generated HTML or PDF output does not open in a Web browser. To work around this issue, open a Web browser, navigate to the generated output and open the index.html file.

3.0 Installation prerequisites

This interim fix is approximately 350 MB. To download and install the interim fix you will require approximately 700 MB of disk space.

Depending on your computer's processor speed, amount of RAM, and the speed of your internet connection, the interim fix might take an extended period of time to download and install.

Attention: Do not cancel the installation of the interim fix once started.

4.0 Customer support

For product news, events, support, and other information, see the Rational Software Architect home page at www.ibm.com/software/awdtools/architect/swarchitect/.

For technical articles, tutorials, samples, and previews of new IBM Rational technology, see www.ibm.com/developerworks/rational/.

5.0 Notices and trademarks

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Intellectual Property Dept. for Rational Software
IBM Corporation
20 Maguire Road
Lexington, MA
02421-3112
USA

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this documentation and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples may include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

(C) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (C) Copyright IBM Corp. 2000, 2005. All rights reserved.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Programming interface information

Programming interface information is intended to help you create application software using this program.

General-use programming interfaces allow you to write application software that obtain the services of this program's tools.

However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.

Trademarks and service marks

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:

• ClearCase
• Cloudscape
• DB2
• IBM
• iSeries
• Rational
• WebSphere

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel is a trademark of Intel Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product or service names, may trademarks or service marks of others.