I looked at tclsoap.sf.net for mailing lists, web forums, etc. and,
since I didn't find any, decided to stop by here for information.

The sf.net site of released files for tclsoap are pretty old - nearly
six years old.  The front page status of changes seems to indicate
that the last change was nearly a year ago.

I had a question from a developer asking about SOAP::WSDL . When I
took a look at the CVS head that exists on the activestate ftp site, I
don't see that package included. There are 2 sample programs which do
a package require on it, but I don't see the code anywhere.

So I am wondering whether anyone is using the SOAP::WSDL package. If
so, where does one find it? And if it is in a package that has not yet
been released, is there an expected release date?

Thank you.

On Feb 26, 4:23=A0am, "Larry W. Virden" <lvir...@gmail.com> wrote:
> I looked at tclsoap.sf.net for mailing lists, web forums, etc. and,
> since I didn't find any, decided to stop by here for information.
>
> The sf.net site of released files for tclsoap are pretty old - nearly
> six years old. =A0The front page status of changes seems to indicate
> that the last change was nearly a year ago.
>
> I had a question from a developer asking about SOAP::WSDL . When I
> took a look at the CVS head that exists on the activestate ftp site, I
> don't see that package included. There are 2 sample programs which do
> a package require on it, but I don't see the code anywhere.
>
> So I am wondering whether anyone is using the SOAP::WSDL package. If
> so, where does one find it? And if it is in a package that has not yet
> been released, is there an expected release date?

A SOAP package that old is bound to be useless. Most web services have
moved from rpc/encoded (slow an proprietary) to document/literal
(faster and generic). And the entire conversation is encoded in a
"generic" WSDL file.

The best Tcl client is WS::Client. The most capable server is tWSDL/
TWiST. WS::Client still handles older stuff, tWSDL/TWiST only deals
with document/literal, but it also has a lot of library code that
could be used for client development.

On Mar 2, 2:44=A0am, "tom.rmadilo" <tom.rmad...@gmail.com> wrote:
> On Feb 26, 4:23=A0am, "Larry W. Virden" <lvir...@gmail.com> wrote:
>
> > I looked at tclsoap.sf.net for mailing lists, web forums, etc. and,
> > since I didn't find any, decided to stop by here for information.
>
> > The sf.net site of released files for tclsoap are pretty old - nearly
> > six years old. =A0The front page status of changes seems to indicate
> > that the last change was nearly a year ago.
>
> > I had a question from a developer asking about SOAP::WSDL . When I
> > took a look at the CVS head that exists on the activestate ftp site, I
> > don't see that package included. There are 2 sample programs which do
> > a package require on it, but I don't see the code anywhere.
>
> > So I am wondering whether anyone is using the SOAP::WSDL package. If
> > so, where does one find it? And if it is in a package that has not yet
> > been released, is there an expected release date?
>
> A SOAP package that old is bound to be useless. Most web services have
> moved from rpc/encoded (slow an proprietary) to document/literal
> (faster and generic). And the entire conversation is encoded in a
> "generic" WSDL file.
>
> The best Tcl client is WS::Client. The most capable server is tWSDL/
> TWiST. WS::Client still handles older stuff, tWSDL/TWiST only deals
> with document/literal, but it also has a lot of library code that
> could be used for client development.

also WS::Client is not perfect. some issues with complex types that I
faces never got resolved with this package and left me stuck:

http://groups.google.com/group/comp.lang.tcl/browse_thread/thread/e8524fd63=
1f3f52f/381851e732f21010?lnk=3Dgst&q=3Dyahalom#381851e732f21010

On Mar 1, 7:44=A0pm, "tom.rmadilo" <tom.rmad...@gmail.com> wrote:

> A SOAP package that old is bound to be useless. Most web services have
> moved from rpc/encoded (slow an proprietary) to document/literal
> (faster and generic). And the entire conversation is encoded in a
> "generic" WSDL file.
>

Thanks for the feedback. I will have to check with the developers to
see whether WS::Client is something in which they wish to investigate.

On Mar 2, 8:09=A0am, "Larry W. Virden" <lvir...@gmail.com> wrote:
> On Mar 1, 7:44=A0pm, "tom.rmadilo" <tom.rmad...@gmail.com> wrote:
>
> > A SOAP package that old is bound to be useless. Most web services have
> > moved from rpc/encoded (slow an proprietary) to document/literal
> > (faster and generic). And the entire conversation is encoded in a
> > "generic" WSDL file.
>
> Thanks for the feedback. I will have to check with the developers to
> see whether WS::Client is something in which they wish to investigate.

Hi, I need help on the tcl soap/webservices.
currently, trying with tclws and tclsoap.
But, tclws is constructing the elements with extr "xs:", so, server is
not understand the subelements.
Please advise with any clues.

URL: http://code.google.com/p/tclws/issues/detail?id=3D7
URL: http://code.google.com/p/tclws/issues/detail?id=3D8

Here are the details
Please provide any additional information below.
How to send the soap request - elements without "xs:" within method
element, as mentioned in the "What is expected output section".
My soap server (tomcat/aix2/wsld1.1), does not able to understand the
request,
because, element tags are prefixed with "xs:" under the method tag.

Please suggest, how to stop prefixing the "xs:" in the elements, which
are
parameters to method.


What steps will reproduce the problem?
1. package require WS::Client
2. ::WS::Client::GetAndParseWsdl $URL
3. ::WS::Client::CreateStubs emsprov
4. ::emsprov::getDevice "1" [list "options" a ] "1"
>> Error at tclsh prompt --
org.apache.axis2.databinding.ADBException: Unexpected subelement
transactionID


What version of the product are you using? On what operating system?
WebServices-1.1.2.zip
tDOM-0.8.2
tclsh8.5
x86_64 x86_64 x86_64 GNU/Linux SUSE

What is the expected output?

<soapenv:Envelope xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-
instance"
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema"
xmlns:soapenv=3D"http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn=3D"urn:emsprov">
   <soapenv:Header/>
   <soapenv:Body>
      <urn:getDevice
soapenv:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/">
         <transactionID xsi:type=3D"xsd:string">1</transactionID>
         <deviceUID xsi:type=3D"xsd:string">1</deviceUID>
         <options xsi:type=3D"urn:ArrayOfKeyValue">
            <!--Zero or more repetitions:-->
            <item xsi:type=3D"urn:KeyValue">
               <key xsi:type=3D"xsd:string">k1</key>
               <value xsi:type=3D"xsd:string">v1</value>
            </item>
         </options>
      </urn:getDevice>
   </soapenv:Body>
</soapenv:Envelope>


<soapenv:Envelope
xmlns:soapenv=3D"http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <ns1:getDeviceResponse xmlns:ns1=3D"urn:emsprov">
         <transactionID>1</transactionID>
         <status>0</status>
         <description/>
         <deviceUID>1</deviceUID>
         <developmentUID>1</developmentUID>
         <deviceType>deviceType</deviceType>
         <deviceModel>deviceModel</deviceModel>
         <deviceManufacturer>deviceManufacturer</deviceManufacturer>
         <deviceAttributes>
            <item>
               <key>Key1</key>
               <value>Value1</value>
            </item>
         </deviceAttributes>
      </ns1:getDeviceResponse>
   </soapenv:Body>
</soapenv:Envelope>

What do you see instead?
<?xml version=3D'1.0' encoding=3D'utf-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-
ENV=3D"http://schemas.xmlsoap.org/soap/envelope/"
xmlns:tns1=3D"urn:emsprov"
xmlns:xs=3D"http://www.w3.org/2001/XMLSchema"
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance">
  <SOAP-ENV:Body>
    <tns1:getDevice SOAP-
ENV:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/">
      <xs:transactionID xsi:type=3D"xs:string">1</xs:transactionID>
      <xs:deviceUID xsi:type=3D"xs:string">1</xs:deviceUID>
      <xs:options xsi:type=3D"xs:ArrayOfKeyValue" />
    </tns1:getDevice>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

<?xml version=3D'1.0' encoding=3D'utf-8'?>
<soapenv:Envelope
xmlns:soapenv=3D"http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:Body>
    <soapenv:Fault>
      <faultcode>soapenv:Server</faultcode>
      <faultstring>org.apache.axis2.databinding.ADBException:
Unexpected
subelement transactionID</faultstring>
      <detail />
    </soapenv:Fault>
  </soapenv:Body>
</soapenv:Envelope>

On Mar 25, 11:21=A0am, credit card fraud - citibank and spiceJet
<msubbare...@gmail.com> wrote:
> On Mar 2, 8:09=A0am, "Larry W. Virden" <lvir...@gmail.com> wrote:
>
> > On Mar 1, 7:44=A0pm, "tom.rmadilo" <tom.rmad...@gmail.com> wrote:
>
> > > A SOAP package that old is bound to be useless. Most web services hav=
e
> > > moved from rpc/encoded (slow an proprietary) to document/literal
> > > (faster and generic). And the entire conversation is encoded in a
> > > "generic" WSDL file.
>
> > Thanks for the feedback. I will have to check with the developers to
> > see whether WS::Client is something in which they wish to investigate.
>
> Hi, I need help on the tcl soap/webservices.
> currently, trying with tclws and tclsoap.
> But, tclws is constructing the elements with extr "xs:", so, server is
> not understand the subelements.
> Please advise with any clues.
>
> URL:http://code.google.com/p/tclws/issues/detail?id=3D7
> URL:http://code.google.com/p/tclws/issues/detail?id=3D8
>
> Here are the details
> Please provide any additional information below.
> How to send the soap request - elements without "xs:" within method
> element, as mentioned in the "What is expected output section".
> My soap server (tomcat/aix2/wsld1.1), does not able to understand the
> request,
> because, element tags are prefixed with "xs:" under the method tag.
>
> Please suggest, how to stop prefixing the "xs:" in the elements, which
> are
> parameters to method.
>
> What steps will reproduce the problem?
> 1. package require WS::Client
> 2. ::WS::Client::GetAndParseWsdl $URL
> 3. ::WS::Client::CreateStubs emsprov
> 4. ::emsprov::getDevice "1" [list "options" a ] "1">> Error at tclsh prom=
pt --
>
> org.apache.axis2.databinding.ADBException: Unexpected subelement
> transactionID
>
> What version of the product are you using? On what operating system?
> WebServices-1.1.2.zip
> tDOM-0.8.2
> tclsh8.5
> x86_64 x86_64 x86_64 GNU/Linux SUSE
>
> What is the expected output?
>
> <soapenv:Envelope xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-
> instance"
> xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema"
> xmlns:soapenv=3D"http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:urn=3D"urn:emsprov">
> =A0 =A0<soapenv:Header/>
> =A0 =A0<soapenv:Body>
> =A0 =A0 =A0 <urn:getDevice
> soapenv:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/">
> =A0 =A0 =A0 =A0 =A0<transactionID xsi:type=3D"xsd:string">1</transactionI=
D>
> =A0 =A0 =A0 =A0 =A0<deviceUID xsi:type=3D"xsd:string">1</deviceUID>
> =A0 =A0 =A0 =A0 =A0<options xsi:type=3D"urn:ArrayOfKeyValue">
> =A0 =A0 =A0 =A0 =A0 =A0 <!--Zero or more repetitions:-->
> =A0 =A0 =A0 =A0 =A0 =A0 <item xsi:type=3D"urn:KeyValue">
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<key xsi:type=3D"xsd:string">k1</key>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<value xsi:type=3D"xsd:string">v1</value>
> =A0 =A0 =A0 =A0 =A0 =A0 </item>
> =A0 =A0 =A0 =A0 =A0</options>
> =A0 =A0 =A0 </urn:getDevice>
> =A0 =A0</soapenv:Body>
> </soapenv:Envelope>
>
> <soapenv:Envelope
> xmlns:soapenv=3D"http://schemas.xmlsoap.org/soap/envelope/">
> =A0 =A0<soapenv:Body>
> =A0 =A0 =A0 <ns1:getDeviceResponse xmlns:ns1=3D"urn:emsprov">
> =A0 =A0 =A0 =A0 =A0<transactionID>1</transactionID>
> =A0 =A0 =A0 =A0 =A0<status>0</status>
> =A0 =A0 =A0 =A0 =A0<description/>
> =A0 =A0 =A0 =A0 =A0<deviceUID>1</deviceUID>
> =A0 =A0 =A0 =A0 =A0<developmentUID>1</developmentUID>
> =A0 =A0 =A0 =A0 =A0<deviceType>deviceType</deviceType>
> =A0 =A0 =A0 =A0 =A0<deviceModel>deviceModel</deviceModel>
> =A0 =A0 =A0 =A0 =A0<deviceManufacturer>deviceManufacturer</deviceManufact=
urer>
> =A0 =A0 =A0 =A0 =A0<deviceAttributes>
> =A0 =A0 =A0 =A0 =A0 =A0 <item>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<key>Key1</key>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<value>Value1</value>
> =A0 =A0 =A0 =A0 =A0 =A0 </item>
> =A0 =A0 =A0 =A0 =A0</deviceAttributes>
> =A0 =A0 =A0 </ns1:getDeviceResponse>
> =A0 =A0</soapenv:Body>
> </soapenv:Envelope>
>
> What do you see instead?
> <?xml version=3D'1.0' encoding=3D'utf-8'?>
> <SOAP-ENV:Envelope xmlns:SOAP-
> ENV=3D"http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:tns1=3D"urn:emsprov"
> xmlns:xs=3D"http://www.w3.org/2001/XMLSchema"
> xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance">
> =A0 <SOAP-ENV:Body>
> =A0 =A0 <tns1:getDevice SOAP-
> ENV:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/">
> =A0 =A0 =A0 <xs:transactionID xsi:type=3D"xs:string">1</xs:transactionID>
> =A0 =A0 =A0 <xs:deviceUID xsi:type=3D"xs:string">1</xs:deviceUID>
> =A0 =A0 =A0 <xs:options xsi:type=3D"xs:ArrayOfKeyValue" />
> =A0 =A0 </tns1:getDevice>
> =A0 </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
> <?xml version=3D'1.0' encoding=3D'utf-8'?>
> <soapenv:Envelope
> xmlns:soapenv=3D"http://schemas.xmlsoap.org/soap/envelope/">
> =A0 <soapenv:Body>
> =A0 =A0 <soapenv:Fault>
> =A0 =A0 =A0 <faultcode>soapenv:Server</faultcode>
> =A0 =A0 =A0 <faultstring>org.apache.axis2.databinding.ADBException:
> Unexpected
> subelement transactionID</faultstring>
> =A0 =A0 =A0 <detail />
> =A0 =A0 </soapenv:Fault>
> =A0 </soapenv:Body>
> </soapenv:Envelope>

This looks like a "server" error, as opposed to a "client" error. That
should mean that the request you sent was in a correct form, but maybe
the data you sent wasn't accepted by the server.

If you notice, your "options" element is empty. The example shows this
is valid, but maybe you need a value in there.

Is it possible to send a multi-depth document with WS::Client? My
guess is yes, since you send a dictionary, but an example would be
nice.

On Mar 25, 4:33=A0pm, "tom.rmadilo" <tom.rmad...@gmail.com> wrote:
> On Mar 25, 11:21=A0am, credit card fraud - citibank and spiceJet
>
>
>
>
>
> <msubbare...@gmail.com> wrote:
> > On Mar 2, 8:09=A0am, "Larry W. Virden" <lvir...@gmail.com> wrote:
>
> > > On Mar 1, 7:44=A0pm, "tom.rmadilo" <tom.rmad...@gmail.com> wrote:
>
> > > > A SOAP package that old is bound to be useless. Most web services h=
ave
> > > > moved from rpc/encoded (slow an proprietary) to document/literal
> > > > (faster and generic). And the entire conversation is encoded in a
> > > > "generic" WSDL file.
>
> > > Thanks for the feedback. I will have to check with the developers to
> > > see whether WS::Client is something in which they wish to investigate=
..
>
> > Hi, I need help on the tcl soap/webservices.
> > currently, trying with tclws and tclsoap.
> > But, tclws is constructing the elements with extr "xs:", so, server is
> > not understand the subelements.
> > Please advise with any clues.
>
> > URL:http://code.google.com/p/tclws/issues/detail?id=3D7
> > URL:http://code.google.com/p/tclws/issues/detail?id=3D8
>
> > Here are the details
> > Please provide any additional information below.
> > How to send the soap request - elements without "xs:" within method
> > element, as mentioned in the "What is expected output section".
> > My soap server (tomcat/aix2/wsld1.1), does not able to understand the
> > request,
> > because, element tags are prefixed with "xs:" under the method tag.
>
> > Please suggest, how to stop prefixing the "xs:" in the elements, which
> > are
> > parameters to method.
>
> > What steps will reproduce the problem?
> > 1. package require WS::Client
> > 2. ::WS::Client::GetAndParseWsdl $URL
> > 3. ::WS::Client::CreateStubs emsprov
> > 4. ::emsprov::getDevice "1" [list "options" a ] "1">> Error at tclsh pr=
ompt --
>
> > org.apache.axis2.databinding.ADBException: Unexpected subelement
> > transactionID
>
> > What version of the product are you using? On what operating system?
> > WebServices-1.1.2.zip
> > tDOM-0.8.2
> > tclsh8.5
> > x86_64 x86_64 x86_64 GNU/Linux SUSE
>
> > What is the expected output?
>
> > <soapenv:Envelope xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-
> > instance"
> > xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema"
> > xmlns:soapenv=3D"http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:urn=3D"urn:emsprov">
> > =A0 =A0<soapenv:Header/>
> > =A0 =A0<soapenv:Body>
> > =A0 =A0 =A0 <urn:getDevice
> > soapenv:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/">
> > =A0 =A0 =A0 =A0 =A0<transactionID xsi:type=3D"xsd:string">1</transactio=
nID>
> > =A0 =A0 =A0 =A0 =A0<deviceUID xsi:type=3D"xsd:string">1</deviceUID>
> > =A0 =A0 =A0 =A0 =A0<options xsi:type=3D"urn:ArrayOfKeyValue">
> > =A0 =A0 =A0 =A0 =A0 =A0 <!--Zero or more repetitions:-->
> > =A0 =A0 =A0 =A0 =A0 =A0 <item xsi:type=3D"urn:KeyValue">
> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<key xsi:type=3D"xsd:string">k1</key>
> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<value xsi:type=3D"xsd:string">v1</value=
>
> > =A0 =A0 =A0 =A0 =A0 =A0 </item>
> > =A0 =A0 =A0 =A0 =A0</options>
> > =A0 =A0 =A0 </urn:getDevice>
> > =A0 =A0</soapenv:Body>
> > </soapenv:Envelope>
>
> > <soapenv:Envelope
> > xmlns:soapenv=3D"http://schemas.xmlsoap.org/soap/envelope/">
> > =A0 =A0<soapenv:Body>
> > =A0 =A0 =A0 <ns1:getDeviceResponse xmlns:ns1=3D"urn:emsprov">
> > =A0 =A0 =A0 =A0 =A0<transactionID>1</transactionID>
> > =A0 =A0 =A0 =A0 =A0<status>0</status>
> > =A0 =A0 =A0 =A0 =A0<description/>
> > =A0 =A0 =A0 =A0 =A0<deviceUID>1</deviceUID>
> > =A0 =A0 =A0 =A0 =A0<developmentUID>1</developmentUID>
> > =A0 =A0 =A0 =A0 =A0<deviceType>deviceType</deviceType>
> > =A0 =A0 =A0 =A0 =A0<deviceModel>deviceModel</deviceModel>
> > =A0 =A0 =A0 =A0 =A0<deviceManufacturer>deviceManufacturer</deviceManufa=
cturer>
> > =A0 =A0 =A0 =A0 =A0<deviceAttributes>
> > =A0 =A0 =A0 =A0 =A0 =A0 <item>
> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<key>Key1</key>
> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<value>Value1</value>
> > =A0 =A0 =A0 =A0 =A0 =A0 </item>
> > =A0 =A0 =A0 =A0 =A0</deviceAttributes>
> > =A0 =A0 =A0 </ns1:getDeviceResponse>
> > =A0 =A0</soapenv:Body>
> > </soapenv:Envelope>
>
> > What do you see instead?
> > <?xml version=3D'1.0' encoding=3D'utf-8'?>
> > <SOAP-ENV:Envelope xmlns:SOAP-
> > ENV=3D"http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:tns1=3D"urn:emsprov"
> > xmlns:xs=3D"http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance">
> > =A0 <SOAP-ENV:Body>
> > =A0 =A0 <tns1:getDevice SOAP-
> > ENV:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/">
> > =A0 =A0 =A0 <xs:transactionID xsi:type=3D"xs:string">1</xs:transactionI=
D>
> > =A0 =A0 =A0 <xs:deviceUID xsi:type=3D"xs:string">1</xs:deviceUID>
> > =A0 =A0 =A0 <xs:options xsi:type=3D"xs:ArrayOfKeyValue" />
> > =A0 =A0 </tns1:getDevice>
> > =A0 </SOAP-ENV:Body>
> > </SOAP-ENV:Envelope>
>
> > <?xml version=3D'1.0' encoding=3D'utf-8'?>
> > <soapenv:Envelope
> > xmlns:soapenv=3D"http://schemas.xmlsoap.org/soap/envelope/">
> > =A0 <soapenv:Body>
> > =A0 =A0 <soapenv:Fault>
> > =A0 =A0 =A0 <faultcode>soapenv:Server</faultcode>
> > =A0 =A0 =A0 <faultstring>org.apache.axis2.databinding.ADBException:
> > Unexpected
> > subelement transactionID</faultstring>
> > =A0 =A0 =A0 <detail />
> > =A0 =A0 </soapenv:Fault>
> > =A0 </soapenv:Body>
> > </soapenv:Envelope>
>
> This looks like a "server" error, as opposed to a "client" error. That
> should mean that the request you sent was in a correct form, but maybe
> the data you sent wasn't accepted by the server.
>
> If you notice, your "options" element is empty. The example shows this
> is valid, but maybe you need a value in there.
>
> Is it possible to send a multi-depth document with WS::Client? My
> guess is yes, since you send a dictionary, but an example would be
> nice.- Hide quoted text -
>
> - Show quoted text -


Yes, thats one more challenge, I am facing on constructing the multi
dimensional data struct to send as part of the SOAP request.
Here is my web post on the same, I would be thankfull for any help
either of the posts.

http://code.google.com/p/tclws/issues/detail?id=3D8

On Mar 26, 8:52=A0am, credit card fraud - citibank and spiceJet
<msubbare...@gmail.com> wrote:
> On Mar 25, 4:33=A0pm, "tom.rmadilo" <tom.rmad...@gmail.com> wrote:

> > Is it possible to send a multi-depth document with WS::Client? My
> > guess is yes, since you send a dictionary, but an example would be
> > nice.- Hide quoted text -

>
> Yes, thats one more challenge, I am facing on constructing the multi
> dimensional data struct to send as part of the SOAP request.
> Here is my web post on the same, I would be thankfull for any help
> either of the posts.
>
> http://code.google.com/p/tclws/issues/detail?id=3D8

I work mainly on the server side, with my tWSDL/TWiST API. The main
problem, as usual, is that your service type is ancient...using rpc/
encoded. Check if WS::Client handles that one.

I have translated your service example into TWiST here:

http://junom.com/ws/emsprov/

You can test the service's one operation:

http://junom.com/ws/emsprov/?op=3DgetDevOperation&mode=3Ddisplay

This service is defined with a TWiST config file, in text form:

http://junom.com/ws/emsprov/index.txt

The testing page shows that you can create a deep xml document. In
fact, the service creates the document based upon your input and sends
it to the server and retrieves the resulting document.

The getDevice.options input is a list of lists: a {b c} {d e} f. A one
element list produces a nil value in xml.

The API actually generates procedures for creating the xml documents
given a tcl list of values (without the element names), so you could
use these generated API to create your client documents.

You can browse the generated code from any of the above links.

On Mar 26, 6:21=A0pm, "tom.rmadilo" <tom.rmad...@gmail.com> wrote:
> On Mar 26, 8:52=A0am, credit card fraud - citibank and spiceJet
>
> <msubbare...@gmail.com> wrote:
> > On Mar 25, 4:33=A0pm, "tom.rmadilo" <tom.rmad...@gmail.com> wrote:
> > > Is it possible to send a multi-depth document with WS::Client? My
> > > guess is yes, since you send a dictionary, but an example would be
> > > nice.- Hide quoted text -
>
> > Yes, thats one more challenge, I am facing on constructing the multi
> > dimensional data struct to send as part of the SOAP request.
> > Here is my web post on the same, I would be thankfull for any help
> > either of the posts.
>
> >http://code.google.com/p/tclws/issues/detail?id=3D8
>
> I work mainly on the server side, with my tWSDL/TWiST API. The main
> problem, as usual, is that your service type is ancient...using rpc/
> encoded. Check if WS::Client handles that one.
>
> I have translated your service example into TWiST here:
>
> http://junom.com/ws/emsprov/
>
> You can test the service's one operation:
>
> http://junom.com/ws/emsprov/?op=3DgetDevOperation&mode=3Ddisplay
>
> This service is defined with a TWiST config file, in text form:
>
> http://junom.com/ws/emsprov/index.txt
>
> The testing page shows that you can create a deep xml document. In
> fact, the service creates the document based upon your input and sends
> it to the server and retrieves the resulting document.
>
> The getDevice.options input is a list of lists: a {b c} {d e} f. A one
> element list produces a nil value in xml.
>
> The API actually generates procedures for creating the xml documents
> given a tcl list of values (without the element names), so you could
> use these generated API to create your client documents.
>
> You can browse the generated code from any of the above links.


Thanks for the co-operation. I will starting using tclsoap and tclws.
But, how to specify the encoding style/use "rpc/encoded" and/or
"document/literal" before initiating the soap request?

--
~ Subba

Subba Reddy wrote:
> On Mar 26, 6:21 pm, "tom.rmadilo" <tom.rmad...@gmail.com> wrote:
>> On Mar 26, 8:52 am, credit card fraud - citibank and spiceJet
>>
>> <msubbare...@gmail.com> wrote:
>>> On Mar 25, 4:33 pm, "tom.rmadilo" <tom.rmad...@gmail.com> wrote:
>>>> Is it possible to send a multi-depth document with WS::Client? My
>>>> guess is yes, since you send a dictionary, but an example would be
>>>> nice.- Hide quoted text -
>>> Yes, thats one more challenge, I am facing on constructing the multi
>>> dimensional data struct to send as part of the SOAP request.
>>> Here is my web post on the same, I would be thankfull for any help
>>> either of the posts.
>>> http://code.google.com/p/tclws/issues/detail?id=8
>> I work mainly on the server side, with my tWSDL/TWiST API. The main
>> problem, as usual, is that your service type is ancient...using rpc/
>> encoded. Check if WS::Client handles that one.
>>
>> I have translated your service example into TWiST here:
>>
>> http://junom.com/ws/emsprov/
>>
>> You can test the service's one operation:
>>
>> http://junom.com/ws/emsprov/?op=getDevOperation&mode=display
>>
>> This service is defined with a TWiST config file, in text form:
>>
>> http://junom.com/ws/emsprov/index.txt
>>
>> The testing page shows that you can create a deep xml document. In
>> fact, the service creates the document based upon your input and sends
>> it to the server and retrieves the resulting document.
>>
>> The getDevice.options input is a list of lists: a {b c} {d e} f. A one
>> element list produces a nil value in xml.
>>
>> The API actually generates procedures for creating the xml documents
>> given a tcl list of values (without the element names), so you could
>> use these generated API to create your client documents.
>>
>> You can browse the generated code from any of the above links.
> 
> 
> Thanks for the co-operation. I will starting using tclsoap and tclws.
> But, how to specify the encoding style/use "rpc/encoded" and/or
> "document/literal" before initiating the soap request?

The server tells you what it wants in the WSDL.

-- 
+------------------------------------------------------------------------+
| Gerald W. Lester                                                       |
|"The man who fights for his ideals is the man who is alive." - Cervantes|
+------------------------------------------------------------------------+

On Apr 2, 12:01=A0am, "Gerald W. Lester" <Gerald.Les...@cox.net> wrote:
> Subba Reddy wrote:
> > On Mar 26, 6:21 pm, "tom.rmadilo" <tom.rmad...@gmail.com> wrote:
> >> On Mar 26, 8:52 am, credit card fraud - citibank and spiceJet
>
> >> <msubbare...@gmail.com> wrote:
> >>> On Mar 25, 4:33 pm, "tom.rmadilo" <tom.rmad...@gmail.com> wrote:
> >>>> Is it possible to send a multi-depth document with WS::Client? My
> >>>> guess is yes, since you send a dictionary, but an example would be
> >>>> nice.- Hide quoted text -
> >>> Yes, thats one more challenge, I am facing on constructing the multi
> >>> dimensional data struct to send as part of the SOAP request.
> >>> Here is my web post on the same, I would be thankfull for any help
> >>> either of the posts.
> >>>http://code.google.com/p/tclws/issues/detail?id=3D8
> >> I work mainly on the server side, with my tWSDL/TWiST API. The main
> >> problem, as usual, is that your service type is ancient...using rpc/
> >> encoded. Check if WS::Client handles that one.
>
> >> I have translated your service example into TWiST here:
>
> >>http://junom.com/ws/emsprov/
>
> >> You can test the service's one operation:
>
> >>http://junom.com/ws/emsprov/?op=3DgetDevOperation&mode=3Ddisplay
>
> >> This service is defined with a TWiST config file, in text form:
>
> >>http://junom.com/ws/emsprov/index.txt
>
> >> The testing page shows that you can create a deep xml document. In
> >> fact, the service creates the document based upon your input and sends
> >> it to the server and retrieves the resulting document.
>
> >> The getDevice.options input is a list of lists: a {b c} {d e} f. A one
> >> element list produces a nil value in xml.
>
> >> The API actually generates procedures for creating the xml documents
> >> given a tcl list of values (without the element names), so you could
> >> use these generated API to create your client documents.
>
> >> You can browse the generated code from any of the above links.
>
> > Thanks for the co-operation. I will starting using tclsoap andtclws.
> > But, how to specify the encoding style/use "rpc/encoded" and/or
> > "document/literal" before initiating the soap request?
>
> The server tells you what it wants in the WSDL.
>
> --
> +------------------------------------------------------------------------=
+
> | Gerald W. Lester =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |
> |"The man who fights for his ideals is the man who is alive." - Cervantes=
|
> +------------------------------------------------------------------------=
+- Hide quoted text -
>
> - Show quoted text -

I agree. But, tclws consuming the server wsdl and giving the stubs.
After, that, when, I make call to server through tclws - stubs,
the generated soap request is not getting accepted by server.

So, the problem at tclws side, not able to generated the server
expected soap envlope.

And, so, we have started looking into tclsoap library usage. And this
is also, provides the machinisima to use the wsdl and construct method
signature.
tclsoap generated request is being accepted by server and getting
response.
And, compatible with server expcted - encode style/usage is rpc/
encoded.

And, our next would be xorb - xotcl soap.

Please advice with your opinions.

~ Subba

On Apr 2, 10:10=A0am, Subba Reddy <msubbare...@gmail.com> wrote:
> On Apr 2, 12:01=A0am, "Gerald W. Lester" <Gerald.Les...@cox.net> wrote:

> > The server tells you what it wants in the WSDL.

> I agree. But, tclws consuming the server wsdl and giving the stubs.
> After, that, when, I make call to server through tclws - stubs,
> the generated soap request is not getting accepted by server.
>
> So, the problem at tclws side, not able to generated the server
> expected soap envlope.

I have nothing to do with WS::Client, what you call tclws. But the
problem is the ancient server, not tclws.

Given a modern server which follows WS-I, you can support users who
don't understand the details of SOAP and web services in general. But
old, ancient services like the one you are interested in using require
that you get into the weeds. There is little chance of automatic
programming.

> And, so, we have started looking into tclsoap library usage. And this
> is also, provides the machinisima to use the wsdl and construct method
> signature.
> tclsoap generated request is being accepted by server and getting
> response.
> And, compatible with server expcted - encode style/usage is rpc/
> encoded.

So use that? When something works, why look for something else?

> And, our next would be xorb - xotcl soap.
>
> Please advice with your opinions.

Complain to whoever runs the web service. They have no excuse for not
keeping up with current standards, it is very easy for the server to
update. New clients have no reason to support old protocols.