* I think SOAP/JMS binding still needs to be found by BindingIDFactory
extension. One can write JMSBindingIDFactory that knows how to create
BindingID from SOAP/JMS binding lexical values. This BindingID, say
JMSBindingID works for both SOAP1.1 and SOAP 1.2 versions.
* We could add a method to BindingID that gives the transport
attribute for the soap binding in the WSDL. The default implementation
would return http transport attribute. This means the existing
BindingID impl wouldn't break. JMSBindingID would provide its own
implementation for this method. WSDLGenerator uses this method while
generating WSDL
String getTransport() {
// Based on SOAPVersion return the correct transport attribute
return SOAP_HTTP_TRANSPORT or SOAP12_HTTP_TRANSPORT;
}
* I suggest that we add these extensions to the trunk and also create
a JMS binding commons project in jax-ws-commons.dev.java.net
* I will send more feedback about the wsgen command line options later
this week.
Jitu
On Aug 20, 2008, at 9:56 AM, Jitendra Kotamraju wrote:
> I am attaching the design document from IBM developers regarding
> SOAP/JMS binding. I respond with my feedback later today.
>
> thanks,
> Jitu
>
> <IBMJAXWSRequirement12June08.doc>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jax-ws.dev.java.net
> For additional commands, e-mail: dev-help_at_jax-ws.dev.java.net