IBM Support

JR41725: Input/Output types are not generated properly if an in-line schema(located in a WSDL) references other schemas that are

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The WSDL discovery feature in Process Designer has problems
    with WSDLs that have in-line schema referencing outside schemas.
    
    Process Designer reports the WSDL as invalid and throws the
    following exception:
    
    CWLLG2229E: An exception occurred in an EJB call.  Error:
    Unable to find definition of element:
    {<wsdl_URL>/}execute
    
    com.lombardisoftware.core.TeamWorksException: Unable to find
    definition of element:
    {<wsdl_URL>/}execute
     at
    com.lombardisoftware.server.eai.soap.wsdl.TWWSDLDataBuilder.getE
    lementType(TWWSDLDataBuilder.java:768)
    
    
    Users will also see typeMismatch errors in response when
    invoking a service, for example:
    
    CWLLG0391E: An update operation failed.
    
    com.lombardisoftware.core.TeamWorksRuntimeException:
    com.lombardisoftware.core.TeamWorksException: Type mismatch.
    Expected "tw.object.String" type, but found "org.jdom.Element"
    java class. Value: "[Element: <token/>]"
     at
    com.lombardisoftware.core.TeamWorksRuntimeException.asTeamWorksR
    untimeException(TeamWorksRuntimeException.java:65)
    

Local fix

  • edit the wsdls
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of BPM Express, Standard and          *
    *                  Advanced.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Input/Output types are not generated    *
    *                      properly if an in-line schema(located   *
    *                      in a WSDL) references other schemas     *
    *                      that are outside the WSDL               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The WSDL discovery feature in Process Designer has problems
    with WSDLs that have in-line schema referencing outside
    schemas.
    

Problem conclusion

  • Fixed the problem in WSDL discovery and enable full WSDL/XSD
    tree loading/parsing and generate the variables correctly for
    both input and output parameters.
    
    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 as follows:
    - Install JR42012 on both Process Designer and Process
    Center/Server using IM
    - On Process Center/Server run bpmprofileUpgrade as outlined in
    http://www-01.ibm.com/support/docview.wss?uid=swg27022245#recove
    rFailure
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR41725

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-01-20

  • Closed date

    2012-03-16

  • Last modified date

    2012-04-18

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

  • Fixed component ID

    5725C9400

Applicable component levels

  • R750 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1"}]

Document Information

Modified date:
07 October 2021