OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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



    [ http://tools.oasis-open.org/issues/browse/CMIS-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21782#action_21782 ] 

Adam Harmetz  commented on CMIS-653:
------------------------------------

I discussed this issue with the .NET team at Microsoft.

There was agreement that the proposed change would indeed make it easier for .NET developers to implement the standard because of design decisions make in .NET.  To be clear, this is not required in order to implement the standard using .NET nor is does it imply that anything .NET is doing doesn't comply with WSDL specifications.  It's just a change we could make to our WSDL that will save .NET developers time - which is a good idea.

> 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: Ethan Gur-esh
>            Priority: Minor
>
> 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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]