RE: Compound types and heterogeneous SOAP servers

[Weider Chang <we...@truetel.com.tw>]

Hi, Jacek

Thanks for your explanation. However, I still have question about it. 

First, if server is an APACHE SOAP, and  client uses the IdooX SOAP. How does the client obtain the whole information to generate its own classes for compound types and the stub ( e.g. Apache_SOAP_Port.java in the Idoox's demo)? Specially, the information likes the content of <schema> in the Idoox's apachesoap.scl ? Apache has a deployment-descriptor xml but this file does not detail what makes about an address (or phone, or the schema). Does this mean the client (not an APACHE SOAP) programmer must obtain the schema-like information (by any mean) to construct the serialization/deserialization mechanism for the client-side SOAP implementation? 

Second, if server is an IdooX SOAP and has the address book service in it, should it need to provide the whole client-side stuff (address.java, phone.address, and the Apache_SOAP_Port.java) for an programmer to access the service easily? If the client is a C++ or Perl SOAP implementation, should the server provide the similiar stuff for client programmer? 
Or, the client-side programmer uses the SCL file (or WSDL file) provided by the SOAP server to create his/her stuff for serialization/deserialization?


Best Regards

Weider Chang

> -----Original Message-----
> From: Jacek Kopecky [mailto:jacek@idoox.com]
> Sent: Friday, March 30, 2001 7:13 PM
> To: Weider Chang
> Cc: Soap-Dev (E-mail)
> Subject: Re: Compound types and heterogeneous SOAP servers
> 
> 
>  Hello Weider. 8-)
> 
>  I can speak for using IdooXoap.
> 
>  We have a demo called apachesoap where we demonstrate how to do
> exactly your example - AddressBook. Try pointing your client to
> "http://soap.idoox.net/1.1/servlet/apachesoap/" and asking about 
> "Peter New". 8-)
> 
>  What you'll need is a description of the service (we made one using
> SCL some time ago, it's included in our packages) and that's about it.
> 
>  The client will need the generated Address and Phone classes only if
> you use IdooXoap-generated stub to access the service, but that's no
> problem, because all this is generated for you. Actually, you can
> change those classes if you want to (only for the client or only on
> the server or however you will), as long as the members stay publicly
> accessible (possibly via JavaBeans-like accessors).
> 
>  If you use ApacheSOAP for creating your client, you might not need
> the classes or you might need to expand them to handle ApacheSOAP
> serialization and deserialization.
> 
>  Best regards 
> 
>                             Jacek Kopecky
>                                Idoox
> 
> 
> 
> On Thu, 29 Mar 2001, Weider Chang wrote:
> 
>  > Hi All, 
>  > 
>  > 	Has any one tried out to use a Apache SOAP client to invoke
>  > any service deployed on a heterogeneous SOAP server (like
>  > SOAPLite, IdooXoap) and the parameters of the service's method
>  > are compund types that are not defined in SOAP 1.1?
>  > 
>  > 	For example, the Apache SOAP sample - AddressBook, there's
>  > two compound JAVA classes, Address and Phone. If the serve is an
>  > IdooXoap SOAP implementation and the client uses the Apache SOAP
>  > implementation, does the client need the Address.class and
>  > Phone.class provided by IdooXoap SOAP server to invoke the
>  > AddressBook service?
>  > 
>  > Weider Chang
> 
> 

RE: Compound types and heterogeneous SOAP servers

[Jacek Kopecky <ja...@idoox.com>]

 Hello Weider,

 To your first question: since IdooXoap is built on service
descriptions, in order to use the best client features of IdooXoap you
have to get the descriptions from somewhere. Example of a description
language that we support is WSDL 1.0 (not 1.1 yet), and that contains
the schema information and the like. (The other language is SCL but
it's obsoleted by WSDL.)

 On the other hand if IdooXoap is on the server side it doesn't matter
to the client that it's IdooXoap - the client only knows the
interface. Again, WSDL is the preferred means of describing
interfaces. So the answer would be "yes, the client uses the WSDL
description in any way it sees fit, IdooXoap client would use it to
generate the classes you mentioned.

 Best regards

                            Jacek Kopecky
                               Idoox



On Mon, 2 Apr 2001, Weider Chang wrote:

 > Hi, Jacek
 >
 > Thanks for your explanation. However, I still have question about it.
 >
 > First, if server is an APACHE SOAP, and client uses the IdooX
 > SOAP. How does the client obtain the whole information to
 > generate its own classes for compound types and the stub ( e.g.
 > Apache_SOAP_Port.java in the Idoox's demo)? Specially, the
 > information likes the content of <schema> in the Idoox's
 > apachesoap.scl ? Apache has a deployment-descriptor xml but this
 > file does not detail what makes about an address (or phone, or
 > the schema). Does this mean the client (not an APACHE SOAP)
 > programmer must obtain the schema-like information (by any mean)
 > to construct the serialization/deserialization mechanism for the
 > client-side SOAP implementation?
 >
 > Second, if server is an IdooX SOAP and has the address book
 > service in it, should it need to provide the whole client-side
 > stuff (address.java, phone.address, and the
 > Apache_SOAP_Port.java) for an programmer to access the service
 > easily? If the client is a C++ or Perl SOAP implementation,
 > should the server provide the similiar stuff for client
 > programmer?  Or, the client-side programmer uses the SCL file
 > (or WSDL file) provided by the SOAP server to create his/her
 > stuff for serialization/deserialization?
 >
 >
 > Best Regards
 >
 > Weider Chang
 >