×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Working on a project involving the use of RXS to consume a suite of SOAP
web services. SOAP web services with lots and lots of parameters (the
RXS templates for them run over 100 lines each). It's a project I've
worked on before; this time, I'm having to port the calls from one
server to another, with different server software, and (near as I can
tell) minor changes in the parameter tags (mostly capitalization changes).
It occurs to me that this would go a lot easier if I actually had an
adequate understanding of the syntax and low-level sematics of SOAP. For
example, one of the most puzzling things I see is that on the nulled-out
parameters in the RXS templates I have, it looks like each invocation of
nil is in its own namespace, e.g.,:
<ns1:foo xmlns:ns2="http://www.w3.org/2001/XMLSchema-instance"; ns2:nil="true"/>
<ns1:bar>.:bar:.</ns1:bar>
<ns1:baz xmlns:ns4="http://www.w3.org/2001/XMLSchema-instance"; ns4:nil="true"/>
(the names have been changed, to protect the innocent).
I'm hoping that the more I know about SOAP, the less it's going to leave
me with a bad taste in my mouth, craving some REST.
Can somebody recommend a reference and/or tutorial that will make all
this a bit more comprehensible to me?
--
JHHL
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
