cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mihir Shelat (JIRA)" <j...@apache.org>
Subject [jira] Created: (CXF-2336) SOAP Binding (i.e. SOAP Version) of out going message should be same as incoming message
Date Fri, 10 Jul 2009 06:42:14 GMT
SOAP Binding (i.e. SOAP Version) of out going message should be same as incoming message
----------------------------------------------------------------------------------------

                 Key: CXF-2336
                 URL: https://issues.apache.org/jira/browse/CXF-2336
             Project: CXF
          Issue Type: Improvement
          Components: Soap Binding
            Reporter: Mihir Shelat


Dear Sir,

Currently I am evaluating various Webservice Frameworks such as Axis2, CXF and Spring WS.

In CXF the default SOAP Binding (i.e. SOAPVersion) is SOAP 1.1. So if you don't set any binding
in your webservice, by default the SOAP version of outgoing message is 1.1.

CXF allows configuring the SOAP binding of outgoing message either using Annotations OR Spring
Configuration. No matter whatever is the SOAP Binding of incoming message, CXF always uses
the binding specified at server side for out going message.

Like wise AXIS2, for outgoing messages, CXF should use the same SOAP Binding as that of incoming
message instead of the one configured in the server. This allows webservices to be more interoperable
and SOAP Binding agnostic.

Let me know if there is any way by which I can configure CXF to use the same SOAP Binding
as that of incoming message. If it is not possible, can we incorporate this improvement in
the next release?

One of the criteria for webservice framework selection is simultaneous support of SOAP 1.1
and SOAP1.2 bindings.

Thanks,
Mihir


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


Mime
View raw message