Fixes are available
Rational Software Architect 9.1.1
Rational Software Architect for WebSphere Software 9.1.1
Rational Software Architect for WebSphere Software 9.1.2
Rational Software Architect 9.1.2
Rational Software Architect for WebSphere Software Fix Pack 1 (9.1.2.1) for 9.1.2
Rational Software Architect Fix Pack 1 (9.1.2.1) for 9.1.2
Rational Software Architect Fix Pack 2 (9.1.2.2) for 9.1.2
Rational Software Architect Fix Pack 3 (9.1.2.3) for 9.1.2
Rational Software Architect for WebSphere Software Fix Pack 1 (9.1.2.3) for 9.1.2
APAR status
Closed as program error.
Error description
In IBM Rational Software Architect (RSA), if you update the 'Properties ? XSD Schema ? Target Namespace' value in the model, the UML-to-XSD transformation configuration's (TC) 'Namespace' value in the 'Output Options' table will not be updated accordingly. The following steps reproduce the problem: 1. Create a UML project ? model 2. Apply the 'SoaML', 'WSDL Transformation', and 'XSD Transformation' profiles to the model 3. Add a folder called 'Test' to the project 4. Add a package 'Package1' to the model and apply the '??schema??' stereotype to it 5. Add a package called 'Package2' under 'Package1' 6. Add a class called 'Class1' under 'Package2' 7. Add operations and attributes to 'Class1' 8. Add a UML-to-XSD transformation to the project, making the model the 'Source' and the 'Test' folder the 'Target'. Make sure that 'Output Options ? Customize the output according to the entries in the following table' check box is checked. 9. Save all changes and run the transformation RESULT: The model is transformed into XSD folders and files, as expected 10. Click, for example, on the 'Package1' entry in the transformation configuration's 'Output Options' table and modify the 'Resource Location' value by typing, for example, 'TestPackage1' (without the quotation marks) into 'Append segment' when prompted. 11. Add, for example, 'http://TestModel2/Package1v1' (without the quotation marks) to Package1's 'Properties ? XSD Schema ? Target Namespace' in the UML model. Note that the value you enter here is a modification to the value in 'Output Options ? Namespace' for 'Package1' 12. Save all changes 13. Close ? reopen the transformation configuration and examine the 'Output Options' table --?Expected Result: The 'Namespace' value in the 'Package1' entry of the transformation configuration reflects the value in the model, namely 'http://TestModel2/Package1v1' added in Step 11. --?Actual Result: The 'Namespace' value in the 'Package1' entry of the transformation configuration has NOT been updated with the new value in the model. 14. Clear the 'Output Options ? Customize the output according to the entries in the following table' check box and then check this check box again RESULT: The correct 'Namespace' value for 'Package1' now appears ('http://TestModel2/Package1v1'), but the 'Resource Location' for 'Package1' reverts to the previous -- and now incorrect -- value. There is no workaround.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** In UML-to-XSD/WSDL transformation, if user checks "Output Options ? Customize the output according to the entries in the following table" check box in the transformation configuration editor, user can update/modify the namspace for each of the packages which would be transformed into a schema file. User can also specifify the target namespace from the stereotype properties page for each of the packages. If user updates the nasmpce in the properties and then closes and opens the transformation configuration editor, it keeps the old namspace specified for the corresponding package and thus the new value specified through the properties page does not get reflected in the configuration editor.
Problem conclusion
The solution is to get the target namespace specified in transformation configuration editor to get synced with the one specified in the model for each of the packages. The solution would work as follows: - If user specifies the target namespace in the UML packges stereotype properties and user opens closes/opens the TC, the namespace specified in package gets reflected in the TC and the corresponding value that was there in TC before gets lost - If user modifies the namespace in the TC for a package, saves it and closes/reopens the TC, the user entered value in TC gets lost. The value in the model gets displayed in TC. Thus the model specified value gets precedence over the TC specified value - If model specified target namespace for a package is blank, then only TC specified namespace gets precedence and preserved.
Temporary fix
Comments
APAR Information
APAR number
PI21310
Reported component name
SW ARCHITECT WI
Reported component ID
5724I7001
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-07-03
Closed date
2014-10-31
Last modified date
2014-10-31
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
SW ARCHITECT WI
Fixed component ID
5724I7001
Applicable component levels
R900 PSN
UP
Document Information
Modified date:
17 October 2021