IBM Support

JR41344: Failure in discovery of WSDL file if it contains multiple schemas that have the same namespace.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Steps to reproduce the problem:
    1. Implement a web service integration service in Process
    Designer
    2. On Discovery tab, discover a WSDL that contains multiple
    schemas that have the same namespace.
    
    An Error occurs on discovery, Process Designer will show an
    error similar to:
    "Error occurred in trying to detect the service...Please check
    whether WSDL is effective, or not"
    and the server system out log would show:
    E CWLLG2229E: An exception occurred in an EJB call.
    Error:file:<xxx.xsd>:src-resolve: Cannot resolve the name
    'xxx' to a 'type definition' component.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of BPM Express, BPM Standard and BPM  *
    *                  Advanced.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Steps to reproduce the problem:         *
    *                      1. Implement a web service              *
    *                      integration service in Process          *
    *                      Designer                                *
    *                      2. On Discovery tab, discover a WSDL    *
    *                      that contains multiple                  *
    *                      schemas that have the same namespace.   *
    *                      An Error occurs on discovery, Process   *
    *                      Designer will show an                   *
    *                      error similar to:                       *
    *                      "Error occurred in trying to detect     *
    *                      the service...Please check              *
    *                      whether WSDL is effective, or not"      *
    *                      and the server system out log would     *
    *                      show:                                   *
    *                      E CWLLG2229E: An exception occurred     *
    *                      in an EJB call.                         *
    *                      Error:file:<xxx.xsd>:src-resolve:       *
    *                      Cannot resolve the name                 *
    *                      'xxx' to a 'type definition'            *
    *                      component.                              *
    *                      The problem is with the way the XSDs    *
    *                      are imported using a single             *
    *                      namespace. The parser                   *
    *                      fails when trying to resolve one of     *
    *                      the schema namespace as it expects      *
    *                      the schemas to be in different          *
    *                      namespace.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An Error occurs on WSDL discovery, Process
    Designer will show an
    error similar to:
    "Error occurred in trying to detect
    the service...Please check
    whether WSDL is effective, or not"
    and the server system out log would
    show:
    E CWLLG2229E: An exception occurred
    in an EJB call.
    Error:file:<xxx.xsd>:src-resolve:
    Cannot resolve the name
    'xxx' to a 'type definition' component.
    The problem is with the way the XSDs
    are imported using a single
    namespace. The parser
    fails when trying to resolve one of
    the schema namespace as it expects
    the schemas to be in different
    namespace.
    If a wsdl imports 2 different schemas that
    have the same namespace:
    Example:
    <xsd:import namespace="http://Router"
    schemaLocation="CalcOut.xsd"/>
    <xsd:import namespace="http://Router"
    schemaLocation="CalcIn.xsd"/>
    This is not a best practice and should be
    avoided. There are a number of vendors
    that do not support this style.
    Best practices suggest that when using <import>, the XSDs are
    typically from heterogenous namespaces but when using
    homogenous namespace approach such as the ones being referred
    here it is best to use <include> option when referring schema
    elements inside the WSDL.
    However, this style is legal. A schema can
    be split over multiple files and this is
    an appropriate way to import the schema.
    

Problem conclusion

  • WSDL Discovery was fixed to tolerate multiple schema names
    that have the same namespace.
    Interim fix is available in fix central for 7.5.0.1 and 7.5.1.
    
    On 7.5.1 The fix is available as a part of the JR42012 ifix
    package:
    http://www-01.ibm.com/support/docview.wss?uid=swg1JR42012
    and needs to be installed following the instructions outlined
    in JR42012.
    
    After installing this fix:
    - Copy the following XML and add it to the
    100Custom.xml under <properties> tag:
    <server merge="mergeChildren">
    <webservices merge="mergeChildren">
    <xsd-loader>
    <feature>http://apache.org/xml/features/honour-all-schemaLocatio
    ns</feature>
    </xsd-loader>
    </webservices>
    </server>
    (please copy the XML to a notepad first to get rid of any
    extra characters before pasting it in 100Custom.xml.
    
    100Custom.xml is located at:
     Standalone Profiles:
     Profile_home\config\cells\<~cellname~>\nodes\<~nodename~>\serve
    rs\<~servername~>\<~process-center/server~>\config\system\100Cus
    tom.xml
     Clusters:
     DMGR_home\config\cells\<~cellname~>\nodes\<~nodename~>\servers\
    <~servername~>\<~process-center/server~>\config\system\100Custom
    .xml
     (After making the changes to 100Custom.xml in the DMGR
    profile, make sure the changes get carried to the nodes by
    doing a force synchronize and restarting the DMGR)
    
    In version 7.5.0 Fix Pack 1 (7.5.0.1), this fix is available
    as a part of the JR42581 ifix package.
    JR42581 can be downloaded from Fix Central:
    http://www-933.ibm.com/support/fixcentral/swg/quickorder?parent=
    ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager
    +Advanced&release=7.5.0.1&platform=All&function=fixId&fixids=7.5
    .0.1-WS-BPM-IFJR42581&includeSupersedes=0&source=fc
    The installation instruction can be downloaded along with
    JR42581 ifix file.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR41344

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-12-01

  • Closed date

    2012-04-16

  • Last modified date

    2013-05-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

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 May 2013