[EMAIL PROTECTED] wrote:
Barzilai. Clam down!
It sounds like you need a REST :-)
Jeff
Heheh, no kidding. Except it's too late to change the whole project now.
Soap seemed new and exciting when I started... now it's a burden.
What I may do in the next version of the project is to extend the specs
to accept old and heavyweight soap, or a lighter approach.
BarZ
----- Original Message -----
From: "Barzilai Spinak" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, July 25, 2005 7:19 PM
Subject: I'm fed up with SOAP
<RANT>
I've been using Soap web services for about 2 years. It took my many
weeks of learning and fighting with Axis. Then I found out that three
quarters of the Soap specification was being "deprecated" or at least
falling out of favour, and now we should be using something called
document/literal. It took me a few more to find out what it *really* was
and how it related to "wrapped" mode (are they the same? are they
different? how so?). Then I came to the conclusion that I'd better
write my WSDL by hand, where, again, 3/4 of it is a pointless leftover
of an overengineered specification for the stuff that fell out of
favour. So, now I have a "wrapped" web service where all I want to do is
return XML documents and the web service response to my XXX operation
has this structure:
soapenv:Envelope
soapenv:Body
XXXResponse
XXXReturn
XXXResult
myActualXML
So, there, *FIVE* levels of useless elements (response, return and
result!!! give me a break!). Now I was considering that I really needed
a wrapping element for some of my responses but I'm resisting the idea
of yet another level.
Well, I know all this ranting is useless but I just wanted to share some
of my frustrations with the list :-)
Thanks for hearing me hehehe
</RANT>
BarZ
Internet Banda Ancha Todo el Dia por $u 490 por mes
Sin gastos adicionales - Sin ocupar su telefono
Y los primeros 4 meses 50% de descuento!
______________________________________________________
http://www.internet.com.uy - En Uruguay somos internet
