This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Does saxon:output do an HTTP POST? (Using XSLT as a Web Services bridge)
- From: "Roger L. Costello" <costello at mitre dot org>
- To: xsl-list at lists dot mulberrytech dot com, costello at mitre dot org
- Cc: paul at prescod dot net
- Date: Sun, 26 May 2002 16:06:57 -0400
- Subject: [xsl] Does saxon:output do an HTTP POST? (Using XSLT as a Web Services bridge)
- Organization: The MITRE Corporation
- References: <003801c1fb8b$8f054e00$0400a8c0@fcmobilexpp>
- Reply-to: xsl-list at lists dot mulberrytech dot com
Several weeks ago I discovered (with help from folks here) that the
document() function could be used to access dynamically generated XML
data (such as from a Web service) as well as static XML data. Most
cool!
Thus, the document() function may be used for inputting Web service
data. Now, I would like to consider using XSLT to output to a Web
service. SAXON and XALAN both have an extension element for outputting
to other files. Suppose that I have a Web service which consumes XML.
That is, you send an XML document as the payload of an HTTP POST. Can
the SAXON:output element be used to send XML data to the Web service?
In other words, does the SAXON:output element do an HTTP POST? If so,
we can use XSLT as a bridge between Web services:
----------------- ----------------
| | | |
| Web Service 1 | | Web Service 2 |
| | | |
----------------- -----------------
| ^
| |
| ---------------- |
| | | |
---------------->| XSLT |------------
| |
----------------
Now that would be ultra cool! /Roger
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list