IBM Support

PM55007: RSA4WS:UML to WSDL, JNPE element executing source org.eclipse.uml2.uml.internal

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This is a namespace prefix conflict problem. The namespace
    prefix for wsdl is generated as tns and the namespace prefix for
    the 'Create Snapshot' schema  used by the Service
    Interface(source of the transform) is also set as tns in the
    stereotype property.I think the same prefix is used within the
    schema tags in the wsdl file as well and this causes problem
    when the wsdl files and schemas are finally persisted in the
    end.The problem happens during the fetch of QName qualifier for
    the xsd request element.The issue is in the eclipse xsd code,
    since there are two namespace(conflict) with the same prefix it
    always resolves it to the namespace of wsdl as parent and not
    the xsd namespace due to which the right QNames could not be
    fetched and it ends with the NPE.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    tns is the default namespace prefix used by WSDL and if the
    same namespace prefix was being used by the inline schemas
    within the WSDL to refer to schema with namespace prefix as
    tns.
    

Problem conclusion

  • tns is the default namespace prefix used by WSDL and if the
    same namespace prefix is used by the schemas referred within
    the WSDL then the inline schema should not use the same
    namespace prefix(i.e. tns) as it is.This is because it
    causes conflicts with WSDL namespace, and during element
    lookup for the xsd element the WSDL namespace is always used
    and the  correct XSD namespace is never found. This results
    in JNPE during lookup.See WI 85851 for more details.Hence
    using tns1 instead of tns when tns is encountered within
    inline schema.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM55007

  • Reported component name

    SW ARCHITECT WI

  • Reported component ID

    5724I7001

  • Reported release

    804

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-12-23

  • Closed date

    2012-06-20

  • Last modified date

    2012-06-20

  • 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

  • R804 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYKBQ","label":"Rational Software Architect Designer for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"804","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4JCV","label":"Rational Software Architect for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"804","Edition":"","Line of Business":{"code":"LOB15","label":"Integration"}}]

Document Information

Modified date:
20 June 2012