[xsd-users] wsdl support - slightly off-topic question

[Balasubramanyam, Shivakumar]

Hi,

I have used XSD and gSOAP and here are my thoughts,

XSD today is purely a data representation layer and has support for data
binding as well. The feature that I liked most in XSD is the ability to
associate a data binding to either one of the supported formats (XML,
XDR, Boost archive, ACE CDR). I am sure this could be extended to any
user required binding fairly easily.

I believe boris has extended this to decouple the data and binding layer
which IMO is really kewl. Supporting multiple data binding in the same
runtime would be even great.

gSOAP is very specific to SOAP protocol which is what you are
specifically looking for. As you pointed out, gsoap provides one feature
worth noting, RPC invocation when compared to XSD. However, gSOAP is not
a true WSDL product for the reasons that WSDL provides multiple RPC
protocols like JMS binding, http binding which gSOAP does not provide
and rightfully not expected as well. The issue however is that once you
change the RPC, all your client code now needs to be ripped off. So
gSOAP is not for a forward looking application user.

But I agree with Attila, if you are looking for something that fits only
SOAP implementation of WSDL and are comfortable with interfaces that are
tightly coupled with gSOAP, then it should work very well for you. The
product is defnitely very stable and we use both gSOAP and XSD in our
product. Ofcourse, we are in the path to get away from gSOAP for reasons
mentioned above.


My wish list for true SOA product would be [or what could be built using
XSD that would make application developer life really simple],

1. Tuscany SCA architecture.

2. Use XSD for data representation layer.

3. WSDL 2.0 + additional interface support from SCA spec. 
	[WSDL 2.0 would specifically help us to use XSD for generating
all the message related schemas. 
		It splits the data representation and RPC invocation
layers more clearly.]

Today, SCA uses SDO and DAS which IMO is cumbersome and I feel XSD
solution would fit the requirements very well.

Thanks,
Shiva

-----Original Message-----
From: xsd-users-bounces at codesynthesis.com
[mailto:xsd-users-bounces at codesynthesis.com] On Behalf Of Attila
Sent: Tuesday, August 05, 2008 7:39 AM
To: Rizzuto, Raymond
Cc: xsd-users at codesynthesis.com
Subject: Re: [xsd-users] wsdl support - slightly off-topic question

I have used gSOAP before with pretty good success.  The one thing that I
find lacking is support for non-standard interactions (such as
notification/subscription interfaces). Also the client SOAP calls are
blocking and takes some work to make it non-blocking.

What tool do you use from before?  I have explored a few options myself,
but gSOAP still seems to come out on top.


On Tue, Aug 5, 2008 at 9:35 AM, Rizzuto, Raymond
<Raymond.Rizzuto at sig.com>wrote:

> I was wondering if there is any way to use xsd to compile a wsdl file
into
> classes that can invoke remote method calls over soap.   I know this
is a
> long shot, but since wsdl is xml-based, I though I might as well ask.

> I'm open to any other suggestions, commercial or open source.
>
> The reason I ask is that I am looking for an alternate to the current 
> tool we use for generating C++ classes/functions from a wsdl file.  
> The current tool we use has very high costs, and the vendor isn't very
responsive.
>
> Ray
>
> ________________________________
> Ray Rizzuto
> raymond.rizzuto at sig.com
> Susquehanna International Group
> (610)747-2336 (W)
> (215)776-3780 (C)
>
>
>
> ________________________________
> IMPORTANT: The information contained in this email and/or its 
> attachments is confidential. If you are not the intended recipient, 
> please notify the sender immediately by reply and immediately delete 
> this message and all its attachments. Any review, use, reproduction, 
> disclosure or dissemination of this message or any attachment by an 
> unintended recipient is strictly prohibited. Neither this message nor 
> any attachment is intended as or should be construed as an offer, 
> solicitation or recommendation to buy or sell any security or other 
> financial instrument. Neither the sender, his or her employer nor any 
> of their respective affiliates makes any warranties as to the 
> completeness or accuracy of any of the information contained herein or
that this message or any of its attachments is free of viruses.
>



--
Attila
Software Developer
atteeela at gmail.com