PI42484: UML2WSDL: MULTIPLE PACKAGES TO THE SAME XSD FILE, DIFFERENCE IN BEHAVIOR

Rational Software Architect Designer 9.5.0
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 Designer for WebSphere Software Fix Pack 1 (9.5.0.1) for 9.5.0
Rational Software Architect Designer for WebSphere Software 9.5.0
Rational Software Architect Designer Fix Pack 2 (9.5.0.2) for 9.5.0
Rational Software Architect Designer for WebSphere Software Fix Pack 2 (9.5.0.2) for 9.5.0
Rational Software Architect Fix Pack 2 (9.1.2.2) for 9.1.2
Rational Software Architect Designer for WebSphere Software Fix Pack 3 (9.5.0.3) for 9.5.0
Rational Software Architect Designer Fix Pack 3 (9.5.0.3) for 9.5.0
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

• When generating the contents of multiple packages to the same
  XSD file, there is a difference in behavior between the UML2WSDL
  and the UML2XSD transformations.
  
  Steps to reproduce:
  Configure both a UML2WSDL and a UML2XSD transformation
  configuration, so that two packages are generated into the same
  xsd file.
  Run the UML2WSDL transformation and validate the result -->
  There are plenty of errors.
  Run the UML2XSD tranformation and overwrite the xsd result, and
  validate --> No validation error.
  

Local fix

• Run the UML2XSD tranformation and overwrite the xsd result, and
  validate --> No validation error.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * -                                                            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * "When generating the contents of multiple packages to the    *
  * same XSD file, the customer saw a difference in behavior     *
  * between the two transformations (1st to WSDL and then to     *
  * XSD) .The problem in this case is that the BaseClass was not *
  * getting transformed                                          *
  * When we overwrite the main xsdƒ  s with the UML2XSD TC       *
  * results, then the validation succeeds without a problem.     *
  * "                                                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• When generating the contents of multiple packages to the same
  XSD file, the customer saw a difference in behavior between the
  two transformations (1st to WSDL and then to XSD) .The problem
  in this case is that the BaseClass was not getting transformed.
  When we overwrite the main xsdƒ  s with the UML2XSD TC results,
  then the validation succeeds without a problem.  Now, BaseClass
  is also transformed in case of XSD transformation and hence
  Validation succeeds for all XSDs generated
  

Temporary fix

Comments

APAR Information

• 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 PSY

     UP

• R910 PSY

     UP

• R911 PSY

     UP

• R912 PSY

     UP