PK87171: WS-ADDRESSING DOES NOT PROPERLY RECOGNIZE THE DEFAULT ACTION PATTERN

APAR status

• Closed as program error.

Error description

• An example request that contains WS-Addressing elements and
  that follows the default action pattern is as below:
  
  <s:Envelope
  xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:a="http://www.w3.org/2005/08/addressing">
  <s:Header>
  <a:Action s:mustUnderstand="1">
  http://com.hello/HelloWorld/sayHelloRequest
  </a:Action>
  ...
  
  The request is valid. However, it is met by a SOAP Fault from
  a WebSphere Application Server web service:
  
  <?xml version="1.0" encoding="utf-8"?>
  <soapenv:Envelope
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:wsa="http://www.w3.org/2005/08/addressing">
  <soapenv:Header>
  <wsa:Action>
  http://www.w3.org/2005/08/addressing/fault
  </wsa:Action>
  <wsa:RelatesTo>
  urn:uuid:ae2b4478-e2b8-4f63-9e5a-21299ac42ce0
  </wsa:RelatesTo>
  <wsa:FaultDetail>
  <wsa:ProblemAction>
  <wsa:Action>
  http://com.hello/HelloWorld/sayHelloRequest
  </wsa:Action>
  </wsa:ProblemAction>
  </wsa:FaultDetail>
  </soapenv:Header>
  <soapenv:Body>
  <soapenv:Fault>
  <faultcode>wsa:ActionNotSupported</faultcode>
  <faultstring>The [action] cannot be processed at
  the receiver.
  </faultstring>
  <detail></detail>
  </soapenv:Fault>
  </soapenv:Body>
  </soapenv:Envelope>
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of WS-Addressing in WebSphere         *
  *                  Application Server V6.1 web services that   *
  *                  receive requests using the default action   *
  *                  pattern.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: A web service might reject a            *
  *                      WS-Addressing request that uses the     *
  *                      default action pattern.                 *
  ****************************************************************
  * RECOMMENDATION:  Install the fix pack that contains this APAR*
  ****************************************************************
  In the absence of a WS-Addressing action attribute on a WSDL
  operation's input and output elements, the W3C specifies that a
  default action pattern be assumed. From the "Web Services
  Addressing" specification:
  
  "The general form of an action URI is as follows:
  
  [target namespace]/[port type name]/[input|output name]
  The "/" is a literal character to be included in the action.
  The values of the properties are as defined below.
  
  [target namespace] is the target namespace
  (/definition/@targetNamespace). If [target namespace] ends
  with a "/" an additional "/" is not added.
  
  [port type name] is the name of the port type
  (/definition/portType/@name).
  
  [input|output name] is the name of the element as defined in
  Section 2.4.5 of WSDL 1.1."
  
  An example request that follows this default action pattern is
  as below:
  
  <s:Envelope
  xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:a="http://www.w3.org/2005/08/addressing">
     <s:Header>
        <a:Action s:mustUnderstand="1">
          http://com.hello/HelloWorld/sayHelloRequest
        </a:Action>
        ...
  
  The request is valid. However, it is met by a SOAP Fault from
  the WebSphere web service:
  
  <?xml version="1.0" encoding="utf-8"?>
    <soapenv:Envelope
     xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
     xmlns:wsa="http://www.w3.org/2005/08/addressing">
      <soapenv:Header>
       <wsa:Action>
        http://www.w3.org/2005/08/addressing/fault
       </wsa:Action>
       <wsa:RelatesTo>
        urn:uuid:ae2b4478-e2b8-4f63-9e5a-21299ac42ce0
       </wsa:RelatesTo>
       <wsa:FaultDetail>
         <wsa:ProblemAction>
           <wsa:Action>
            http://TwoWSDLTest/echo/echo/operation1Request
           </wsa:Action>
         </wsa:ProblemAction>
       </wsa:FaultDetail>
       </soapenv:Header>
       <soapenv:Body>
         <soapenv:Fault>
            <faultcode>wsa:ActionNotSupported</faultcode>
            <faultstring>The [action] cannot be processed at
  the receiver.
            </faultstring>
            <detail></detail>
         </soapenv:Fault>
       </soapenv:Body>
    </soapenv:Envelope>
  
  This SOAP Fault specifically occurs when the web service is
  described by a WSDL that defines the binding, then imports
  a separate WSDL that defines the portType.
  

Problem conclusion

• The JAX-WS engine was fixed to improve processing of imported
  WSDL's. This improvement allows the WS-Addressing runtime to
  detect the correct default URI for the WS-Addressing action
  element.
  
  This problem does not exist in V7.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.27.  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 is sysrouted FROM one or more of the following:

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

Fix information

• Fixed component name

  WEBSERVIC FEATU

• Fixed component ID

  5724J0850

Applicable component levels

• R610 PSY

     UP