W. Matthew, I see that you chose the same approach as IdooXoap did,
too. We also compare xsi:type against the WSDL, we don't require
xsi:type either and we also put it in there everywhere.

What kind of XML Schema representation of SOAP Encoding structures
do you support? Or do you support any general schema?

                             Jacek Kopecky
                                Idoox



On Fri, 2 Feb 2001, W. Matthew Long wrote:

  > >   Hi Tony,
  > >
  > >   What I'm actually looking for is a service that doesn't put in the
  > > xsi:type
  > >   stuff and relies on WSDL/SDL/whatever to get the knowledge of the
  > types of
  > >   parameters of a call. We recently put in support in Apache SOAP
  > to handle
  > >   that and I haven't been able to find any complex type tests. I
  > wrote a
  > >   simpel test to talk to your guidgen server (written in MS SOAP I
  > believe)
  > >   and it works fine.
  > >
  >
  > Sanjiva,
  >
  > We should be releasing the vbSOAP tool set in two weeks.  The SOAP
  > Processor utilizes the WSDL Processor to ensure the scenario.
  > 1) If the xsi:type is set in the Request Envelope the xsi:type is
  > check against the WSDL document, also the value is check against the
  > type specific is the xsi:type(s) match between the request and the
  > WSLD document for the service
  > 2) If the xsi:type is not specified, the SOAP processor utilizes the
  > WSDL processor to ensure the part values can be converted into the
  > appropriate type.
  > 3) Finally, we have WSDL interrogator that will generate VBScript
  > from a WSDL document for method calls.  The Interrogator along with
  > our SOAP client will automatically use xsi:type attributes on the
  > parts for interoperability purposes, although our SOAP processor does
  > not require it.
  >
  > We have found that the WSDL Interrogator along with our SOAP client
  > is highly interoperable with does take into account the possibility
  > of differing XMLSchema, i.e., 1999 and 2000/10, which some
  > implementations require.
  >
  > All this will be available, along with our WSDL Wizard for COM
  > objects after the documentation is completed (which is a mountain of
  > documentation)
  >
  >
  >
  >
  >
  >
  >
  > To unsubscribe from this group, send an email to:
  > soapbuilders-unsubscribe@yahoogroups.com
  >
  >
  >

Apologies to those who are seeing this same question on a gzillion
different discussion groups but I am determined to find out if this is
possible or not and it seems like this is just the right place to
do that...

<B>has anyone out there managed to make a Visual Basic client
(Microsoft SOAP Toolkit v2.0) which exploits a WSDL file work against
a SOAP server implemented with Apache SOAP 2.0 or 2.1 ?</B>

I have made a VB client work against an Apache SOAP server by
exploiting the low level API (ie. manipulating the soap envelope
directly on the VB side to include the xsi:type param) but would like
to get it working by exploiting the high level API / WSDL file.

Apparently Apache SOAP 2.1 has "Reduced dependency on xsi:type for
deserialization" - but I haven't yet seen how. examples...
1) If I take my VB client written with a low level API and remove the
code which inserts the xsi:type line into the envelope, I get a server
side error : "No Deserializer found" for my 'type' (actually my
method's parameter name) - see actual error message below.
2) If I use the high level API and exploit a wsdl file I get the same
error

No Deserializer found to deserialize a ':imntType' using encoding
style 'http://schemas.xmlsoap.org/soap/encoding/'.

many thanks for any help you can provide

Nick Quaine

-----Original Message-----
From: Florin Moldovan [mailto:florin@...]
Sent: Friday, February 02, 2001 1:48 AM
To: soapbuilders@yahoogroups.com
Subject: [soapbuilders] SOAP question

        Hi everybody,

I'm a Java programmer and I'm working with Apache SOAP.
I want to send an object like ObjectType, via SOAP, and I don't know how. Could anybody help me ?
(I work with Apache SOAP)

e.g.:
public class ObjectType{

    String s;
    Vector v;
    AnotherType a;
............
}

It's a problem with Vector and AnotherType types.
I want to use this ObjectType like parameter of a client-side methode.

Thank you very, very much.

            Florin.

To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com

>   Hi Tony,
>
>   What I'm actually looking for is a service that doesn't put in the
> xsi:type
>   stuff and relies on WSDL/SDL/whatever to get the knowledge of the
types of
>   parameters of a call. We recently put in support in Apache SOAP
to handle
>   that and I haven't been able to find any complex type tests. I
wrote a
>   simpel test to talk to your guidgen server (written in MS SOAP I
believe)
>   and it works fine.
>

Sanjiva,

We should be releasing the vbSOAP tool set in two weeks.  The SOAP
Processor utilizes the WSDL Processor to ensure the scenario.
1) If the xsi:type is set in the Request Envelope the xsi:type is
check against the WSDL document, also the value is check against the
type specific is the xsi:type(s) match between the request and the
WSLD document for the service
2) If the xsi:type is not specified, the SOAP processor utilizes the
WSDL processor to ensure the part values can be converted into the
appropriate type.
3) Finally, we have WSDL interrogator that will generate VBScript
from a WSDL document for method calls.  The Interrogator along with
our SOAP client will automatically use xsi:type attributes on the
parts for interoperability purposes, although our SOAP processor does
not require it.

We have found that the WSDL Interrogator along with our SOAP client
is highly interoperable with does take into account the possibility
of differing XMLSchema, i.e., 1999 and 2000/10, which some
implementations require.

All this will be available, along with our WSDL Wizard for COM
objects after the documentation is completed (which is a mountain of
documentation)

Hi Tony,

What I'm actually looking for is a service that doesn't put in the xsi:type
stuff and relies on WSDL/SDL/whatever to get the knowledge of the types of
parameters of a call. We recently put in support in Apache SOAP to handle
that and I haven't been able to find any complex type tests. I wrote a
simpel test to talk to your guidgen server (written in MS SOAP I believe)
and it works fine.

Sanjiva.

"Tony Hong" <thong@...> on 01/31/2001 08:17:32 PM

Please respond to soapbuilders@yahoogroups.com

To:   <soapbuilders@yahoogroups.com>
cc:
Subject:  RE: [soapbuilders] Interoperability lab




Sanjiva,

One  other note -  to illustrate the existing struct array test, here is
the  request/response wiredump. In
this  example, it's a Apache 2.0 client hitting a SOAPLite server (it works
successfully) . Let me know if
this  is what you're thinking about, or if you need something different.
Thanks

Tony

----------- Apache Requst  -----------------------

POST  /perl/soaplite.cgi HTTP/1.0
Host: tony:8080
Content-Type:  text/xml
Content- Length: 541
SOAPAction:  "urn:xmethodsInterop#echoStruct"

<SOAP-ENV:Envelope  xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/"  xmlns:xsi="
http://www.w3.org/1999/XMLSchema-instance"  xmlns:xsd="
http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<ns1:echoStruct  xmlns:ns1="urn:xmethodsInterop"  SOAP-ENV:encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/">
<echo  xsi:type="ns1:SOAPStruct">
<varInt  xsi:type="xsd:int">3</varInt>
<varFloat  xsi:type="xsd:float">1.2</varFloat>
<varString  xsi:type="xsd:string">Hello</varString>
</echo>
</ns1:echoStruct>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

------------- SOAPLite  response --------------------------

HTTP/1.1 200 OK
Content- Length:  672
Content-Type: text/xml
glue-routing: true
date: Thu, 01 Feb 2001  01:11:21 GMT
server: Apache/1.3.14 (Unix) PHP/4.0.1pl2
soapserver:  SOAP::Lite/Perl/0.45

<?xml version="1.0"  encoding="UTF-8"?><SOAP-ENV:Envelope  xmlns:SOAP-ENC="
http://schemas.xmlsoap.org/soap/encoding/"  SOAP-ENV:encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/"  xmlns:xsi="
http://www.w3.org/1999/XMLSchema-instance"  xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/"  xmlns:xsd="
http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<namesp1:echoStructResponse  xmlns:namesp1="urn:xmethodsInterop">
<SOAPStruct  xsi:type="namesp1:SOAPStruct">
<varFloat  xsi:type="xsd:float">1.2</varFloat>
<varString  xsi:type="xsd:string">Hello</varString>
<varInt  xsi:type="xsd:int">3</varInt>
</SOAPStruct>
</namesp1:echoStructResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

-----Original Message-----
From: Tony  Hong [mailto:thong@...]
Sent: Wednesday, January 31, 2001  4:57 PM
To: soapbuilders@yahoogroups.com
Subject: RE:  [soapbuilders] Interoperability lab


Hi  Sanjiva,

Thanks, I'm glad you find the idea  useful!

The  yahoo group is listed now - I accidently delisted it from their
directory, but  it's
visible again. Just search for"soapbuilders"  at groups.yahoo.com and you
should
see  it pop up .

The  testbed as I'vedescribed has an "echoStruct" and "echoStructArray"
methods -
I've built this service already for  Apache and SOAP::Lite - for Apache,
the service uses
the  Bean serializer to map to/from a simple object. See

http://www.xmethods.net/detail.html?id=10  for SOAP::Lite
and
http://www.xmethods.net/detail.html?id=11   for Apache

Is  this what you are thinking of?

As  far as MS or 4s4c, I'm not sure of any other existing services that
involve
complex types - Simon, do you know of  any?

If  you describe the kind of type/structure you'd like to see built as an
"echo"  , I can make sure its part
of  the target test set and start the construction in a variety of
implementations, including the ones
you  mention.

Cheers,
Tony


-----Original Message-----
From: Sanjiva Weerawarana  [mailto:sanjiva@...]
Sent: Wednesday, January 31, 2001 9:42  AM
To: soapbuilders@yahoogroups.com
Subject: Re:  [soapbuilders] Interoperability lab


Hi  Tony,

I think this is a great idea! Thanks for starting the  work!

Do u know of a service implemented with MS SOAP, 4S4C, ... etc.  that uses
complex types and is available on the net? I'm trying to test  the apache
soap interoperabilty using complex types with non-Apache SOAP  services and
I can't seem to find interesting services to  try.

Also, what's the Yahoo group for this? I can't seem to find the  group to
change my email  address!

Bye,

Sanjiva.

Jacek Kopecky  <jacek@...> on 01/31/2001 10:23:07 AM

Please respond to  soapbuilders@yahoogroups.com

To:   Soapbuilders  <soapbuilders@yahoogroups.com>
cc:
Subject:  Re:  [soapbuilders] Interoperability lab



I'd add a circular  structure:

LinkedList echoLinkedList(LinkedList  linkedList)

where the definition in Java would be

public class  LinkedList {
    int x;
    LinkedList  next;
}

which means nullable and referenced next part. Sending a  circular list
through might also help.  8-)

                             Jacek  Kopecky
                                Idoox



On Wed, 31 Jan 2001, Tony Hong wrote:

> Hi  all
>
> I've mentioned to a couple of you that I'm going to  create
> an interoperability testbed. I'd like to get some  feedback
> from this group.
>
> For each if a number of  different SOAP implemenation, I'm
> planning to host a service that  exposes these methods
>
> String echoString(String  inputString)
> String[] echoStringArrray(String[]  inputStringArray)
> Integer echoInteger(Integer inputInteger)
>  Integer[] echoIntegerArray(Integer[] inputIntegerArray)
> Float  echoFloat(Float inputFloat)
> Float[] echoFloatArray(Float[]  inputFloatArray)
> SOAPStruct echoStruct( SOAPStruct  inputStruct)
> SOAPStruct[] echoStructArray (SOAPStruct[]  inputStructArray)
>
> Where SOAPStruct is a simple structure  with integer, float, and
> string fields.
>
> Other  possibilities include:
> Hashmap / Associative array , using the  encoding proposed by
> the Apache folks.
> XML  Documents
>
> This "echo" service does nothing really useful  except
> illustrate the ability of the service to accept a  clients
> envelope, deserialize the types correctly, and then
>  reserialize the respones into something that the client
> can see if  it understands.
>
> I built this service for Apache 2.0 and  SOAP::Lite a few
> months ago, and I think Paul Kulchenko will agree  that
> it's been really useful for testing interop  issues.
>
>
> In addition to exposing these services, I  also plan to:
>
> * Publish wiredumps of the request and  response envelopes
> that each implementation uses - ie, each  implementations
> client
> * For those implementations that  dynamically generate
> WSDL, I will publish the WSDL generated for  each of these
> methods.
>
> I think this is a first step  to REALLY filling out those issues
> lists for SOAP and WSDL  interoperability. It's much easier to
> see the issues when all this  info is right in front of you.
>
> My question here is
>
> Does this set of types/methods make sense? Would you  modify
> this list in any way?
>
> Thanks for any  feedback!
>
> Tony
>
>  ----------------------------------------
> XMethods Web Services  Listings
> http://www.xmethods.net
>
>
>  To unsubscribe from this group, send an email to:
>  soapbuilders-unsubscribe@yahoogroups.com
>
>
>



To  unsubscribe from this group, send an email  to:
soapbuilders-unsubscribe@yahoogroups.com








To  unsubscribe from this group, send an email  to:
soapbuilders-unsubscribe@yahoogroups.com




To  unsubscribe from this group, send an email  to:
soapbuilders-unsubscribe@yahoogroups.com



                                                                           
                                Yahoo! Groups Sponsor                      
                                                                           
                                                                           
                                                                           
                                                                           
                                                        [IMAGE]            
               [IMAGE]                                                     
                                                                           
                                                                           
                                                          !                
                                  www. .com                                
                                                                           
                                                                           
                                                                           
          [IMAGE]                                                          
                                                                           


To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com








To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com

Hi Sanjiva,

Per your suggestion I've started a WSDL discussion group on yahoo groups -
here's the
reachability info:

Post message: wsdl@yahoogroups.com
Subscribe:  wsdl-subscribe@yahoogroups.com
Unsubscribe:  wsdl-unsubscribe@yahoogroups.com
List owner:  wsdl-owner@yahoogroups.com
URL: http://groups.yahoo.com/group/wsdl

Cheers,
Tony

> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:sanjiva@...]
> Sent: Thursday, February 01, 2001 11:43 AM
> To: soapbuilders@yahoogroups.com; Apache SOAP; soap@...
> Cc: Paco Curbera; erikc@...
> Subject: another list for WSDL discussions?
>
>
> There are WSDL discussions going on in various lists. IMO its time
> to create a WSDL discussion list. What do u think? I'd like to
> separate it from SOAP because while WSDL is useful in the SOAP
> context, its actually quite independent from SOAP too.
>
> If there's consensus, can someone please volunteer to do it? We could
> do another Yahoo! group thing or whatever.
>
> Thanks,
>
> Sanjiva.
>
>
>

There are WSDL discussions going on in various lists. IMO its time
to create a WSDL discussion list. What do u think? I'd like to
separate it from SOAP because while WSDL is useful in the SOAP
context, its actually quite independent from SOAP too.

If there's consensus, can someone please volunteer to do it? We could
do another Yahoo! group thing or whatever.

Thanks,

Sanjiva.

Hi Tony,

What I'm actually looking for is a service that doesn't put in the xsi:type
stuff and relies on WSDL/SDL/whatever to get the knowledge of the types of
parameters of a call. We recently put in support in Apache SOAP to handle
that and I haven't been able to find any complex type tests. I wrote a
simpel test to talk to your guidgen server (written in MS SOAP I believe)
and it works fine.

Sanjiva.

"Tony Hong" <thong@...> on 01/31/2001 08:17:32 PM

Please respond to soapbuilders@yahoogroups.com

To:   <soapbuilders@yahoogroups.com>
cc:
Subject:  RE: [soapbuilders] Interoperability lab




Sanjiva,

One  other note -  to illustrate the existing struct array test, here is
the  request/response wiredump. In
this  example, it's a Apache 2.0 client hitting a SOAPLite server (it works
successfully) . Let me know if
this  is what you're thinking about, or if you need something different.
Thanks

Tony

----------- Apache Requst  -----------------------

POST  /perl/soaplite.cgi HTTP/1.0
Host: tony:8080
Content-Type:  text/xml
Content- Length: 541
SOAPAction:  "urn:xmethodsInterop#echoStruct"

<SOAP-ENV:Envelope  xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/"  xmlns:xsi="
http://www.w3.org/1999/XMLSchema-instance"  xmlns:xsd="
http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<ns1:echoStruct  xmlns:ns1="urn:xmethodsInterop"  SOAP-ENV:encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/">
<echo  xsi:type="ns1:SOAPStruct">
<varInt  xsi:type="xsd:int">3</varInt>
<varFloat  xsi:type="xsd:float">1.2</varFloat>
<varString  xsi:type="xsd:string">Hello</varString>
</echo>
</ns1:echoStruct>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

------------- SOAPLite  response --------------------------

HTTP/1.1 200 OK
Content- Length:  672
Content-Type: text/xml
glue-routing: true
date: Thu, 01 Feb 2001  01:11:21 GMT
server: Apache/1.3.14 (Unix) PHP/4.0.1pl2
soapserver:  SOAP::Lite/Perl/0.45

<?xml version="1.0"  encoding="UTF-8"?><SOAP-ENV:Envelope  xmlns:SOAP-ENC="
http://schemas.xmlsoap.org/soap/encoding/"  SOAP-ENV:encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/"  xmlns:xsi="
http://www.w3.org/1999/XMLSchema-instance"  xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/"  xmlns:xsd="
http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<namesp1:echoStructResponse  xmlns:namesp1="urn:xmethodsInterop">
<SOAPStruct  xsi:type="namesp1:SOAPStruct">
<varFloat  xsi:type="xsd:float">1.2</varFloat>
<varString  xsi:type="xsd:string">Hello</varString>
<varInt  xsi:type="xsd:int">3</varInt>
</SOAPStruct>
</namesp1:echoStructResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

-----Original Message-----
From: Tony  Hong [mailto:thong@...]
Sent: Wednesday, January 31, 2001  4:57 PM
To: soapbuilders@yahoogroups.com
Subject: RE:  [soapbuilders] Interoperability lab


Hi  Sanjiva,

Thanks, I'm glad you find the idea  useful!

The  yahoo group is listed now - I accidently delisted it from their
directory, but  it's
visible again. Just search for"soapbuilders"  at groups.yahoo.com and you
should
see  it pop up .

The  testbed as I'vedescribed has an "echoStruct" and "echoStructArray"
methods -
I've built this service already for  Apache and SOAP::Lite - for Apache,
the service uses
the  Bean serializer to map to/from a simple object. See

http://www.xmethods.net/detail.html?id=10  for SOAP::Lite
and
http://www.xmethods.net/detail.html?id=11   for Apache

Is  this what you are thinking of?

As  far as MS or 4s4c, I'm not sure of any other existing services that
involve
complex types - Simon, do you know of  any?

If  you describe the kind of type/structure you'd like to see built as an
"echo"  , I can make sure its part
of  the target test set and start the construction in a variety of
implementations, including the ones
you  mention.

Cheers,
Tony


-----Original Message-----
From: Sanjiva Weerawarana  [mailto:sanjiva@...]
Sent: Wednesday, January 31, 2001 9:42  AM
To: soapbuilders@yahoogroups.com
Subject: Re:  [soapbuilders] Interoperability lab


Hi  Tony,

I think this is a great idea! Thanks for starting the  work!

Do u know of a service implemented with MS SOAP, 4S4C, ... etc.  that uses
complex types and is available on the net? I'm trying to test  the apache
soap interoperabilty using complex types with non-Apache SOAP  services and
I can't seem to find interesting services to  try.

Also, what's the Yahoo group for this? I can't seem to find the  group to
change my email  address!

Bye,

Sanjiva.

Jacek Kopecky  <jacek@...> on 01/31/2001 10:23:07 AM

Please respond to  soapbuilders@yahoogroups.com

To:   Soapbuilders  <soapbuilders@yahoogroups.com>
cc:
Subject:  Re:  [soapbuilders] Interoperability lab



I'd add a circular  structure:

LinkedList echoLinkedList(LinkedList  linkedList)

where the definition in Java would be

public class  LinkedList {
    int x;
    LinkedList  next;
}

which means nullable and referenced next part. Sending a  circular list
through might also help.  8-)

                             Jacek  Kopecky
                                Idoox



On Wed, 31 Jan 2001, Tony Hong wrote:

> Hi  all
>
> I've mentioned to a couple of you that I'm going to  create
> an interoperability testbed. I'd like to get some  feedback
> from this group.
>
> For each if a number of  different SOAP implemenation, I'm
> planning to host a service that  exposes these methods
>
> String echoString(String  inputString)
> String[] echoStringArrray(String[]  inputStringArray)
> Integer echoInteger(Integer inputInteger)
>  Integer[] echoIntegerArray(Integer[] inputIntegerArray)
> Float  echoFloat(Float inputFloat)
> Float[] echoFloatArray(Float[]  inputFloatArray)
> SOAPStruct echoStruct( SOAPStruct  inputStruct)
> SOAPStruct[] echoStructArray (SOAPStruct[]  inputStructArray)
>
> Where SOAPStruct is a simple structure  with integer, float, and
> string fields.
>
> Other  possibilities include:
> Hashmap / Associative array , using the  encoding proposed by
> the Apache folks.
> XML  Documents
>
> This "echo" service does nothing really useful  except
> illustrate the ability of the service to accept a  clients
> envelope, deserialize the types correctly, and then
>  reserialize the respones into something that the client
> can see if  it understands.
>
> I built this service for Apache 2.0 and  SOAP::Lite a few
> months ago, and I think Paul Kulchenko will agree  that
> it's been really useful for testing interop  issues.
>
>
> In addition to exposing these services, I  also plan to:
>
> * Publish wiredumps of the request and  response envelopes
> that each implementation uses - ie, each  implementations
> client
> * For those implementations that  dynamically generate
> WSDL, I will publish the WSDL generated for  each of these
> methods.
>
> I think this is a first step  to REALLY filling out those issues
> lists for SOAP and WSDL  interoperability. It's much easier to
> see the issues when all this  info is right in front of you.
>
> My question here is
>
> Does this set of types/methods make sense? Would you  modify
> this list in any way?
>
> Thanks for any  feedback!
>
> Tony
>
>  ----------------------------------------
> XMethods Web Services  Listings
> http://www.xmethods.net
>
>
>  To unsubscribe from this group, send an email to:
>  soapbuilders-unsubscribe@yahoogroups.com
>
>
>



To  unsubscribe from this group, send an email  to:
soapbuilders-unsubscribe@yahoogroups.com








To  unsubscribe from this group, send an email  to:
soapbuilders-unsubscribe@yahoogroups.com




To  unsubscribe from this group, send an email  to:
soapbuilders-unsubscribe@yahoogroups.com




                                 Yahoo! Groups Sponsor




                                                         [IMAGE]
                [IMAGE]


                                                           !
                                   www. .com



           [IMAGE]



  To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com

-----Original Message-----
From: Jacek Kopecky [mailto:jacek@...]
Sent: Wednesday, January 31, 2001 7:19 AM
To: soapbuilders@yahoogroups.com
Subject: Re: [soapbuilders] WSDL and method names

> > On a slightly different note, while i was working on the WSDL
> > generator for 4s4c, i tried various WSDL toolkits, and in
> > particular i
> > tried doing some array / complex type inter-op, and i couldn't get
> > of them to work cross-tool for arrays or complex types.
> Right, there (at least in SOAP::Lite) is no support for arrays and
> complex types. I don't want to implements it before I'll have clear
> understanding how to map it to user input.

When we were implementing our WSDL parser for our stub-generating
tools, we decided to go with some subset of XML Scheme that seemed to
describe the complex types the best.

> > I'd like to propose that we workup some well documented examples of
> > what WSDL should look like, and try and resolve some of the
> > outstanding issues that Tony Hong has already raised (which part of
> > WSDL controls the method names / responses, one way vs empty
> > response etc )
> It would be great! Who will take the lead? Author? :))

Attached is our demo WSDL description where we use both structures
and arrays. Comments welcome. 8-)

This WSDL description is parsable with version 1.0 of IdooXoap and
describes a (very demo-ish) service at our server soap.idoox.net. I
can post example requests sent by stubs generated from this WSDL so
that you know how we interpret the WSDL description.

I already know about one thing that we fixed after 1.0 that is
probably a problem with our understanding of WSDL, it's the body
element's namespace that isn't being put there in 1.0.

I think this might be a good starting point for creating that
well-documented example WSDL.

Enjoy! 8-)

                            Jacek Kopecky
                               Idoox


To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com

-----Original Message-----
From: Simon Fell [mailto:soap@...]
Sent: Thursday, February 01, 2001 12:23 AM
To: soapbuilders@yahoogroups.com
Subject: Re: [soapbuilders] Interoperability lab

I've got an implementation of this running, i'll try and get it on a
public server tomorrow. I'm testing with SOAP::Lite as a client, can
anyone show me how to call the echoStruct method, i'm having trouble
getting the values nested in the inputStruct element (my perl skills
can only get better from this point <g>)

this is what i currently have

my @struct = (
      SOAP::Data->name(varInt => 42),
      SOAP::Data->name(varFloat => 42.42),
      SOAP::Data->name(varString => "SOAP::Lite to 4s4c")
      ) ;

my @parameters = (
      SOAP::Data->name(inputStruct => @struct )
      ) ;
     
print @{$soap->echoStruct(@parameters)->method}{'outputStruct'} , "\n"
;


For reference here are traces for the call to echoStringArray, one
thing i did notice is that SOAP::Lite types the array as namesp2:Array
whilst i'm typing it as SOAP-ENC:Array.

Cheers
Simon

------------------ SOAP::Lite request ---------------------------
POST /ilab/soap.asp HTTP/1.0
Host: localhost:8080
User-Agent: SOAP::Lite/Perl/0.45
Content-Type: text/xml
SOAPAction: "urn:xmethodsInterop#echoStringArray"

<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"><SOAP-ENV:Body>
<namesp2:echoStringArray xmlns:namesp2="urn:xmethodsInterop">
<inputStringArray SOAP-ENC:arrayType="xsd:string[3]"
xsi:type="namesp2:Array">
<c-gensym9 xsi:type="xsd:string">SOAP::Lite</c-gensym9>
<c-gensym9 xsi:type="xsd:string">to</c-gensym9>
<c-gensym9 xsi:type="xsd:string">4s4c</c-gensym9>
</inputStringArray></namesp2:echoStringArray>
</SOAP-ENV:Body></SOAP-ENV:Envelope>


---------------------- 4s4c Response -----------------------------
HTTP/1.1 200 OK
Server: Microsoft-IIS/5.0
Date: Thu, 01 Feb 2001 08:09:24 GMT
Connection: Keep-Alive
Content-Type: text/xml
Expires: Thu, 01 Feb 2001 08:09:24 GMT
Set-Cookie: ASPSESSIONIDGGQGQPMO=OOMLALIAMAFPCEFMOJNBNGGN; path=/
Cache-control: private

<?xml version="1.0"?><SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body><m:echoStringArrayResponse
xmlns:m="urn:xmethodsInterop">
<outputStringArray xsi:type="SOAP-ENC:Array"
SOAP-ENC:arrayType="xsd:string[3]">
<item xsi:type="xsd:string">SOAP::Lite</item>
<item xsi:type="xsd:string">to</item>
<item xsi:type="xsd:string">4s4c</item>
</outputStringArray></m:echoStringArrayResponse>
</SOAP-ENV:Body></SOAP-ENV:Envelope>



On Wed, 31 Jan 2001 17:17:32 -0800, in soap you wrote:

>Sanjiva,
>
>One other note -  to illustrate the existing struct array test, here is the
>request/response wiredump. In
>this example, it's a Apache 2.0 client hitting a SOAPLite server (it works
>successfully) . Let me know if
>this is what you're thinking about, or if you need something different.
>Thanks
>
>Tony
>
>----------- Apache Requst -----------------------
>
>POST /perl/soaplite.cgi HTTP/1.0
>Host: tony:8080
>Content-Type: text/xml
>Content- Length: 541
>SOAPAction: "urn:xmethodsInterop#echoStruct"
>
><SOAP-ENV:Envelope
>xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
>xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
>xmlns:xsd="http://www.w3.org/1999/XMLSchema">
><SOAP-ENV:Body>
><ns1:echoStruct xmlns:ns1="urn:xmethodsInterop"
>SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
><echo xsi:type="ns1:SOAPStruct">
><varInt xsi:type="xsd:int">3</varInt>
><varFloat xsi:type="xsd:float">1.2</varFloat>
><varString xsi:type="xsd:string">Hello</varString>
></echo>
></ns1:echoStruct>
></SOAP-ENV:Body>
></SOAP-ENV:Envelope>
>
>------------- SOAPLite response --------------------------
>
>HTTP/1.1 200 OK
>Content- Length: 672
>Content-Type: text/xml
>glue-routing: true
>date: Thu, 01 Feb 2001 01:11:21 GMT
>server: Apache/1.3.14 (Unix) PHP/4.0.1pl2
>soapserver: SOAP::Lite/Perl/0.45
>
><?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
>xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
>SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
>xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
>xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
>xmlns:xsd="http://www.w3.org/1999/XMLSchema">
><SOAP-ENV:Body>
><namesp1:echoStructResponse xmlns:namesp1="urn:xmethodsInterop">
><SOAPStruct xsi:type="namesp1:SOAPStruct">
><varFloat xsi:type="xsd:float">1.2</varFloat>
><varString xsi:type="xsd:string">Hello</varString>
><varInt xsi:type="xsd:int">3</varInt>
></SOAPStruct>
></namesp1:echoStructResponse>
></SOAP-ENV:Body>
></SOAP-ENV:Envelope>
>
>-----Original Message-----
>From: Tony Hong [mailto:thong@...]
>Sent: Wednesday, January 31, 2001 4:57 PM
>To: soapbuilders@yahoogroups.com
>Subject: RE: [soapbuilders] Interoperability lab
>
>
>  Hi Sanjiva,
>
>  Thanks, I'm glad you find the idea useful!
>
>  The yahoo group is listed now - I accidently delisted it from their
>directory, but it's
>  visible again. Just search for "soapbuilders" at groups.yahoo.com and you
>should
>  see it pop up .
>
>  The testbed as I've described has an "echoStruct" and "echoStructArray"
>methods -
>  I've built this service already for Apache and SOAP::Lite - for Apache,
>the service uses
>  the Bean serializer to map to/from a simple object. See
>
>  http://www.xmethods.net/detail.html?id=10 for SOAP::Lite
>  and
>  http://www.xmethods.net/detail.html?id=11  for Apache
>
>  Is this what you are thinking of?
>
>  As far as MS or 4s4c, I'm not sure of any other existing services that
>involve
>  complex types - Simon, do you know of any?
>
>  If you describe the kind of type/structure you'd like to see built as an
>"echo" , I can make sure its part
>  of the target test set and start the construction in a variety of
>implementations, including the ones
>  you mention.
>
>  Cheers,
>  Tony
>
>
>    -----Original Message-----
>    From: Sanjiva Weerawarana [mailto:sanjiva@...]
>    Sent: Wednesday, January 31, 2001 9:42 AM
>    To: soapbuilders@yahoogroups.com
>    Subject: Re: [soapbuilders] Interoperability lab
>
>
>
>    Hi Tony,
>
>    I think this is a great idea! Thanks for starting the work!
>
>    Do u know of a service implemented with MS SOAP, 4S4C, ... etc. that
>uses
>    complex types and is available on the net? I'm trying to test the apache
>    soap interoperabilty using complex types with non-Apache SOAP services
>and
>    I can't seem to find interesting services to try.
>
>    Also, what's the Yahoo group for this? I can't seem to find the group to
>    change my email address!
>
>    Bye,
>
>    Sanjiva.
>
>    Jacek Kopecky <jacek@...> on 01/31/2001 10:23:07 AM
>
>    Please respond to soapbuilders@yahoogroups.com
>
>    To:   Soapbuilders <soapbuilders@yahoogroups.com>
>    cc:
>    Subject:  Re: [soapbuilders] Interoperability lab
>
>
>
>    I'd add a circular structure:
>
>    LinkedList echoLinkedList(LinkedList linkedList)
>
>    where the definition in Java would be
>
>    public class LinkedList {
>        int x;
>        LinkedList next;
>    }
>
>    which means nullable and referenced next part. Sending a circular list
>    through might also help. 8-)
>
>                                Jacek Kopecky
>                                   Idoox
>
>
>
>    On Wed, 31 Jan 2001, Tony Hong wrote:
>
>    > Hi all
>    >
>    > I've mentioned to a couple of you that I'm going to create
>    > an interoperability testbed. I'd like to get some feedback
>    > from this group.
>    >
>    > For each if a number of different SOAP implemenation, I'm
>    > planning to host a service that exposes these methods
>    >
>    > String echoString(String inputString)
>    > String[] echoStringArrray(String[] inputStringArray)
>    > Integer echoInteger(Integer inputInteger)
>    > Integer[] echoIntegerArray(Integer[] inputIntegerArray)
>    > Float echoFloat(Float inputFloat)
>    > Float[] echoFloatArray(Float[] inputFloatArray)
>    > SOAPStruct echoStruct( SOAPStruct inputStruct)
>    > SOAPStruct[] echoStructArray (SOAPStruct[] inputStructArray)
>    >
>    > Where SOAPStruct is a simple structure with integer, float, and
>    > string fields.
>    >
>    > Other possibilities include:
>    > Hashmap / Associative array , using the encoding proposed by
>    > the Apache folks.
>    > XML Documents
>    >
>    > This "echo" service does nothing really useful except
>    > illustrate the ability of the service to accept a clients
>    > envelope, deserialize the types correctly, and then
>    > reserialize the respones into something that the client
>    > can see if it understands.
>    >
>    > I built this service for Apache 2.0 and SOAP::Lite a few
>    > months ago, and I think Paul Kulchenko will agree that
>    > it's been really useful for testing interop issues.
>    >
>    >
>    > In addition to exposing these services, I also plan to:
>    >
>    > * Publish wiredumps of the request and response envelopes
>    > that each implementation uses - ie, each implementations
>    > client
>    > * For those implementations that dynamically generate
>    > WSDL, I will publish the WSDL generated for each of these
>    > methods.
>    >
>    > I think this is a first step to REALLY filling out those issues
>    > lists for SOAP and WSDL interoperability. It's much easier to
>    > see the issues when all this info is right in front of you.
>    >
>    > My question here is :
>    >
>    > Does this set of types/methods make sense? Would you modify
>    > this list in any way?
>    >
>    > Thanks for any feedback!
>    >
>    > Tony



To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com

I've got an implementation of this running, i'll try and get it on a
public server tomorrow. I'm testing with SOAP::Lite as a client, can
anyone show me how to call the echoStruct method, i'm having trouble
getting the values nested in the inputStruct element (my perl skills
can only get better from this point <g>)

this is what i currently have

my @struct = (
	 SOAP::Data->name(varInt => 42),
	 SOAP::Data->name(varFloat => 42.42),
	 SOAP::Data->name(varString => "SOAP::Lite to 4s4c")
	 ) ;

my @parameters = (
	 SOAP::Data->name(inputStruct => @struct )
	 ) ;

print @{$soap->echoStruct(@parameters)->method}{'outputStruct'} , "\n"
;


For reference here are traces for the call to echoStringArray, one
thing i did notice is that SOAP::Lite types the array as namesp2:Array
whilst i'm typing it as SOAP-ENC:Array.

Cheers
Simon

------------------ SOAP::Lite request ---------------------------
POST /ilab/soap.asp HTTP/1.0
Host: localhost:8080
User-Agent: SOAP::Lite/Perl/0.45
Content-Length: 727
Content-Type: text/xml
SOAPAction: "urn:xmethodsInterop#echoStringArray"

<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"><SOAP-ENV:Body>
<namesp2:echoStringArray xmlns:namesp2="urn:xmethodsInterop">
<inputStringArray SOAP-ENC:arrayType="xsd:string[3]"
xsi:type="namesp2:Array">
<c-gensym9 xsi:type="xsd:string">SOAP::Lite</c-gensym9>
<c-gensym9 xsi:type="xsd:string">to</c-gensym9>
<c-gensym9 xsi:type="xsd:string">4s4c</c-gensym9>
</inputStringArray></namesp2:echoStringArray>
</SOAP-ENV:Body></SOAP-ENV:Envelope>


---------------------- 4s4c Response -----------------------------
HTTP/1.1 200 OK
Server: Microsoft-IIS/5.0
Date: Thu, 01 Feb 2001 08:09:24 GMT
Connection: Keep-Alive
Content-Length: 681
Content-Type: text/xml
Expires: Thu, 01 Feb 2001 08:09:24 GMT
Set-Cookie: ASPSESSIONIDGGQGQPMO=OOMLALIAMAFPCEFMOJNBNGGN; path=/
Cache-control: private

<?xml version="1.0"?><SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body><m:echoStringArrayResponse
xmlns:m="urn:xmethodsInterop">
<outputStringArray xsi:type="SOAP-ENC:Array"
SOAP-ENC:arrayType="xsd:string[3]">
<item xsi:type="xsd:string">SOAP::Lite</item>
<item xsi:type="xsd:string">to</item>
<item xsi:type="xsd:string">4s4c</item>
</outputStringArray></m:echoStringArrayResponse>
</SOAP-ENV:Body></SOAP-ENV:Envelope>



On Wed, 31 Jan 2001 17:17:32 -0800, in soap you wrote:

>Sanjiva,
>
>One other note -  to illustrate the existing struct array test, here is the
>request/response wiredump. In
>this example, it's a Apache 2.0 client hitting a SOAPLite server (it works
>successfully) . Let me know if
>this is what you're thinking about, or if you need something different.
>Thanks
>
>Tony
>
>----------- Apache Requst -----------------------
>
>POST /perl/soaplite.cgi HTTP/1.0
>Host: tony:8080
>Content-Type: text/xml
>Content- Length: 541
>SOAPAction: "urn:xmethodsInterop#echoStruct"
>
><SOAP-ENV:Envelope
>xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
>xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
>xmlns:xsd="http://www.w3.org/1999/XMLSchema">
><SOAP-ENV:Body>
><ns1:echoStruct xmlns:ns1="urn:xmethodsInterop"
>SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
><echo xsi:type="ns1:SOAPStruct">
><varInt xsi:type="xsd:int">3</varInt>
><varFloat xsi:type="xsd:float">1.2</varFloat>
><varString xsi:type="xsd:string">Hello</varString>
></echo>
></ns1:echoStruct>
></SOAP-ENV:Body>
></SOAP-ENV:Envelope>
>
>------------- SOAPLite response --------------------------
>
>HTTP/1.1 200 OK
>Content- Length: 672
>Content-Type: text/xml
>glue-routing: true
>date: Thu, 01 Feb 2001 01:11:21 GMT
>server: Apache/1.3.14 (Unix) PHP/4.0.1pl2
>soapserver: SOAP::Lite/Perl/0.45
>
><?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
>xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
>SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
>xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
>xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
>xmlns:xsd="http://www.w3.org/1999/XMLSchema">
><SOAP-ENV:Body>
><namesp1:echoStructResponse xmlns:namesp1="urn:xmethodsInterop">
><SOAPStruct xsi:type="namesp1:SOAPStruct">
><varFloat xsi:type="xsd:float">1.2</varFloat>
><varString xsi:type="xsd:string">Hello</varString>
><varInt xsi:type="xsd:int">3</varInt>
></SOAPStruct>
></namesp1:echoStructResponse>
></SOAP-ENV:Body>
></SOAP-ENV:Envelope>
>
>-----Original Message-----
>From: Tony Hong [mailto:thong@...]
>Sent: Wednesday, January 31, 2001 4:57 PM
>To: soapbuilders@yahoogroups.com
>Subject: RE: [soapbuilders] Interoperability lab
>
>
>  Hi Sanjiva,
>
>  Thanks, I'm glad you find the idea useful!
>
>  The yahoo group is listed now - I accidently delisted it from their
>directory, but it's
>  visible again. Just search for "soapbuilders" at groups.yahoo.com and you
>should
>  see it pop up .
>
>  The testbed as I've described has an "echoStruct" and "echoStructArray"
>methods -
>  I've built this service already for Apache and SOAP::Lite - for Apache,
>the service uses
>  the Bean serializer to map to/from a simple object. See
>
>  http://www.xmethods.net/detail.html?id=10 for SOAP::Lite
>  and
>  http://www.xmethods.net/detail.html?id=11  for Apache
>
>  Is this what you are thinking of?
>
>  As far as MS or 4s4c, I'm not sure of any other existing services that
>involve
>  complex types - Simon, do you know of any?
>
>  If you describe the kind of type/structure you'd like to see built as an
>"echo" , I can make sure its part
>  of the target test set and start the construction in a variety of
>implementations, including the ones
>  you mention.
>
>  Cheers,
>  Tony
>
>
>    -----Original Message-----
>    From: Sanjiva Weerawarana [mailto:sanjiva@...]
>    Sent: Wednesday, January 31, 2001 9:42 AM
>    To: soapbuilders@yahoogroups.com
>    Subject: Re: [soapbuilders] Interoperability lab
>
>
>
>    Hi Tony,
>
>    I think this is a great idea! Thanks for starting the work!
>
>    Do u know of a service implemented with MS SOAP, 4S4C, ... etc. that
>uses
>    complex types and is available on the net? I'm trying to test the apache
>    soap interoperabilty using complex types with non-Apache SOAP services
>and
>    I can't seem to find interesting services to try.
>
>    Also, what's the Yahoo group for this? I can't seem to find the group to
>    change my email address!
>
>    Bye,
>
>    Sanjiva.
>
>    Jacek Kopecky <jacek@...> on 01/31/2001 10:23:07 AM
>
>    Please respond to soapbuilders@yahoogroups.com
>
>    To:   Soapbuilders <soapbuilders@yahoogroups.com>
>    cc:
>    Subject:  Re: [soapbuilders] Interoperability lab
>
>
>
>    I'd add a circular structure:
>
>    LinkedList echoLinkedList(LinkedList linkedList)
>
>    where the definition in Java would be
>
>    public class LinkedList {
>        int x;
>        LinkedList next;
>    }
>
>    which means nullable and referenced next part. Sending a circular list
>    through might also help. 8-)
>
>                                Jacek Kopecky
>                                   Idoox
>
>
>
>    On Wed, 31 Jan 2001, Tony Hong wrote:
>
>    > Hi all
>    >
>    > I've mentioned to a couple of you that I'm going to create
>    > an interoperability testbed. I'd like to get some feedback
>    > from this group.
>    >
>    > For each if a number of different SOAP implemenation, I'm
>    > planning to host a service that exposes these methods
>    >
>    > String echoString(String inputString)
>    > String[] echoStringArrray(String[] inputStringArray)
>    > Integer echoInteger(Integer inputInteger)
>    > Integer[] echoIntegerArray(Integer[] inputIntegerArray)
>    > Float echoFloat(Float inputFloat)
>    > Float[] echoFloatArray(Float[] inputFloatArray)
>    > SOAPStruct echoStruct( SOAPStruct inputStruct)
>    > SOAPStruct[] echoStructArray (SOAPStruct[] inputStructArray)
>    >
>    > Where SOAPStruct is a simple structure with integer, float, and
>    > string fields.
>    >
>    > Other possibilities include:
>    > Hashmap / Associative array , using the encoding proposed by
>    > the Apache folks.
>    > XML Documents
>    >
>    > This "echo" service does nothing really useful except
>    > illustrate the ability of the service to accept a clients
>    > envelope, deserialize the types correctly, and then
>    > reserialize the respones into something that the client
>    > can see if it understands.
>    >
>    > I built this service for Apache 2.0 and SOAP::Lite a few
>    > months ago, and I think Paul Kulchenko will agree that
>    > it's been really useful for testing interop issues.
>    >
>    >
>    > In addition to exposing these services, I also plan to:
>    >
>    > * Publish wiredumps of the request and response envelopes
>    > that each implementation uses - ie, each implementations
>    > client
>    > * For those implementations that dynamically generate
>    > WSDL, I will publish the WSDL generated for each of these
>    > methods.
>    >
>    > I think this is a first step to REALLY filling out those issues
>    > lists for SOAP and WSDL interoperability. It's much easier to
>    > see the issues when all this info is right in front of you.
>    >
>    > My question here is :
>    >
>    > Does this set of types/methods make sense? Would you modify
>    > this list in any way?
>    >
>    > Thanks for any feedback!
>    >
>    > Tony

-----Original Message-----
From: Simon Fell [mailto:soap@...]
Sent: Wednesday, January 31, 2001 9:15 PM
To: soapbuilders@yahoogroups.com
Subject: Re: [soapbuilders] Interoperability lab

Hi,

The basic 4s4c install includes some tests with complex types,
including a shell version of the server end of the address book sample
in Apache SOAP. When we've decided on what the test set looks like i'm
more than happy to put together the 4s4c versions. Peter Drayton who
currently hosts a public reachable 4s4c server is having some major
connectivity problems at the minute, i'm hoping to get another public
server up soon.

Out of the MS toolkits, only the SOAP support in .NET supports complex
types and arrays, both ROPE and the new v2 beta 1 toolkit are limited
to simple types.

Cheers
Simon

On Wed, 31 Jan 2001 16:57:02 -0800, in soap you wrote:

>Hi Sanjiva,
>
>Thanks, I'm glad you find the idea useful!
>
>The yahoo group is listed now - I accidently delisted it from their
>directory, but it's
>visible again. Just search for "soapbuilders" at groups.yahoo.com and you
>should
>see it pop up .
>
>The testbed as I've described has an "echoStruct" and "echoStructArray"
>methods -
>I've built this service already for Apache and SOAP::Lite - for Apache, the
>service uses
>the Bean serializer to map to/from a simple object. See
>
>http://www.xmethods.net/detail.html?id=10 for SOAP::Lite
>and
>http://www.xmethods.net/detail.html?id=11  for Apache
>
>Is this what you are thinking of?
>
>As far as MS or 4s4c, I'm not sure of any other existing services that
>involve
>complex types - Simon, do you know of any?
>
>If you describe the kind of type/structure you'd like to see built as an
>"echo" , I can make sure its part
>of the target test set and start the construction in a variety of
>implementations, including the ones
>you mention.
>
>Cheers,
>Tony
>
>
>  -----Original Message-----
>  From: Sanjiva Weerawarana [mailto:sanjiva@...]
>  Sent: Wednesday, January 31, 2001 9:42 AM
>  To: soapbuilders@yahoogroups.com
>  Subject: Re: [soapbuilders] Interoperability lab
>
>
>
>  Hi Tony,
>
>  I think this is a great idea! Thanks for starting the work!
>
>  Do u know of a service implemented with MS SOAP, 4S4C, ... etc. that uses
>  complex types and is available on the net? I'm trying to test the apache
>  soap interoperabilty using complex types with non-Apache SOAP services and
>  I can't seem to find interesting services to try.
>
>  Also, what's the Yahoo group for this? I can't seem to find the group to
>  change my email address!
>
>  Bye,
>
>  Sanjiva.
>
>  Jacek Kopecky <jacek@...> on 01/31/2001 10:23:07 AM
>
>  Please respond to soapbuilders@yahoogroups.com
>
>  To:   Soapbuilders <soapbuilders@yahoogroups.com>
>  cc:
>  Subject:  Re: [soapbuilders] Interoperability lab
>
>
>
>  I'd add a circular structure:
>
>  LinkedList echoLinkedList(LinkedList linkedList)
>
>  where the definition in Java would be
>
>  public class LinkedList {
>      int x;
>      LinkedList next;
>  }
>
>  which means nullable and referenced next part. Sending a circular list
>  through might also help. 8-)
>
>                              Jacek Kopecky
>                                 Idoox
>
>
>
>  On Wed, 31 Jan 2001, Tony Hong wrote:
>
>  > Hi all
>  >
>  > I've mentioned to a couple of you that I'm going to create
>  > an interoperability testbed. I'd like to get some feedback
>  > from this group.
>  >
>  > For each if a number of different SOAP implemenation, I'm
>  > planning to host a service that exposes these methods
>  >
>  > String echoString(String inputString)
>  > String[] echoStringArrray(String[] inputStringArray)
>  > Integer echoInteger(Integer inputInteger)
>  > Integer[] echoIntegerArray(Integer[] inputIntegerArray)
>  > Float echoFloat(Float inputFloat)
>  > Float[] echoFloatArray(Float[] inputFloatArray)
>  > SOAPStruct echoStruct( SOAPStruct inputStruct)
>  > SOAPStruct[] echoStructArray (SOAPStruct[] inputStructArray)
>  >
>  > Where SOAPStruct is a simple structure with integer, float, and
>  > string fields.
>  >
>  > Other possibilities include:
>  > Hashmap / Associative array , using the encoding proposed by
>  > the Apache folks.
>  > XML Documents
>  >
>  > This "echo" service does nothing really useful except
>  > illustrate the ability of the service to accept a clients
>  > envelope, deserialize the types correctly, and then
>  > reserialize the respones into something that the client
>  > can see if it understands.
>  >
>  > I built this service for Apache 2.0 and SOAP::Lite a few
>  > months ago, and I think Paul Kulchenko will agree that
>  > it's been really useful for testing interop issues.
>  >
>  >
>  > In addition to exposing these services, I also plan to:
>  >
>  > * Publish wiredumps of the request and response envelopes
>  > that each implementation uses - ie, each implementations
>  > client
>  > * For those implementations that dynamically generate
>  > WSDL, I will publish the WSDL generated for each of these
>  > methods.
>  >
>  > I think this is a first step to REALLY filling out those issues
>  > lists for SOAP and WSDL interoperability. It's much easier to
>  > see the issues when all this info is right in front of you.
>  >
>  > My question here is :
>  >
>  > Does this set of types/methods make sense? Would you modify
>  > this list in any way?
>  >
>  > Thanks for any feedback!
>  >
>  > Tony
>  >
>  > ----------------------------------------
>  > XMethods Web Services Listings
>  > http://www.xmethods.net
>  >
>  >
>  > To unsubscribe from this group, send an email to:
>  > soapbuilders-unsubscribe@yahoogroups.com
>  >
>  >
>  >
>
>
>
>  To unsubscribe from this group, send an email to:
>  soapbuilders-unsubscribe@yahoogroups.com
>
>
>
>
>
>
>
>        Yahoo! Groups Sponsor
>
>
>
>  To unsubscribe from this group, send an email to:
>  soapbuilders-unsubscribe@yahoogroups.com
>
>



To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com

Dave,

I took my findings on writing a WSDL file for Manila to the
soapbuilders list (we were discussing WSDL inter-op), and Paul pointed
out that /'s in element names don't appear to be valid XML. Is my
interpretation of the Manila SOAP spec[1] correct ? i.e. Manila
expects a SOAP request similar to

<S:Envelope ...>
<S:Body>
<css/get>
	 <username>...</username>
	 <password>...</password>
	 <siteName>...</siteName>
</css/get>
</S:Body>
</S:Envelope>

Cheers
Simon
[1]http://www.xml-rpc.com/manilaRpcSpec#callingManilaRpcHandlersUsingSoap


On Wed, 31 Jan 2001 06:29:02 -0800 (PST), in soap Paul Kulchenko
<paulclinger@...> wrote:

>Hi, Simon!
>
>--- Simon Fell <soap@...> wrote:
>> couple of separate issues here
>> 1. There is no reason why a soap request of <css/get>...</css/get>
>> needs to be mapped directly to a language method of css/get,
>> different
>> languages have different rules on legal names, and they are going
>> to have to escape them in a manner that works for that language.
>True, but if other implementation expect to get css/get there is no
>way for client to alter this name on wire.
>
>> 2. I had no trouble generating and parsing a SOAP message using
>> that
>> format, but i just had a quick look through the XML spec and i'm
>> not sure if it is a valid element name or not.
>[40]    STag    ::=    '<' Name (S Attribute)* S? '>'
> [5]    Name    ::=    (Letter | '_' | ':') (NameChar)*
>[84]    Letter    ::=    BaseChar | Ideographic
> [4]    NameChar    ::=    Letter | Digit | '.' | '-' | '_' | ':' |
>CombiningChar | Extender
>[85]    BaseChar    ::=    [#x0041-#x005A] | [#x0061-#x007A] | .....
>
>So, as I understand there is no place for '/'.
>
>Best wishes, Paul.

> Attached is our demo WSDL description where we use both structures
>and arrays. Comments welcome. 8-)

Thanks Jacek, i have a few comments.

1. in binding\operation\input\soap:body & output\soap:body
there's no "use" attribute, the WSDL spec says that this is required,
and if set to "encoded" as i think it should for your example, it also
needs an encodingStyle attribute e.g.

<operation name='revert'>
  <soap:operation soapAction=""/>
   <input>
    <soap:body use="encoded" namespace="http://my.org/structures.xsd"
	 encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
   </input>
   <output>
    <soap:body use="encoded" namespace="http://my.org/structures.xsd"
	 encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
   </output>
</operation>

2. under types you have a couple of type="soap:reference", i couldn't
find this in the spec at all.

3. you have the following definition
<complexType name="SimpleArray">
<sequence>
<element name="a" type="soap:reference" soap:reftype="my:SimpleStruct"
nullable="true"/>
<element name="b" type="soap:reference" soap:reftype="my:SimpleStruct"
nullable="true"/>
<element name="c" type="soap:reference" soap:reftype="my:SimpleStruct"
nullable="true"/>
<element name="d" type="soap:reference" soap:reftype="my:SimpleStruct"
nullable="true"/>
</sequence>
</complexType>

You've called this SimpleArray, but it looks more than a struct than
an array.

5. for your ArrayofInt you have
<complexType name="ArrayOfInt" base="soapenc:Array"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<all>
  <element name="x" type="xsd:int"/>
</all>
</complexType>

based on a disucsion[1] on soap@... with Martin Gudgen
i believe that arrays should be

<complexType name="ArrayOfint" base="soapenc:Array"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
  <sequence>
   <element name="item" type="xsd:int" minOccurs='0'
maxOccurs='unbounded' />
  </sequence>
</complexType>

Note that this is slightly different from Martins post and takes into
account the correct scoping of Array as per Jacek's example. This of
course is different to Erik Christensen's earlier array example[2]

6. The final issue is that over the version of the XML Schema in use,
the WSDL spec doesn't mandate a particular version or even mandate the
use of XML Schama's. This makes it nice and extensible, but a complete
nightmare from an inter-op point of view. Unfortunately the spec
doesn't indicate anyway for the client to indicate any preference in
which schema language it would like to receive type information in,
the likely result being that some OOB communication is used to pick a
schema language. RDDL is picking up momentum as a mechanism for
finding meta data available in many formats, it may be an interesting
exercise to see if a WSDL client could use RDDL to negotiate which
schema language it wanted type information in.


I think at this point i could tweak the 4s4c WSDL generator to output
the newer schema version, and it would likely inter-op with IdooXoap
at this point.

Cheers
Simon


[1]http://discuss.develop.com/archives/wa.exe?A2=ind0101&L=SOAP&P=R1343
[2]http://discuss.develop.com/archives/wa.exe?A2=ind0011&L=SOAP&P=R11363

Hi,

The basic 4s4c install includes some tests with complex types,
including a shell version of the server end of the address book sample
in Apache SOAP. When we've decided on what the test set looks like i'm
more than happy to put together the 4s4c versions. Peter Drayton who
currently hosts a public reachable 4s4c server is having some major
connectivity problems at the minute, i'm hoping to get another public
server up soon.

Out of the MS toolkits, only the SOAP support in .NET supports complex
types and arrays, both ROPE and the new v2 beta 1 toolkit are limited
to simple types.

Cheers
Simon

On Wed, 31 Jan 2001 16:57:02 -0800, in soap you wrote:

>Hi Sanjiva,
>
>Thanks, I'm glad you find the idea useful!
>
>The yahoo group is listed now - I accidently delisted it from their
>directory, but it's
>visible again. Just search for "soapbuilders" at groups.yahoo.com and you
>should
>see it pop up .
>
>The testbed as I've described has an "echoStruct" and "echoStructArray"
>methods -
>I've built this service already for Apache and SOAP::Lite - for Apache, the
>service uses
>the Bean serializer to map to/from a simple object. See
>
>http://www.xmethods.net/detail.html?id=10 for SOAP::Lite
>and
>http://www.xmethods.net/detail.html?id=11  for Apache
>
>Is this what you are thinking of?
>
>As far as MS or 4s4c, I'm not sure of any other existing services that
>involve
>complex types - Simon, do you know of any?
>
>If you describe the kind of type/structure you'd like to see built as an
>"echo" , I can make sure its part
>of the target test set and start the construction in a variety of
>implementations, including the ones
>you mention.
>
>Cheers,
>Tony
>
>
>  -----Original Message-----
>  From: Sanjiva Weerawarana [mailto:sanjiva@...]
>  Sent: Wednesday, January 31, 2001 9:42 AM
>  To: soapbuilders@yahoogroups.com
>  Subject: Re: [soapbuilders] Interoperability lab
>
>
>
>  Hi Tony,
>
>  I think this is a great idea! Thanks for starting the work!
>
>  Do u know of a service implemented with MS SOAP, 4S4C, ... etc. that uses
>  complex types and is available on the net? I'm trying to test the apache
>  soap interoperabilty using complex types with non-Apache SOAP services and
>  I can't seem to find interesting services to try.
>
>  Also, what's the Yahoo group for this? I can't seem to find the group to
>  change my email address!
>
>  Bye,
>
>  Sanjiva.
>
>  Jacek Kopecky <jacek@...> on 01/31/2001 10:23:07 AM
>
>  Please respond to soapbuilders@yahoogroups.com
>
>  To:   Soapbuilders <soapbuilders@yahoogroups.com>
>  cc:
>  Subject:  Re: [soapbuilders] Interoperability lab
>
>
>
>  I'd add a circular structure:
>
>  LinkedList echoLinkedList(LinkedList linkedList)
>
>  where the definition in Java would be
>
>  public class LinkedList {
>      int x;
>      LinkedList next;
>  }
>
>  which means nullable and referenced next part. Sending a circular list
>  through might also help. 8-)
>
>                              Jacek Kopecky
>                                 Idoox
>
>
>
>  On Wed, 31 Jan 2001, Tony Hong wrote:
>
>  > Hi all
>  >
>  > I've mentioned to a couple of you that I'm going to create
>  > an interoperability testbed. I'd like to get some feedback
>  > from this group.
>  >
>  > For each if a number of different SOAP implemenation, I'm
>  > planning to host a service that exposes these methods
>  >
>  > String echoString(String inputString)
>  > String[] echoStringArrray(String[] inputStringArray)
>  > Integer echoInteger(Integer inputInteger)
>  > Integer[] echoIntegerArray(Integer[] inputIntegerArray)
>  > Float echoFloat(Float inputFloat)
>  > Float[] echoFloatArray(Float[] inputFloatArray)
>  > SOAPStruct echoStruct( SOAPStruct inputStruct)
>  > SOAPStruct[] echoStructArray (SOAPStruct[] inputStructArray)
>  >
>  > Where SOAPStruct is a simple structure with integer, float, and
>  > string fields.
>  >
>  > Other possibilities include:
>  > Hashmap / Associative array , using the encoding proposed by
>  > the Apache folks.
>  > XML Documents
>  >
>  > This "echo" service does nothing really useful except
>  > illustrate the ability of the service to accept a clients
>  > envelope, deserialize the types correctly, and then
>  > reserialize the respones into something that the client
>  > can see if it understands.
>  >
>  > I built this service for Apache 2.0 and SOAP::Lite a few
>  > months ago, and I think Paul Kulchenko will agree that
>  > it's been really useful for testing interop issues.
>  >
>  >
>  > In addition to exposing these services, I also plan to:
>  >
>  > * Publish wiredumps of the request and response envelopes
>  > that each implementation uses - ie, each implementations
>  > client
>  > * For those implementations that dynamically generate
>  > WSDL, I will publish the WSDL generated for each of these
>  > methods.
>  >
>  > I think this is a first step to REALLY filling out those issues
>  > lists for SOAP and WSDL interoperability. It's much easier to
>  > see the issues when all this info is right in front of you.
>  >
>  > My question here is :
>  >
>  > Does this set of types/methods make sense? Would you modify
>  > this list in any way?
>  >
>  > Thanks for any feedback!
>  >
>  > Tony
>  >
>  > ----------------------------------------
>  > XMethods Web Services Listings
>  > http://www.xmethods.net
>  >
>  >
>  > To unsubscribe from this group, send an email to:
>  > soapbuilders-unsubscribe@yahoogroups.com
>  >
>  >
>  >
>
>
>
>  To unsubscribe from this group, send an email to:
>  soapbuilders-unsubscribe@yahoogroups.com
>
>
>
>
>
>
>
>        Yahoo! Groups Sponsor
>
>
>
>  To unsubscribe from this group, send an email to:
>  soapbuilders-unsubscribe@yahoogroups.com
>
>

Per Sanjiva's earlier email,

Even though the "soapbuilders" group has been relisted in the Yahoo
directory, it remains off the search indexes, so nothing shows up if
you search from the groups.yahoo.com front page (contrary to what I
said earlier).

You can reach the group page directly at

http://groups.yahoo.com/group/soapbuilders

Sorry for the confusion!

Tony





----------------------------------------
XMethods Web Services Listings
http://www.xmethods.net

-----Original Message-----
From: Jacek Kopecky [mailto:jacek@...]
Sent: Wednesday, January 31, 2001 7:23 AM
To: Soapbuilders
Subject: Re: [soapbuilders] Interoperability lab

I'd add a circular structure:

LinkedList echoLinkedList(LinkedList linkedList)

where the definition in Java would be

public class LinkedList {
    int x;
    LinkedList next;
}

which means nullable and referenced next part. Sending a circular list
through might also help. 8-)

                            Jacek Kopecky
                               Idoox



On Wed, 31 Jan 2001, Tony Hong wrote:

> Hi all
>
> I've mentioned to a couple of you that I'm going to create
> an interoperability testbed. I'd like to get some feedback
> from this group.
>
> For each if a number of different SOAP implemenation, I'm
> planning to host a service that exposes these methods
>
> String echoString(String inputString)
> String[] echoStringArrray(String[] inputStringArray)
> Integer echoInteger(Integer inputInteger)
> Integer[] echoIntegerArray(Integer[] inputIntegerArray)
> Float echoFloat(Float inputFloat)
> Float[] echoFloatArray(Float[] inputFloatArray)
> SOAPStruct echoStruct( SOAPStruct inputStruct)
> SOAPStruct[] echoStructArray (SOAPStruct[] inputStructArray)
>
> Where SOAPStruct is a simple structure with integer, float, and
> string fields.
>
> Other possibilities include:
> Hashmap / Associative array , using the encoding proposed by
> the Apache folks.
> XML Documents
>
> This "echo" service does nothing really useful except
> illustrate the ability of the service to accept a clients
> envelope, deserialize the types correctly, and then
> reserialize the respones into something that the client
> can see if it understands.
>
> I built this service for Apache 2.0 and SOAP::Lite a few
> months ago, and I think Paul Kulchenko will agree that
> it's been really useful for testing interop issues.
>
>
> In addition to exposing these services, I also plan to:
>
> * Publish wiredumps of the request and response envelopes
> that each implementation uses - ie, each implementations
> client
> * For those implementations that dynamically generate
> WSDL, I will publish the WSDL generated for each of these
> methods.
>
> I think this is a first step to REALLY filling out those issues
> lists for SOAP and WSDL interoperability. It's much easier to
> see the issues when all this info is right in front of you.
>
> My question here is :
>
> Does this set of types/methods make sense? Would you modify
> this list in any way?
>
> Thanks for any feedback!
>
> Tony
>
> ----------------------------------------
> XMethods Web Services Listings
> http://www.xmethods.net
>
>
> To unsubscribe from this group, send an email to:
> soapbuilders-unsubscribe@yahoogroups.com
>
>
>

-----Original Message-----
From: Jacek Kopecky [mailto:jacek@...]
Sent: Wednesday, January 31, 2001 7:23 AM
To: Soapbuilders
Subject: Re: [soapbuilders] Interoperability lab

I'd add a circular structure:

LinkedList echoLinkedList(LinkedList linkedList)

where the definition in Java would be

public class LinkedList {
    int x;
    LinkedList next;
}

which means nullable and referenced next part. Sending a circular list
through might also help. 8-)

                            Jacek Kopecky
                               Idoox



On Wed, 31 Jan 2001, Tony Hong wrote:

> Hi all
>
> I've mentioned to a couple of you that I'm going to create
> an interoperability testbed. I'd like to get some feedback
> from this group.
>
> For each if a number of different SOAP implemenation, I'm
> planning to host a service that exposes these methods
>
> String echoString(String inputString)
> String[] echoStringArrray(String[] inputStringArray)
> Integer echoInteger(Integer inputInteger)
> Integer[] echoIntegerArray(Integer[] inputIntegerArray)
> Float echoFloat(Float inputFloat)
> Float[] echoFloatArray(Float[] inputFloatArray)
> SOAPStruct echoStruct( SOAPStruct inputStruct)
> SOAPStruct[] echoStructArray (SOAPStruct[] inputStructArray)
>
> Where SOAPStruct is a simple structure with integer, float, and
> string fields.
>
> Other possibilities include:
> Hashmap / Associative array , using the encoding proposed by
> the Apache folks.
> XML Documents
>
> This "echo" service does nothing really useful except
> illustrate the ability of the service to accept a clients
> envelope, deserialize the types correctly, and then
> reserialize the respones into something that the client
> can see if it understands.
>
> I built this service for Apache 2.0 and SOAP::Lite a few
> months ago, and I think Paul Kulchenko will agree that
> it's been really useful for testing interop issues.
>
>
> In addition to exposing these services, I also plan to:
>
> * Publish wiredumps of the request and response envelopes
> that each implementation uses - ie, each implementations
> client
> * For those implementations that dynamically generate
> WSDL, I will publish the WSDL generated for each of these
> methods.
>
> I think this is a first step to REALLY filling out those issues
> lists for SOAP and WSDL interoperability. It's much easier to
> see the issues when all this info is right in front of you.
>
> My question here is :
>
> Does this set of types/methods make sense? Would you modify
> this list in any way?
>
> Thanks for any feedback!
>
> Tony
>
> ----------------------------------------
> XMethods Web Services Listings
> http://www.xmethods.net
>
>
> To unsubscribe from this group, send an email to:
> soapbuilders-unsubscribe@yahoogroups.com
>
>
>



To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com

Hi Sanjiva,

 

Thanks, I'm glad you find the idea useful!

 

The yahoo group is listed now - I accidently delisted it from their directory, but it's

visible again. Just search for "soapbuilders" at groups.yahoo.com and you should

see it pop up .

 

The testbed as I've described has an "echoStruct" and "echoStructArray" methods -

I've built this service already for Apache and SOAP::Lite - for Apache, the service uses

the Bean serializer to map to/from a simple object. See

 

http://www.xmethods.net/detail.html?id=10 for SOAP::Lite

and

http://www.xmethods.net/detail.html?id=11  for Apache

 

Is this what you are thinking of?

 

As far as MS or 4s4c, I'm not sure of any other existing services that involve

complex types - Simon, do you know of any?

 

If you describe the kind of type/structure you'd like to see built as an "echo" , I can make sure its part

of the target test set and start the construction in a variety of implementations, including the ones

you mention.

 

Cheers,

Tony

 

 

-----Original Message-----
From: Sanjiva Weerawarana [mailto:sanjiva@...]
Sent: Wednesday, January 31, 2001 9:42 AM
To: soapbuilders@yahoogroups.com
Subject: Re: [soapbuilders] Interoperability lab

Hi Tony,

I think this is a great idea! Thanks for starting the work!

Do u know of a service implemented with MS SOAP, 4S4C, ... etc. that uses
complex types and is available on the net? I'm trying to test the apache
soap interoperabilty using complex types with non-Apache SOAP services and
I can't seem to find interesting services to try.

Also, what's the Yahoo group for this? I can't seem to find the group to
change my email address!

Bye,

Sanjiva.

Jacek Kopecky <jacek@...> on 01/31/2001 10:23:07 AM

Please respond to soapbuilders@yahoogroups.com

To:   Soapbuilders <soapbuilders@yahoogroups.com>
cc:
Subject:  Re: [soapbuilders] Interoperability lab



I'd add a circular structure:

LinkedList echoLinkedList(LinkedList linkedList)

where the definition in Java would be

public class LinkedList {
    int x;
    LinkedList next;
}

which means nullable and referenced next part. Sending a circular list
through might also help. 8-)

                            Jacek Kopecky
                               Idoox



On Wed, 31 Jan 2001, Tony Hong wrote:

> Hi all
>
> I've mentioned to a couple of you that I'm going to create
> an interoperability testbed. I'd like to get some feedback
> from this group.
>
> For each if a number of different SOAP implemenation, I'm
> planning to host a service that exposes these methods
>
> String echoString(String inputString)
> String[] echoStringArrray(String[] inputStringArray)
> Integer echoInteger(Integer inputInteger)
> Integer[] echoIntegerArray(Integer[] inputIntegerArray)
> Float echoFloat(Float inputFloat)
> Float[] echoFloatArray(Float[] inputFloatArray)
> SOAPStruct echoStruct( SOAPStruct inputStruct)
> SOAPStruct[] echoStructArray (SOAPStruct[] inputStructArray)
>
> Where SOAPStruct is a simple structure with integer, float, and
> string fields.
>
> Other possibilities include:
> Hashmap / Associative array , using the encoding proposed by
> the Apache folks.
> XML Documents
>
> This "echo" service does nothing really useful except
> illustrate the ability of the service to accept a clients
> envelope, deserialize the types correctly, and then
> reserialize the respones into something that the client
> can see if it understands.
>
> I built this service for Apache 2.0 and SOAP::Lite a few
> months ago, and I think Paul Kulchenko will agree that
> it's been really useful for testing interop issues.
>
>
> In addition to exposing these services, I also plan to:
>
> * Publish wiredumps of the request and response envelopes
> that each implementation uses - ie, each implementations
> client
> * For those implementations that dynamically generate
> WSDL, I will publish the WSDL generated for each of these
> methods.
>
> I think this is a first step to REALLY filling out those issues
> lists for SOAP and WSDL interoperability. It's much easier to
> see the issues when all this info is right in front of you.
>
> My question here is :
>
> Does this set of types/methods make sense? Would you modify
> this list in any way?
>
> Thanks for any feedback!
>
> Tony
>
> ----------------------------------------
> XMethods Web Services Listings
> http://www.xmethods.net
>
>
> To unsubscribe from this group, send an email to:
> soapbuilders-unsubscribe@yahoogroups.com
>
>
>



To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com








To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com

To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com

-----Original Message-----
From: Sanjiva Weerawarana [mailto:sanjiva@...]
Sent: Wednesday, January 31, 2001 9:42 AM
To: soapbuilders@yahoogroups.com
Subject: Re: [soapbuilders] Interoperability lab

Hi Tony,

I think this is a great idea! Thanks for starting the work!

Do u know of a service implemented with MS SOAP, 4S4C, ... etc. that uses
complex types and is available on the net? I'm trying to test the apache
soap interoperabilty using complex types with non-Apache SOAP services and
I can't seem to find interesting services to try.

Also, what's the Yahoo group for this? I can't seem to find the group to
change my email address!

Bye,

Sanjiva.

Jacek Kopecky <jacek@...> on 01/31/2001 10:23:07 AM

Please respond to soapbuilders@yahoogroups.com

To:   Soapbuilders <soapbuilders@yahoogroups.com>
cc:
Subject:  Re: [soapbuilders] Interoperability lab



I'd add a circular structure:

LinkedList echoLinkedList(LinkedList linkedList)

where the definition in Java would be

public class LinkedList {
    int x;
    LinkedList next;
}

which means nullable and referenced next part. Sending a circular list
through might also help. 8-)

                            Jacek Kopecky
                               Idoox



On Wed, 31 Jan 2001, Tony Hong wrote:

> Hi all
>
> I've mentioned to a couple of you that I'm going to create
> an interoperability testbed. I'd like to get some feedback
> from this group.
>
> For each if a number of different SOAP implemenation, I'm
> planning to host a service that exposes these methods
>
> String echoString(String inputString)
> String[] echoStringArrray(String[] inputStringArray)
> Integer echoInteger(Integer inputInteger)
> Integer[] echoIntegerArray(Integer[] inputIntegerArray)
> Float echoFloat(Float inputFloat)
> Float[] echoFloatArray(Float[] inputFloatArray)
> SOAPStruct echoStruct( SOAPStruct inputStruct)
> SOAPStruct[] echoStructArray (SOAPStruct[] inputStructArray)
>
> Where SOAPStruct is a simple structure with integer, float, and
> string fields.
>
> Other possibilities include:
> Hashmap / Associative array , using the encoding proposed by
> the Apache folks.
> XML Documents
>
> This "echo" service does nothing really useful except
> illustrate the ability of the service to accept a clients
> envelope, deserialize the types correctly, and then
> reserialize the respones into something that the client
> can see if it understands.
>
> I built this service for Apache 2.0 and SOAP::Lite a few
> months ago, and I think Paul Kulchenko will agree that
> it's been really useful for testing interop issues.
>
>
> In addition to exposing these services, I also plan to:
>
> * Publish wiredumps of the request and response envelopes
> that each implementation uses - ie, each implementations
> client
> * For those implementations that dynamically generate
> WSDL, I will publish the WSDL generated for each of these
> methods.
>
> I think this is a first step to REALLY filling out those issues
> lists for SOAP and WSDL interoperability. It's much easier to
> see the issues when all this info is right in front of you.
>
> My question here is :
>
> Does this set of types/methods make sense? Would you modify
> this list in any way?
>
> Thanks for any feedback!
>
> Tony
>
> ----------------------------------------
> XMethods Web Services Listings
> http://www.xmethods.net
>
>
> To unsubscribe from this group, send an email to:
> soapbuilders-unsubscribe@yahoogroups.com
>
>
>



To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com








To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com

Hi Tony,

I think this is a great idea! Thanks for starting the work!

Do u know of a service implemented with MS SOAP, 4S4C, ... etc. that uses
complex types and is available on the net? I'm trying to test the apache
soap interoperabilty using complex types with non-Apache SOAP services and
I can't seem to find interesting services to try.

Also, what's the Yahoo group for this? I can't seem to find the group to
change my email address!

Bye,

Sanjiva.

Jacek Kopecky <jacek@...> on 01/31/2001 10:23:07 AM

Please respond to soapbuilders@yahoogroups.com

To:   Soapbuilders <soapbuilders@yahoogroups.com>
cc:
Subject:  Re: [soapbuilders] Interoperability lab



I'd add a circular structure:

LinkedList echoLinkedList(LinkedList linkedList)

where the definition in Java would be

public class LinkedList {
     int x;
     LinkedList next;
}

which means nullable and referenced next part. Sending a circular list
through might also help. 8-)

                             Jacek Kopecky
                                Idoox



On Wed, 31 Jan 2001, Tony Hong wrote:

  > Hi all
  >
  > I've mentioned to a couple of you that I'm going to create
  > an interoperability testbed. I'd like to get some feedback
  > from this group.
  >
  > For each if a number of different SOAP implemenation, I'm
  > planning to host a service that exposes these methods
  >
  > String echoString(String inputString)
  > String[] echoStringArrray(String[] inputStringArray)
  > Integer echoInteger(Integer inputInteger)
  > Integer[] echoIntegerArray(Integer[] inputIntegerArray)
  > Float echoFloat(Float inputFloat)
  > Float[] echoFloatArray(Float[] inputFloatArray)
  > SOAPStruct echoStruct( SOAPStruct inputStruct)
  > SOAPStruct[] echoStructArray (SOAPStruct[] inputStructArray)
  >
  > Where SOAPStruct is a simple structure with integer, float, and
  > string fields.
  >
  > Other possibilities include:
  > Hashmap / Associative array , using the encoding proposed by
  > the Apache folks.
  > XML Documents
  >
  > This "echo" service does nothing really useful except
  > illustrate the ability of the service to accept a clients
  > envelope, deserialize the types correctly, and then
  > reserialize the respones into something that the client
  > can see if it understands.
  >
  > I built this service for Apache 2.0 and SOAP::Lite a few
  > months ago, and I think Paul Kulchenko will agree that
  > it's been really useful for testing interop issues.
  >
  >
  > In addition to exposing these services, I also plan to:
  >
  > * Publish wiredumps of the request and response envelopes
  > that each implementation uses - ie, each implementations
  > client
  > * For those implementations that dynamically generate
  > WSDL, I will publish the WSDL generated for each of these
  > methods.
  >
  > I think this is a first step to REALLY filling out those issues
  > lists for SOAP and WSDL interoperability. It's much easier to
  > see the issues when all this info is right in front of you.
  >
  > My question here is :
  >
  > Does this set of types/methods make sense? Would you modify
  > this list in any way?
  >
  > Thanks for any feedback!
  >
  > Tony
  >
  > ----------------------------------------
  > XMethods Web Services Listings
  > http://www.xmethods.net
  >
  >
  > To unsubscribe from this group, send an email to:
  > soapbuilders-unsubscribe@yahoogroups.com
  >
  >
  >



To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com

I'd add a circular structure:

LinkedList echoLinkedList(LinkedList linkedList)

where the definition in Java would be

public class LinkedList {
     int x;
     LinkedList next;
}

which means nullable and referenced next part. Sending a circular list
through might also help. 8-)

                             Jacek Kopecky
                                Idoox



On Wed, 31 Jan 2001, Tony Hong wrote:

  > Hi all
  >
  > I've mentioned to a couple of you that I'm going to create
  > an interoperability testbed. I'd like to get some feedback
  > from this group.
  >
  > For each if a number of different SOAP implemenation, I'm
  > planning to host a service that exposes these methods
  >
  > String echoString(String inputString)
  > String[] echoStringArrray(String[] inputStringArray)
  > Integer echoInteger(Integer inputInteger)
  > Integer[] echoIntegerArray(Integer[] inputIntegerArray)
  > Float echoFloat(Float inputFloat)
  > Float[] echoFloatArray(Float[] inputFloatArray)
  > SOAPStruct echoStruct( SOAPStruct inputStruct)
  > SOAPStruct[] echoStructArray (SOAPStruct[] inputStructArray)
  >
  > Where SOAPStruct is a simple structure with integer, float, and
  > string fields.
  >
  > Other possibilities include:
  > Hashmap / Associative array , using the encoding proposed by
  > the Apache folks.
  > XML Documents
  >
  > This "echo" service does nothing really useful except
  > illustrate the ability of the service to accept a clients
  > envelope, deserialize the types correctly, and then
  > reserialize the respones into something that the client
  > can see if it understands.
  >
  > I built this service for Apache 2.0 and SOAP::Lite a few
  > months ago, and I think Paul Kulchenko will agree that
  > it's been really useful for testing interop issues.
  >
  >
  > In addition to exposing these services, I also plan to:
  >
  > * Publish wiredumps of the request and response envelopes
  > that each implementation uses - ie, each implementations
  > client
  > * For those implementations that dynamically generate
  > WSDL, I will publish the WSDL generated for each of these
  > methods.
  >
  > I think this is a first step to REALLY filling out those issues
  > lists for SOAP and WSDL interoperability. It's much easier to
  > see the issues when all this info is right in front of you.
  >
  > My question here is :
  >
  > Does this set of types/methods make sense? Would you modify
  > this list in any way?
  >
  > Thanks for any feedback!
  >
  > Tony
  >
  > ----------------------------------------
  > XMethods Web Services Listings
  > http://www.xmethods.net
  >
  >
  > To unsubscribe from this group, send an email to:
  > soapbuilders-unsubscribe@yahoogroups.com
  >
  >
  >

> > On a slightly different note, while i was working on the WSDL
  > > generator for 4s4c, i tried various WSDL toolkits, and in
  > > particular i
  > > tried doing some array / complex type inter-op, and i couldn't get
  > > of them to work cross-tool for arrays or complex types.
  > Right, there (at least in SOAP::Lite) is no support for arrays and
  > complex types. I don't want to implements it before I'll have clear
  > understanding how to map it to user input.

When we were implementing our WSDL parser for our stub-generating
tools, we decided to go with some subset of XML Scheme that seemed to
describe the complex types the best.

  > > I'd like to propose that we workup some well documented examples of
  > > what WSDL should look like, and try and resolve some of the
  > > outstanding issues that Tony Hong has already raised (which part of
  > > WSDL controls the method names / responses, one way vs empty
  > > response etc )
  > It would be great! Who will take the lead? Author? :))

  Attached is our demo WSDL description where we use both structures
and arrays. Comments welcome. 8-)

  This WSDL description is parsable with version 1.0 of IdooXoap and
describes a (very demo-ish) service at our server soap.idoox.net. I
can post example requests sent by stubs generated from this WSDL so
that you know how we interpret the WSDL description.

  I already know about one thing that we fixed after 1.0 that is
probably a problem with our understanding of WSDL, it's the body
element's namespace that isn't being put there in 1.0.

  I think this might be a good starting point for creating that
well-documented example WSDL.

  Enjoy! 8-)

                             Jacek Kopecky
                                Idoox

<?xml version="1.0"?>

<definitions targetNamespace="http://my.org/structures.wsdl"
           xmlns:tns=      "http://my.org/structures.wsdl"
           xmlns:my=       "http://my.org/structures.xsd"
           xmlns:xsd=      "http://www.w3.org/2000/10/XMLSchema"
           xmlns:soap=     "http://schemas.xmlsoap.org/wsdl/soap/"
           xmlns=          "http://schemas.xmlsoap.org/wsdl/">

     <!-- put -->
     <message name="put">
         <part name="x" type="xsd:int"/>
         <part name="y" type="xsd:int"/>
     </message>
     <message name="putResponse">
         <part name="return" type="my:SimpleStruct"/>
     </message>

     <!-- putTo -->
     <message name="putTo">
	 <part name="x" type="xsd:int"/>
	 <part name="y" type="xsd:int"/>
	 <part name="str" type="my:SimpleStruct"/>
     </message>
     <message name="putToResponse">
	 <part name="return" element="my:return"/>
	 <part name="str" type="my:SimpleStruct"/>
     </message>

     <!-- swap -->
     <message name="swap">
         <part name="str" type="my:SimpleStruct"/>
     </message>
     <message name="swapResponse">
	 <part name="return" element="my:return"/>
	 <part name="str" type="my:SimpleStruct"/>
     </message>

     <!-- makeCircle -->
     <message name="makeCircle">
	 <part name="list" element="my:list"/>
     </message>
     <message name="makeCircleResponse">
	 <part name="return" element="my:return"/>
	 <part name="list" element="my:list"/>
     </message>

     <!-- killCircle -->
     <message name="killCircle">
	 <part name="list" element="my:list"/>
     </message>
     <message name="killCircleResponse">
	 <part name="return" element="my:return"/>
	 <part name="list" element="my:list"/>
     </message>

     <!-- revert -->
     <message name="revert">
	 <part name="array" type="my:SimpleArray"/>
     </message>
     <message name="revertResponse">
	 <part name="return" element="my:return"/>
	 <part name="array" type="my:SimpleArray"/>
     </message>

     <!-- average -->
     <message name="average">
	 <part name="array" type="my:ArrayOfInt"/>
     </message>
     <message name="averageResponse">
	 <part name="return" type="xsd:float"/>
     </message>

     <portType name='StructuresPortType'>
         <operation name='put'>
	     <input name='put' message="tns:put"/>
	     <output message="tns:putResponse"/>
	 </operation>
         <operation name='putTo'>
	     <input name='putTo' message="tns:putTo"/>
	     <output message="tns:putToResponse"/>
	 </operation>
         <operation name='swap'>
	     <input name='swap' message="tns:swap"/>
	     <output message="tns:swapResponse"/>
	 </operation>
         <operation name='makeCircle'>
	     <input name='makeCircle' message="tns:makeCircle"/>
	     <output message="tns:makeCircleResponse"/>
	 </operation>
         <operation name='killCircle'>
	     <input name='killCircle' message="tns:killCircle"/>
	     <output message="tns:killCircleResponse"/>
	 </operation>
         <operation name='revert'>
	     <input name='revert' message="tns:revert"/>
	     <output message="tns:revertResponse"/>
	 </operation>
         <operation name='average'>
	     <input name='average' message="tns:average"/>
	     <output message="tns:averageResponse"/>
	 </operation>
     </portType>

     <binding name="StructuresSOAPBinding" type="tns:StructuresPortType">
         <soap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http"/>
         <operation name='put'>
	     <soap:operation soapAction=""/>
	     <input>
	         <soap:body namespace="http://my.org/structures.xsd"/>
             </input>
	     <output>
	         <soap:body namespace="http://my.org/structures.xsd"/>
             </output>
	 </operation>
         <operation name='putTo'>
	     <soap:operation soapAction=""/>
	     <input>
	         <soap:body namespace="http://my.org/structures.xsd"/>
             </input>
	     <output>
	         <soap:body namespace="http://my.org/structures.xsd"/>
             </output>
	 </operation>
         <operation name='swap'>
	     <soap:operation soapAction=""/>
	     <input>
	         <soap:body namespace="http://my.org/structures.xsd"/>
             </input>
	     <output>
	         <soap:body namespace="http://my.org/structures.xsd"/>
             </output>
	 </operation>
         <operation name='makeCircle'>
	     <soap:operation soapAction=""/>
	     <input>
	         <soap:body namespace="http://my.org/structures.xsd"/>
             </input>
	     <output>
	         <soap:body namespace="http://my.org/structures.xsd"/>
             </output>
	 </operation>
         <operation name='killCircle'>
	     <soap:operation soapAction=""/>
	     <input>
	         <soap:body namespace="http://my.org/structures.xsd"/>
             </input>
	     <output>
	         <soap:body namespace="http://my.org/structures.xsd"/>
             </output>
	 </operation>
         <operation name='revert'>
	     <soap:operation soapAction=""/>
	     <input>
	         <soap:body namespace="http://my.org/structures.xsd"/>
             </input>
	     <output>
	         <soap:body namespace="http://my.org/structures.xsd"/>
             </output>
	 </operation>
         <operation name='average'>
	     <soap:operation soapAction=""/>
	     <input>
	         <soap:body namespace="http://my.org/structures.xsd"/>
             </input>
	     <output>
	         <soap:body namespace="http://my.org/structures.xsd"/>
             </output>
	 </operation>
     </binding>

     <service name="Demo">
         <port name="StructuresPort" binding="tns:StructuresSOAPBinding">
	     <soap:address
location="http://localhost:8080/soap/servlet/soap/structures"/>
	 </port>
     </service>


     <types>
	 <schema targetNamespace="http://my.org/structures.xsd"
		 xmlns="http://www.w3.org/2000/10/XMLSchema"
		 xmlns:my=       "http://my.org/structures.xsd">

	     <element name="return" type="xsd:boolean" nullable="true"/>

	     <element name="list" type="soap:reference" soap:reftype="my:SimpleList"
nullable="true"/>

	     <!-- SimpleStruct -->
	     <complexType name="SimpleStruct">
		 <sequence>
		     <element name="a" type="xsd:int"/>
		     <element name="b" type="xsd:int"/>
		 </sequence>
	     </complexType>
	     <!-- SimpleList -->
	     <complexType name="SimpleList">
		 <sequence>
		     <element name="next" type="soap:reference" soap:reftype="my:SimpleList"
nullable="true"/>
		     <element name="x" type="xsd:int"/>
		 </sequence>
	     </complexType>
	     <!-- SimpleArray -->
	     <complexType name="SimpleArray">
		 <sequence>
		     <element name="a" type="soap:reference" soap:reftype="my:SimpleStruct"
nullable="true"/>
		     <element name="b" type="soap:reference" soap:reftype="my:SimpleStruct"
nullable="true"/>
		     <element name="c" type="soap:reference" soap:reftype="my:SimpleStruct"
nullable="true"/>
		     <element name="d" type="soap:reference" soap:reftype="my:SimpleStruct"
nullable="true"/>
		 </sequence>
	     </complexType>
	     <complexType name="ArrayOfInt" base="soapenc:Array"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
		 <all>
		     <element name="x" type="xsd:int"/>
		 </all>
	     </complexType>
	 </schema>
     </types>
</definitions>

Hi, Simon!

--- Simon Fell <soap@...> wrote:
> couple of separate issues here
> 1. There is no reason why a soap request of <css/get>...</css/get>
> needs to be mapped directly to a language method of css/get,
> different
> languages have different rules on legal names, and they are going
> to have to escape them in a manner that works for that language.
True, but if other implementation expect to get css/get there is no
way for client to alter this name on wire.

> 2. I had no trouble generating and parsing a SOAP message using
> that
> format, but i just had a quick look through the XML spec and i'm
> not sure if it is a valid element name or not.
[40]    STag    ::=    '<' Name (S Attribute)* S? '>'
  [5]    Name    ::=    (Letter | '_' | ':') (NameChar)*
[84]    Letter    ::=    BaseChar | Ideographic
  [4]    NameChar    ::=    Letter | Digit | '.' | '-' | '_' | ':' |
CombiningChar | Extender
[85]    BaseChar    ::=    [#x0041-#x005A] | [#x0061-#x007A] | .....

So, as I understand there is no place for '/'.

Best wishes, Paul.


__________________________________________________
Get personalized email addresses from Yahoo! Mail - only $35
a year!  http://personal.mail.yahoo.com/

hi tony,

what about some methods that either take no arguments
or return no value (void)? those combinations would
be useful to test.

cheers,
graham

-----Original Message-----
From: Tony Hong [mailto:thong@...]
Sent: Wednesday, January 31, 2001 2:39 AM
To: Soapbuilders
Subject: [soapbuilders] Interoperability lab


Hi all

I've mentioned to a couple of you that I'm going to create
an interoperability testbed. I'd like to get some feedback
from this group.

For each if a number of different SOAP implemenation, I'm
planning to host a service that exposes these methods

String echoString(String inputString)
String[] echoStringArrray(String[] inputStringArray)
Integer echoInteger(Integer inputInteger)
Integer[] echoIntegerArray(Integer[] inputIntegerArray)
Float echoFloat(Float inputFloat)
Float[] echoFloatArray(Float[] inputFloatArray)
SOAPStruct echoStruct( SOAPStruct inputStruct)
SOAPStruct[] echoStructArray (SOAPStruct[] inputStructArray)

Where SOAPStruct is a simple structure with integer, float, and
string fields.

Other possibilities include:
Hashmap / Associative array , using the encoding proposed by
the Apache folks.
XML Documents

This "echo" service does nothing really useful except
illustrate the ability of the service to accept a clients
envelope, deserialize the types correctly, and then
reserialize the respones into something that the client
can see if it understands.

I built this service for Apache 2.0 and SOAP::Lite a few
months ago, and I think Paul Kulchenko will agree that
it's been really useful for testing interop issues.


In addition to exposing these services, I also plan to:

* Publish wiredumps of the request and response envelopes
that each implementation uses - ie, each implementations
client
* For those implementations that dynamically generate
WSDL, I will publish the WSDL generated for each of these
methods.

I think this is a first step to REALLY filling out those issues
lists for SOAP and WSDL interoperability. It's much easier to
see the issues when all this info is right in front of you.

My question here is :

Does this set of types/methods make sense? Would you modify
this list in any way?

Thanks for any feedback!

Tony

----------------------------------------
XMethods Web Services Listings
http://www.xmethods.net


To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com

Hi all

I've mentioned to a couple of you that I'm going to create
an interoperability testbed. I'd like to get some feedback
from this group.

For each if a number of different SOAP implemenation, I'm
planning to host a service that exposes these methods

String echoString(String inputString)
String[] echoStringArrray(String[] inputStringArray)
Integer echoInteger(Integer inputInteger)
Integer[] echoIntegerArray(Integer[] inputIntegerArray)
Float echoFloat(Float inputFloat)
Float[] echoFloatArray(Float[] inputFloatArray)
SOAPStruct echoStruct( SOAPStruct inputStruct)
SOAPStruct[] echoStructArray (SOAPStruct[] inputStructArray)

Where SOAPStruct is a simple structure with integer, float, and
string fields.

Other possibilities include:
Hashmap / Associative array , using the encoding proposed by
the Apache folks.
XML Documents

This "echo" service does nothing really useful except
illustrate the ability of the service to accept a clients
envelope, deserialize the types correctly, and then
reserialize the respones into something that the client
can see if it understands.

I built this service for Apache 2.0 and SOAP::Lite a few
months ago, and I think Paul Kulchenko will agree that
it's been really useful for testing interop issues.


In addition to exposing these services, I also plan to:

* Publish wiredumps of the request and response envelopes
that each implementation uses - ie, each implementations
client
* For those implementations that dynamically generate
WSDL, I will publish the WSDL generated for each of these
methods.

I think this is a first step to REALLY filling out those issues
lists for SOAP and WSDL interoperability. It's much easier to
see the issues when all this info is right in front of you.

My question here is :

Does this set of types/methods make sense? Would you modify
this list in any way?

Thanks for any feedback!

Tony

----------------------------------------
XMethods Web Services Listings
http://www.xmethods.net

On Tue, 30 Jan 2001 21:35:04 -0800 (PST), in soap you wrote:

>Hi, Simon!
>
>--- Simon Fell <soap@...> wrote:
>> Most of us have been talking about WSDL issues on and off for a
>> while,
>> so i doubt this comes as a surprise to anyone, but i was looking at
>> writing a WSDL description for manila following Dave Winer's call
>> for
>> help on scripting.com. I had no trouble putting a basic WSDL file
>> together but i ran the results through both SOAP::Lite and IdooXoap
>> both choked with the same problem (and i'm guessing the other WSDL
>> toolkits would too) as the method names for manila have /'s in
>> them, e.g. css/get, css/checkIn
>True, but as I understand it's not a toolkit problem, because I could
>fix the name (for example change non-allowed symbols to '_'), but
>it'll have no use, since server won't understand modified name
>anyway. I don't know how they can choose method elements with '/' if
>it couldn't be properly encoded according to SOAP spec. Or I'm
>missing something?

couple of separate issues here
1. There is no reason why a soap request of <css/get>...</css/get>
needs to be mapped directly to a language method of css/get, different
languages have different rules on legal names, and they are going to
have to escape them in a manner that works for that language.
2. I had no trouble generating and parsing a SOAP message using that
format, but i just had a quick look through the XML spec and i'm not
sure if it is a valid element name or not.

>> On a slightly different note, while i was working on the WSDL
>> generator for 4s4c, i tried various WSDL toolkits, and in
>> particular i
>> tried doing some array / complex type inter-op, and i couldn't get
>> of them to work cross-tool for arrays or complex types.
>Right, there (at least in SOAP::Lite) is no support for arrays and
>complex types. I don't want to implements it before I'll have clear
>understanding how to map it to user input.

me and you both, i don't really want to start work on a WSDL client
until its better defined.

>> I'd like to propose that we workup some well documented examples of
>> what WSDL should look like, and try and resolve some of the
>> outstanding issues that Tony Hong has already raised (which part of
>> WSDL controls the method names / responses, one way vs empty
>> response etc )
>It would be great! Who will take the lead? Author? :))

I'm more that happy to try and drive this forward, however i'd be
interested in hearing Sanjiva's opinion of issues first (as one of the
WSDL authors).

Cheers
Simon

Hi, Simon!

--- Simon Fell <soap@...> wrote:
> Most of us have been talking about WSDL issues on and off for a
> while,
> so i doubt this comes as a surprise to anyone, but i was looking at
> writing a WSDL description for manila following Dave Winer's call
> for
> help on scripting.com. I had no trouble putting a basic WSDL file
> together but i ran the results through both SOAP::Lite and IdooXoap
> both choked with the same problem (and i'm guessing the other WSDL
> toolkits would too) as the method names for manila have /'s in
> them, e.g. css/get, css/checkIn
True, but as I understand it's not a toolkit problem, because I could
fix the name (for example change non-allowed symbols to '_'), but
it'll have no use, since server won't understand modified name
anyway. I don't know how they can choose method elements with '/' if
it couldn't be properly encoded according to SOAP spec. Or I'm
missing something?

> On a slightly different note, while i was working on the WSDL
> generator for 4s4c, i tried various WSDL toolkits, and in
> particular i
> tried doing some array / complex type inter-op, and i couldn't get
> of them to work cross-tool for arrays or complex types.
Right, there (at least in SOAP::Lite) is no support for arrays and
complex types. I don't want to implements it before I'll have clear
understanding how to map it to user input.

> I'd like to propose that we workup some well documented examples of
> what WSDL should look like, and try and resolve some of the
> outstanding issues that Tony Hong has already raised (which part of
> WSDL controls the method names / responses, one way vs empty
> response etc )
It would be great! Who will take the lead? Author? :))

Best wishes, Paul.

__________________________________________________
Get personalized email addresses from Yahoo! Mail - only $35
a year!  http://personal.mail.yahoo.com/

Hi all,

Most of us have been talking about WSDL issues on and off for a while,
so i doubt this comes as a surprise to anyone, but i was looking at
writing a WSDL description for manila following Dave Winer's call for
help on scripting.com. I had no trouble putting a basic WSDL file
together but i ran the results through both SOAP::Lite and IdooXoap
both choked with the same problem (and i'm guessing the other WSDL
toolkits would too) as the method names for manila have /'s in them,
e.g. css/get, css/checkIn

On a slightly different note, while i was working on the WSDL
generator for 4s4c, i tried various WSDL toolkits, and in particular i
tried doing some array / complex type inter-op, and i couldn't get of
them to work cross-tool for arrays or complex types.

I'd like to propose that we workup some well documented examples of
what WSDL should look like, and try and resolve some of the
outstanding issues that Tony Hong has already raised (which part of
WSDL controls the method names / responses, one way vs empty response
etc )

Cheers
Simon
www.pocketsoap.com