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

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-c-cpp message

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


Subject: Re: [sca-c-cpp] ISSUE 17: Should C++ -> WSDL Roundtrip with WSDL -> C++



As promised...
Upon further study, the real distinction seems to be based on if messages have one part with a type defined by a schema element or potentially multiple parts each with a type defined by a schema type (simple or otherwise).

As far as I can tell the difference between doc-literal and wrapped doc-literal has to do with the rules for the name of the schema element describing the request message at least as far as the WSDL goes.  If I am missing something here, I would love to be enlightened.  I do not suggest distinguishing between these.

In any event, I still believe we have to address both ways of describing messages and this document has revised mapping rules based on those David described last week as well as the WSDL fragments promised below.


Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect

Research Triangle Park,  NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com



Bryan Aupperle/Raleigh/IBM@IBMUS

05/05/2008 04:30 PM

To
sca-c-cpp@lists.oasis-open.org
cc
Subject
Re: [sca-c-cpp] ISSUE 17: Should C++ -> WSDL Roundtrip with WSDL -> C++






As I think about this some more, we are going to have to address mapping from WSDL for at least rpc-literal, doc-literal and wrapped doc-literal.  We could try and limit this, but the reality is that all three styles are in use.


In the reverse direction I believe that again, we cannot ignore doc-literal or wrapped doc-literal since these are popular, and interoperable styles.  We can discuss if we need annotations to control which style is to be generated or leave it  to be specified in an implementation dependent manner (e.g. tool preference).


David has stated the basic principles but now we need to apply them to each style.


I'll try to work on some WSDL fragments of each style that illustrate the principles.


Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect

Research Triangle Park,  NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com


"David Haney" <haney@roguewave.com>

04/29/2008 07:53 PM


To
<sca-c-cpp@lists.oasis-open.org>
cc
Subject
[sca-c-cpp] ISSUE 17: Should C++ -> WSDL Roundtrip with WSDL -> C++







Attached is some initial work around redefining the C++ -> WSDL and WSDL
-> C++ mapping.  It still needs quite a bit of work, but there may be
enough there to start discussing whether it's a direction we want to
take.

Thanks.

David.

-- David Haney
-- Director of Architecture
-- Rogue Wave Software
-- http://www.roguewave.com/


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php ---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

wsdl-cpp-mapping.doc

WSDL Fragments.doc



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