This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Does saxon:output do an HTTP POST? (Using XSLT as a Web Services bridge)
- From: "Thomas B. Passin" <tpassin at mitretek dot org>
- To: <xsl-list at lists dot mulberrytech dot com>
- Date: Tue, 28 May 2002 09:59:15 -0400
- Subject: Re: [xsl] Does saxon:output do an HTTP POST? (Using XSLT as a Web Services bridge)
- References: <7D365016E308F44EACB6ADB51CBD690404ED8E@shbex01.hosting.innerhost.com>
- Reply-to: xsl-list at lists dot mulberrytech dot com
[Paul Brown]
> From: Francis Norton [mailto:francis@redrice.com]
> So let's hope we get an output option which is compatible
> with those Web Services which require a POST rather than a
> mere GET.
I know that this isn't necessarily the desired solution, but one can create
a GET/POST proxy servlet in a jiffy -- and the problem of creating the body
of a POST request out of a GET form submission boils down to generating
output for a set of name/value pairs.
[Tom P]
Whether you can do it depends on what you mean by "Web Service". It's one
thing to POST some (name,variable) pairs. It's another to construct a SOAP
envelope + payload and to respond to possible SOAP error messages.
Cheers,
Tom P
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list