Your report is interesting.
One important thing to note: SOAP calls are not in any way guaranteed to
be idempotent. Because XSLT is a declarative, not procedural language,
you do not necessarily know how many times your XSLT will call the
method. If the method has side effects then depending on the engine you
use you may find that the methods are called in different orders or even
different numbers of times. With HTTP you know that anything that can be
GOT is intended by the HTTP specification to have no side effects. If
there ARE side effects that is a bug in the server, not in either your
XSLT transformation or your XSLT engine. So in general I do not think
that this model is really a safe way to deal with SOAP services.
Another thing is that many SOAP advocates say that most real-world SOAP
services will NOT use the SOAP RPC conventions. This means that your URL
construct will not work with them.
Paul Prescod
