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: "Roger L. Costello" <costello at mitre dot org>
- To: xsl-list at lists dot mulberrytech dot com
- Cc: paul at prescod dot net
- Date: Mon, 27 May 2002 09:13:17 -0400
- Subject: Re: [xsl] Does saxon:output do an HTTP POST? (Using XSLT as a Web Services bridge)
- Organization: The MITRE Corporation
- References: <003801c1fb8b$8f054e00$0400a8c0@fcmobilexpp> <3CF14061.3D3BBA93@mitre.org>
- Reply-to: xsl-list at lists dot mulberrytech dot com
"Roger L. Costello" wrote:
>
> 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...
I just did a test. I created a Web service on my local machine which
consumes XML. I created a stylesheet that did SAXON:output to that
service. When I ran it SAXON gave me an error message,
"Failed to create output file http://localhost:8080/servlet/sample"
xalan also bombed. It gave me an error:
java.lang.reflect.InvocationTargetException
I am very disappointed. This means that it's possible to input from a
Web service (using document()), but it is not possible to output to a
Web service. In my mind, I see this as a major inconsistency between
the input capability and the output capability. Does anyone know of
what is planned for XSLT 2.0? I believe that there will be a built-in
output element, correct? Will it be able to do an HTTP POST to any
consumer of XML (such as a Web service)? /Roger
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list