PM21772: The JAX-RPC WSDL2Java tool generates an incorrect method signature for an element that has maxOccurs="unbounded".

Fixes are available

APAR status

Closed as program error.

Error description

If a WSDL operation uses the document/literal wrapped style,
then there is a corresponding schema element that defines the
parameters.  The WSDL2Java tool will generate a java method
signature representing the schema element.

This schema element to method signature mapping includes a
special mapping for arrays.

For example:

<xsd:element name="myMethod">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="param1" type="xsd:string">
<xsd:element name = param2">
<xsd:complexType>
<xsd:sequence>
<element name="data" type="xsd:string"
maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>

Causes WSDL2Java to generate a method similar to:

public void myMethod(String param1, String[] param2);


Problem:

If the param2 element is changed to include
maxOccurs="unbounded", the mapping from WSDL2Java is
incorrect.

Example:

<xsd:element name="myMethod">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="param1" type="xsd:string">
<xsd:element name = param2" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<element name="data" type="xsd:string"
maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>


The incorrect method produced by WSDL2Java is:

public void myMethod(String param1, String[] param2);

The expected method is:

public void myMethod(String param1, String[][] param2);


The invalid method can cause compilation errors, or unexpected
runtime errors.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V6.1 and   *
*                  V7.0 users of JAX-RPC                       *
****************************************************************
* PROBLEM DESCRIPTION: The WSDL2Java tool produces an          *
*                      invalid method signature                *
****************************************************************
* RECOMMENDATION:  Install a fix pack containing this APAR and *
*                  regenerate the application with the         *
*                  command line or WSAD tooling.               *
****************************************************************
If a WSDL operation uses the document/literal wrapped style,
then there is a corresponding schema element that defines the
parameters.  The WSDL2Java tool will generate a Java method
signature representing the schema element.

This schema element to method signature mapping includes a
special mapping for arrays.


For example:

<xsd:element name="myMethod">
 <xsd:complexType>
  <xsd:sequence>
   <xsd:element name="param1" type="xsd:string">
   <xsd:element name = param2">
    <xsd:complexType>
     <xsd:sequence>
      <element name="data" type="xsd:string"
               maxOccurs="unbounded" />
     </xsd:sequence>
    </xsd:complexType>
   </xsd:element>
  </xsd:sequence>
 </xsd:complexType>
</xsd:element>

Causes WSDL2Java to generate a method similar to:

   public void myMethod(String param1, String[] param2);


Problem:

If the param2 element is changed to include
maxOccurs="unbounded", the mapping from WSDL2Java is
incorrect.

Example:

<xsd:element name="myMethod">
 <xsd:complexType>
  <xsd:sequence>
   <xsd:element name="param1" type="xsd:string">
   <xsd:element name = param2" maxOccurs="unbounded">
    <xsd:complexType>
     <xsd:sequence>
      <element name="data" type="xsd:string"
               maxOccurs="unbounded" />
     </xsd:sequence>
    </xsd:complexType>
   </xsd:element>
  </xsd:sequence>
 </xsd:complexType>
</xsd:element>


The incorrect method produced by WSDL2Java is:

  public void myMethod(String param1, String[] param2);

The expected method is:

  public void myMethod(String param1, String[][] param2);


The invalid method can cause compilation errors, unexpected
runtime errors or silent (but invalid) operation.

This problem can also occur if using Rational Application
Developer to generate the Web Service.

Problem conclusion

The WSDL2Java tool is changed to recognize the maxOccurs
setting on the xsd:element and choose the correct mapping.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.35 and 7.0.0.15.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM21772
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-09-01
Closed date
2010-09-17
Last modified date
2010-10-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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM21772: The JAX-RPC WSDL2Java tool generates an incorrect method signature for an element that has maxOccurs="unbounded".

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?