PK83482: ADD MULTIPLE BINDING TYPE SUPPORT FOR JAX-WS PROVIDER ENDPOINT.

Fixes are available

APAR status

Closed as new function.

Error description

Enhance the JAX-WS Provider endpoint to allow multiple
message binding types (SOAP 1.1 & SOAP 1.2) on the same endpoint
implementation.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application Server        *
*                  Feature Pack for Web Services developers    *
*                  of JAX-WS or Service Component              *
*                  Architecture (SCA)                          *
****************************************************************
* PROBLEM DESCRIPTION: Multiple Binding Type support for       *
*                      JAX-WS Provider Endpoint.               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This is an improvement item for IBM Websphere Process Server.
Websphere Process Server has a requirement to support multiple
bindings on a JAX-WS Provider endpoint.

Problem conclusion

This APAR adds an enhancement for Websphere Process Server to
support multiple message binding type (SOAP 1.1 or SOAP 1.2)
on a JAX-WS Provider endpoint. This implementation will allow
Websphere Process Server to define a custom constant on
@BindingType annotation on JAX-WS Provider. This constant will
enable Websphere Process Server to send SOAP1.1 and SOAP1.2
requests to a JAX-WS Provider endpoint.
Following is an example of the new @BindingType:
/**
* @generated
* SCA WS binding provider
*
*/
@WebServiceProvider(
targetNamespace="http://ServiceASOAP1/echo/Binding",
serviceName="echoExport1_echoHttpService",
portName="echoExport1_echoHttpPort",

wsdlLocation="WEB-INF/wsdl/ServiceASOAP1_echoExport1.wsdl"
)
@ServiceMode(value=Service.Mode.MESSAGE)
@BindingType(SOAPBinding.SOAP_HTTP_BINDING)
public class EchoProvider implements Provider<SOAPMessage> {

/* (non-Javadoc)
* @see javax.xml.ws.Provider#invoke(java.lang.Object)
*/
public SOAPMessage invoke(SOAPMessage request) {
return request
}
}

APAR PK96819 corrects this problem for WebSphere
Application Server V7.

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

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

PK96819

Fix information

Fixed component name
WEBSERVIC FEATU
Fixed component ID
5724J0850

Applicable component levels

R610 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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:
29 December 2021

Tips

PK83482: ADD MULTIPLE BINDING TYPE SUPPORT FOR JAX-WS PROVIDER ENDPOINT.

Fixes are available

Subscribe

APAR status

Closed as new function.

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

R610 PSY

Document Information

Share your feedback

Need support?