Prev: 748300 Up to date Net and Tech news, knowledge, empowerment 01
Next: launch default editor for windows
From: Larry W. Virden on 26 Feb 2010 07:23
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.
From: tom.rmadilo on 1 Mar 2010 19:44
On Feb 26, 4:23 am, "Larry W. Virden" <lvir...(a)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.  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?

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.
From: yahalom on 2 Mar 2010 01:52
On Mar 2, 2:44 am, "tom.rmadilo" <tom.rmad...(a)gmail.com> wrote:
> On Feb 26, 4:23 am, "Larry W. Virden" <lvir...(a)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.  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?
>
> 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/e8524fd631f3f52f/381851e732f21010?lnk=gst&q=yahalom#381851e732f21010
From: Larry W. Virden on 2 Mar 2010 07:09
On Mar 1, 7:44 pm, "tom.rmadilo" <tom.rmad...(a)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.
From: credit card fraud - citibank and spiceJet on 25 Mar 2010 14:21
On Mar 2, 8:09 am, "Larry W. Virden" <lvir...(a)gmail.com> wrote:
> On Mar 1, 7:44 pm, "tom.rmadilo" <tom.rmad...(a)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=7
URL: http://code.google.com/p/tclws/issues/detail?id=8

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


<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<ns1:getDeviceResponse xmlns:ns1="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='1.0' encoding='utf-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-
ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:tns1="urn:emsprov"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<tns1:getDevice SOAP-
ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<xs:transactionID xsi:type="xs:string">1</xs:transactionID>
<xs:deviceUID xsi:type="xs:string">1</xs:deviceUID>
<xs:options xsi:type="xs:ArrayOfKeyValue" />
</tns1:getDevice>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

<?xml version='1.0' encoding='utf-8'?>
<soapenv:Envelope
xmlns:soapenv="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>
 |  Next  |  Last
Pages: 1 2 3
Prev: 748300 Up to date Net and Tech news, knowledge, empowerment 01
Next: launch default editor for windows