PK92489: WHILE USING HTTP GET, THE NULL VALUE FOR A DISPATCH INVOCATION USING THE XML/HTTP BINDING SHOULD BE ACCEPTABLE.

Fixes are available

APAR status

Closed as program error.

Error description

Using HTTP GET, a null value for a Dispatch invocation using
the XML/HTTP binding results in an exception.

...
Caused by: java.lang.Throwable: The parameter cannot be a null
value for a Dispatch invocation using the XML/HTTP binding.
at
org.apache.axis2.jaxws.client.dispatch.BaseDispatch.getProtocolE
xception(BaseDispatch.java:437)
...

Local fix

```
na
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V7.0       *
*                  JAX-WS clients that use an XML/HTTP Binding *
****************************************************************
* PROBLEM DESCRIPTION: An error occurs if a JAX-WS client      *
*                      uses Dispatch with a XML/HTTP GET       *
*                      designation.                            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The JAX-WS programming model allows a user to communicate with
SOAP or XML/HTTP style messages.  If an XML/HTTP style is
chosen, the user may choose to send messages via POST or GET
HTTP protocols.

A GET protocol implies that no payload is sent to the remote
web service, but a payload is expected from the web service.

Example:

        Service service = Service.create(GREETER_SERVICE);
        service.addPort(HTTP_GREETER_PORT,
                        HTTPBinding.HTTP_BINDING,
"http://localhost:8080/jaxws-provider/provider/http/source/sayhi
?value=geronimo");

        Dispatch<Source> dispatch =
           service.createDispatch(HTTP_GREETER_PORT,
                                  Source.class,
                                  Service.Mode.MESSAGE);
        Map<String, Object> requestContext =
                      dispatch.getRequestContext();
        requestContext.put(MessageContext.HTTP_REQUEST_METHOD,
                           "GET");
        Source response = dispatch.invoke(null);

Example error:

java.lang.Throwable: The parameter cannot be a null
value for a Dispatch invocation using the XML/HTTP binding.
at
org.apache.axis2.jaxws.client.dispatch.BaseDispatch.getProtocolE
xception(BaseDispatch.java:437)

The null argument should be tolerated since this is an
acceptable usage pattern.

Problem conclusion

Code is added to the JAX-WS Dispatch runtime to tolerate
invoke(null) for the XML/HTTP GET scenario.

If a null input parameter is detected for other scenarios, the
JAX-WS Dispatch runtime will correctly issue an error.

APAR PK93689 fixes this problem for the WebSphere Application
Server V6.1 Feature Pack for Web Services.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.9.  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
PK92489
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-07-28
Closed date
2009-08-26
Last modified date
2009-08-26

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

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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PK92489: WHILE USING HTTP GET, THE NULL VALUE FOR A DISPATCH INVOCATION USING THE XML/HTTP BINDING SHOULD BE ACCEPTABLE.

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

R700 PSY

Document Information

Share your feedback

Need support?