[OASIS Issue Tracker] Updated: (CMIS-653) WSDL needs soapActionvalue in operation declarations for increased interoperability with .NET

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/CMIS-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Florian Mueller updated CMIS-653:
---------------------------------

    Fix Version/s: V1.1
                       (was: V1.0 Errata)

> WSDL needs soapAction value in operation declarations for increased interoperability with .NET
> ----------------------------------------------------------------------------------------------
>
>                 Key: CMIS-653
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-653
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Improvement
>          Components: Web Services Binding
>    Affects Versions: Draft 0.70
>            Reporter: Celso Rodriguez
>            Assignee: Florian Mueller
>            Priority: Minor
>             Fix For: V1.1
>
>
> The WSDL for the web services binding specifies empty soapAction attributes in operation declarations. These empty soapAction attributes cause problems when you try to implement the services using .NET tools. If you want to implement the services in either traditional ASMX or WCF you will need to manually modify the WSDL to fill in the missing soapAction attribute. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira