You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andrei Shakirin (JIRA)" <ji...@apache.org> on 2012/10/22 13:40:12 UTC

[jira] [Created] (CXF-4593) STSClient: support different SOAP bindings for MEX call

Andrei Shakirin created CXF-4593:
------------------------------------

             Summary: 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
            Priority: Minor


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

[jira] [Updated] (CXF-4593) STSClient: support different SOAP bindings for MEX call

Posted by "Andrei Shakirin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrei Shakirin updated CXF-4593:
---------------------------------

    Attachment: STSClientMEX.patch

Patch
                
> 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
>            Priority: Minor
>         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

[jira] [Resolved] (CXF-4593) STSClient: support different SOAP bindings for MEX call

Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
     [ 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