PQ80083: WSAS 5.x Web Services IllegalArgumentException when request defined for desiredLocales, monOccurs=0

APAR status
Closed as program error.

Error description
User reports getting exception:
1. When I send the request(see below) without <desiredLocales
xsi:nil="true"/> I get an IllegalArgumentException. I get this
exception although in wsrp_v1_types.xsd(see below) for
desiredLocales,minOccures=0   is defined.  To get this exception
you need to call WSRP_V1_ServiceDescription_PortType.getServiceD
escription(...,desiredLocales,...) with String desiredLocales[]
= new String[]{};
 wsrp_v1_types.xsd
   <element name="getServiceDescription">
     <complexType>
       <sequence>
         <element name="registrationContext"
type="types:RegistrationContext" nillable="true"/>
         <element name="desiredLocales"      type="xsd:string"
minOccurs="0"  maxOccurs="unbounded"/>
       </sequence>
     </complexType>
   </element>
   <element name="getServiceDescriptionResponse"
type="types:ServiceDescription"/>
 Request:
 POST /wps/WSRPServiceDescriptionService HTTP/1.0
 Content-Type: text/xml; charset=utf-8
 Accept: application/soap+xml, application/dime,
multipart/related,
text/*
 User-Agent: IBM WebServices/1.0
 Host: localhost
 Cache-Control: no-cache
 Pragma: no-cache
 SOAPAction: "urn:oasis:names:tc:wsrp:v1:getServiceDescription"
 Reponse:
 HTTP/1.1 500 Internal Server Error
 Server: WebSphere Application Server/5.0
 Content-Type: text/xml; charset=utf-8
 Content-Language: de
 Connection: close
2. As you can see below the response contains the request
message. Every
response caused by an exception contains the request.

 Reponse:
 <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       <soapenv:Body>
          <Fault
xmlns="http://schemas.xmlsoap.org/soap/envelope/">
             <faultcode
xmlns:ns-115442631="urn:oasis:names:tc:wsrp:v1:types"
xmlns="">ns-115442631:OperationFailed</faultcode>
             <faultstring xmlns="">
                <![CDATA[FaultString = Test
Errormessage]]></faultstring>
                <detail xmlns="">
                   <OperationFailed
xmlns="urn:oasis:names:tc:wsrp:v1:types"/>
                    <requestMessage
xmlns="http://websphere.ibm.com/webservices/">
                       <![CDATA[
                          <?xml version="1.0" encoding="UTF-8"?>
                             <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
     xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                                <soapenv:Body>
                                    <getServiceDescription
xmlns="urn:oasis:names:tc:wsrp:v1:types">
                                        <registrationContext
xsi:nil="true"/>
                                        <desiredLocales
xsi:nil="true"/>
                                    </getServiceDescription>
                                </soapenv:Body>
                           </soapenv:Envelope>]]>
                         </requestMessage>
                      </detail>
                   </Fault>
      </soapenv:Body>
            </soapenv:Envelope>

 We have to remove this request message - because of the Web
Services
for Remote Portlets Specification. From chapter 13 of this
specification:
  ...
  In addition, the SOAP 1.1 fault's detail element MUST contain
the
corresponding namespaced
  fault element from the WSRP v1 WSDL as its only content.

The problem is use to WebServicesFault or add functionality
to help the request message.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of web    *
*                 services                                     *
****************************************************************
* PROBLEM DESCRIPTION: Several issues surrounding the use of   *
*                      SOAPElement.                            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Several issues surrounding the use of SOAPElement. The one
that initiated this APAR was: Web Services
IllegalArgumentException when request defined for
desiredLocales, minOccurs=0
Problem conclusion
A one-off fix for WSAS 5.0.2 GM was created to address several
issues WPS required. Customers requiring this fix should apply
at least the 5.0.2.3 service pack.
Temporary fix Comments
APAR information
APAR number PQ80083
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 003
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-10-27
Closed date 2003-11-18
Last modified date 2003-11-18

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
websrvce          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 003
Software edition:
Reference #: PQ80083
IBM Group: Software Group
Modified date: Nov 18, 2003