axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Barrett (JIRA)" <>
Subject [jira] Commented: (AXIS2-4876) Support SOAP11 and SOAP12 over JMS binding types
Date Mon, 08 Nov 2010 16:29:10 GMT


Jeff Barrett commented on AXIS2-4876:

As noted in AXIS2-4855, JAX-WS does not currently support binding types of SOAP11 and SOAP12
for WSDL-less clients and services.  If WSDL is provided, then the SOAP version will be determined
based on the SOAP binding namespace.  However, for WSDL-less clients (e.g. using the JMS namespace
on createDispatch) or services (e.g. using the JMS namespace on the BindingType annotation),
only SOAP11 is currently supported.

The reason is that the SOAP JMS spec only defines a single namespace used for SOAP11 and SOAP12.
 The JAX-WS runtime uses that namespace as the binding type for both SOAP11 and SOAP12, and
therefore can not differentiate between the two.  This is an issue in modules/jaxws/src/org/apache/axis2/jaxws/message/
and modules/metadata/src/org/apache/axis2/jaxws/description/builder/ (at

The runtime needs to handle both SOAP11 and SOAP12 over JMS in WSDL-less scenarios.

> Support SOAP11 and SOAP12 over JMS binding types
> ------------------------------------------------
>                 Key: AXIS2-4876
>                 URL:
>             Project: Axis2
>          Issue Type: Improvement
>          Components: jaxws, kernel
>            Reporter: Jeff Barrett
>            Assignee: Jeff Barrett
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> The W3C SOAP/JMS binding specification (located here:
is nearing its first approved version, and has defined a more up to date binding ID for use
in the @BindingType annotation (for JAX-WS endpoint impl classes) and within the soap:binding
transport attribute within a WSDL document.    Previously, the SOAP/JMS spec defined this
binding ID:
> but that was just a placeholder, and the spec has amended that to this new binding ID:
> I've made some minor changes to the jax-ws and axis2 code to reflect this new binding
ID, and I've also run some tests and found a few problems and fixed those as well.    I'm
attaching a patch file with the changes.
> The purpose of the JIRA is to request that someone apply the changes since I'm not a

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message