PI42096: UML2WSDL transformation is generating incorrect import statements of an XSD to itself

Rational Software Architect Designer 9.5.0
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 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

APAR status

• Closed as program error.

Error description

• Abstract:
  UML2WSDL transformation is generating incorrect import
  statements of an XSD to itself
  
  Error Description:
  - A ??schema?? stereotype defines the namespace for a package.
  - In the transformation, the different .xsd and the .wsdl file
  for the package are set to the same namespace.
  - The resulting ??schema name??.xsd gets an incorrect import,
  which should not be there at all.
  Example: '?xsd:import namespace='??namespace path??'
  schemaLocation=''/?'
  
  Local Fix:
  Remove the incorrect import after transformation.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * -                                                            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Customer ran into an issue where an import is generated in   *
  * one of the XSDƒ  s, which is incorrect (should not be        *
  * present). Just removing the import resolved  the issue, but  *
  * this involved manual action and the customer didnƒ  t want   *
  * to post-process the schema in their model-driven approach.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Customer ran into an issue where an import is generated in one
  of the XSDƒ  s, which is incorrect (should not be present). Just
  removing the import resolved  the issue, but this involved
  manual action and the customer didnƒ  t want to post-process the
  schema in their model-driven approach.  Now, we have ensured
  that the namespaces are processed in a way that self import is
  avoided there-by solving customer's problem
  

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

  RATL SW ARCHITE

• Fixed component ID

  5725A3000

Applicable component levels

• R900 PSY

     UP

• R910 PSY

     UP

• R911 PSY

     UP

• R912 PSY

     UP