Prev: 748300 Up to date Net and Tech news, knowledge, empowerment 01
Next: launch default editor for windows
From: Subba Reddy on 2 Apr 2010 13:10
On Apr 2, 12:01 am, "Gerald W. Lester" <Gerald.Les...(a)cox.net> wrote:
> Subba Reddy wrote:
> > On Mar 26, 6:21 pm, "tom.rmadilo" <tom.rmad...(a)gmail.com> wrote:
> >> On Mar 26, 8:52 am, credit card fraud - citibank and spiceJet
>
> >> <msubbare...(a)gmail.com> wrote:
> >>> On Mar 25, 4:33 pm, "tom.rmadilo" <tom.rmad...(a)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 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                                                       |
> |"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

From: tom.rmadilo on 2 Apr 2010 15:46
On Apr 2, 10:10 am, Subba Reddy <msubbare...(a)gmail.com> wrote:
> On Apr 2, 12:01 am, "Gerald W. Lester" <Gerald.Les...(a)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.
First  |  Prev  | 
Pages: 1 2 3
Prev: 748300 Up to date Net and Tech news, knowledge, empowerment 01
Next: launch default editor for windows