"Klotz, Leigh" wrote:
>
>...
>
> Paul Prescod points out that the direct mapping of document('soap://...') to
> an invication of a SOAP-based web service may not be the best mechanism for
> hooking the SOAP and the XSLT together, since that puts invocations of the
> web service under control of the XSLT processing model rather than putting
> the results of the SOAP invocation as documents given to XSLT. I believe
> what is needed are specific input-output transformation operations that are
> orchestration steps producing result documents. These result documents
> could then be named and referred to by XSLT "document('result1')"
> expression, or perhaps by a simple XPath path expression if the results are
> incorporated back into the document itself.
I guess you realize that if you use HTTP rather than SOAP then you can
skip this step and avoid the possible problems caused by downloading
documents (e.g. problems comparing identity or URI bases).
Paul Prescod
