Hi,
First note that what OPS provides to implement a Web service is very low level. Basically, you access the XML document sent by the client with the Request generator, create the XML document you want to reply with, and send it back with the XML Serializer.
This is actually just what I am looking for since I am really only adding a web service interface onto the application. The average response will be just to repackage the SOAP body via an xslt and then call an existing pipeline and send the response back.
If you want the same path to serve both the WSDL and implement the service, map that path (/endpoint) to an XPL, and in the XPL based on the parameters (that you get with the request generator) either execute the service or send the WSDL file.
That's pretty much what I had suspected.
I note that in the documentation on the web page for the request generator, the /request/body element mentioned in the web service integration is not listed in the "full" list for /request.
Cheers,
Matthew
------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ orbeon-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/orbeon-user
