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-4593) STSClient: support different SOAP bindings for MEX call
Date Tue, 20 Nov 2012 21:16:59 GMT

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

Daniel Kulp resolved CXF-4593.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.7.1
                   2.6.4
                   2.5.7
         Assignee: Daniel Kulp
    
> STSClient: support different SOAP bindings for MEX call
> -------------------------------------------------------
>
>                 Key: CXF-4593
>                 URL: https://issues.apache.org/jira/browse/CXF-4593
>             Project: CXF
>          Issue Type: Improvement
>            Reporter: Andrei Shakirin
>            Assignee: Daniel Kulp
>            Priority: Minor
>             Fix For: 2.5.7, 2.6.4, 2.7.1
>
>         Attachments: STSClientMEX.patch
>
>
> Hi,
> Actually STSClient always uses SOAP 1.1 bindings for the MEX communications.
> There are some use cases, where MEX should be done using SOAP 1.2 (http://cxf.547215.n5.nabble.com/Dispatching-WS-with-WSS4J-through-STS-tt5716991.html).
> At the moment only the way to do it is wrap STSClient in own implementation and override
STSClient.configureViaEPR() method, that is not easy and comfortable.
> Proposal: use soapVersion from STSClient also for MEX communication (with high probability
STS and MEX communications will use the same SOAP versions)
> Regards,
> Andrei.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message