IBM Support

OA41071: JAVA CODE GENERATOR NOT ABLE TO GENERATE SOAP CLIENT CODE FROM S AMPLE WSDL FILES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WSDL files znvwsdl1.wsdl and znvwsdl2.wsdl do not generate a
    useable SOAP client.
    

Local fix

  • none at this time.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the Tivoli NetView for z/OS     *
    *                 web services gateway sample WSDL files,      *
    *                 znvwsdl1.wsdl and znvwsdl2.wsdl, to          *
    *                 generate code for SOAP clients               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Sample Web Services Description         *
    *                      Language (WSDL) files znvwsdl1.wsdl     *
    *                      and znvwsdl2.wsdl do not comform to     *
    *                      the web services interoperability       *
    *                      (WS-I) basic profile, which causes      *
    *                      the following symptoms to occur.        *
    *                      1. Some code generation tools, such     *
    *                      as Apache Axis2 WSDL2Java, will         *
    *                      indicate there is no element type       *
    *                      for the NVCMDRequest message and        *
    *                      will generate no code from the          *
    *                      sample WSDL                             *
    *                      2. WS-I basic profile conformance       *
    *                      scanning tools indicate that the        *
    *                      sample WSDL fails test assertions       *
    *                      BP2012 and BP2113                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Samples znvwsdl1.wsdl and znvwsdl2.wsdl define SOAP message
    parts with part elements.  Because the part elements specify the
    "type" attribute, instead of the "element" attribute, they fail
    web services interoperability (WS-I) basic profile checking.
    Any code generator tools, such as Apache Axis2 WSDL2Java, that
    enforce WS-I basic profile conformance will fail to generate
    code in that situation.
    A failed attempt to generate Java code using either sample,
    znvwsdl1.wsdl or znvwsdl2.wsdl, with Apache Axis2 WSDL2Java
    is illustrated by the following excerpt from the trace of the
    Java exception thrown by WSDL2Java (formatted to fit the
    problem summary):
    Exception in thread "main"
    org.apache.axis2.wsdl.codegen.CodeGenerationException: Error
    parsing WSDL
            at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.
               <init>(CodeGenerationEngine.java:175)
            at org.apache.axis2.wsdl.WSDL2Code.
               main(WSDL2Code.java:35)
            at org.apache.axis2.wsdl.WSDL2Java.
               main(WSDL2Java.java:24)
    Caused by: org.apache.axis2.AxisFault: No element type is
      defined for message NVCMDRequest
    

Problem conclusion

  • Through CMVC defect OA41071, samples znvwsdl1.wsdl and
    znvwsdl2.wsdl are being changed to define their elements in
    conformance with the WS-I basic profile.  One noteworthy
    result of the changes will be the different structure of the
    SOAP request body that each sample defines.
    The format of the SOAP request body defined by each original
    sample is as follows (formatted for readability):
    <NVCMD>
      <Name>operator_id</Name>
      <Password>password</Password>
      <cmd>netview_command</cmd>
    </NVCMD>
    The format of the SOAP request body that will be defined by
    each changed sample is as follows (formatted for readability):
    <znv:NVBODY>
      <Name>operator_id</Name>
      <Password>password</Password>
      <NVCMD>
        <cmd>netview_command</cmd>
      </NVCMD>
    </znv:NVBODY>
    Both SOAP request body formats are acceptable to the NetView
    web services gateway (a.k.a. NetView SOAP server).
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA41071

  • Reported component name

    NETVIEW FOR Z/O

  • Reported component ID

    5697NV600

  • Reported release

    10B

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-12-19

  • Closed date

    2013-02-27

  • Last modified date

    2013-05-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UA68188

Modules/Macros

  • IHSSOA06 IHSSOA07
    

Fix information

  • Fixed component name

    NETVIEW FOR Z/O

  • Fixed component ID

    5697NV600

Applicable component levels

  • R10B PSY UA68188

       UP13/04/16 P F304

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJDU","label":"IBM Z NetView"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10B","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10B","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 May 2013