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-4855) Support new SOAP/JMS binding ID
Date Mon, 08 Nov 2010 16:18:14 GMT


Jeff Barrett commented on AXIS2-4855:

One other important point.  The issue is with WSDL-less clients and servers.  When WSDL is
included, the soap version is determined by the SOAP namespace on the binding.  When WSDL
is not included, and the JMS namespace is used on the client (for createDispatch) or on the
server (in the @BindingType annotation), that is when the issue occurs.

> Support new SOAP/JMS binding ID
> -------------------------------
>                 Key: AXIS2-4855
>                 URL:
>             Project: Axis2
>          Issue Type: Improvement
>          Components: jaxws, kernel
>            Reporter: Phil Adams
>            Assignee: Jeff Barrett
>         Attachments: patch.txt
>   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