cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-2336) SOAP Binding (i.e. SOAP Version) of out going message should be same as incoming message
Date Thu, 16 Jul 2009 17:27:14 GMT

     [ https://issues.apache.org/jira/browse/CXF-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Kulp resolved CXF-2336.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.3
                   2.1.6
         Assignee: Daniel Kulp


There are a couple issues that I've now fixed.  However, there is an easy workaround that
you could use for now.

If you add a SECOND jaxws:endpoint definition to the beans.xml that binds to the same address,
but uses soap 1.2, it should "just work" for you.   That should allow it to respond properly
with soap 1.1 responses.

While playing with your testcase, I did discover some other issues that are now fixed.   If
a soap 1.2 request comes into a soap 1.1 endpoint, it was supposed to raise a VersionMismatch
exception.   That is now fixed.    I also fixed your case of a soap 1.1 message coming into
a soap 1.2 endpoint.   It now properly processes and a soap 1.1 response sent back.



> 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
>            Assignee: Daniel Kulp
>             Fix For: 2.1.6, 2.2.3
>
>         Attachments: cxf_ex.zip, winmail.dat
>
>
> 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