Colleagues, I am finally back to writing my OXF application and I am really excited. But my first attempt to consume a web service is stalled.
Is there a code snippet to simply dump the response I get as text? Why does the ca-traffic sample require 3 processors? Borrowing from your ca=-traffic example, the code below executes the webservice correctly, according to the SOAP monitor program. However, I get a single empty element (I think -- I just want to see the whole message). Thanks in advance for any clues. --Hank ============================================ Replying to a list? I'll get my copy there! Hank Ratzesberger http://crustal.ucsb.edu/ | http://neesgrid.org/ Institute for Crustal Studies University of California, Santa Barbara ============================================ <p:param type="input" name="instance"/> <p:param type="output" name="data"/> <p:processor uri="oxf/processor/xslt"> <p:input name="data" href="#instance"/> <p:input name="config"> <xsl:stylesheet version="1.0"> <xsl:template match="/"> <delegation:execute service="standardPersonService" operation="getAllPersons"/> </xsl:template> </xsl:stylesheet> </p:input> <p:output name="data" id="call"/> </p:processor> <p:processor uri="oxf/processor/delegation"> <p:input name="interface"> <config> <service id="standardPersonService" type="webservice" endpoint="http://www.nacse.org/neesSiteSpecs/services/StandardPersonService";> <operation nsuri="http://service.ssdb.nacse.org"; name="getAllPersons" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> </service> </config> </p:input> <p:input name="data"><dummy/></p:input> <p:input name="call" href="#call"/> <p:output name="data" id="persons"/> </p:processor> <p:processor uri="oxf/processor/identity"> <p:input name="data" href="aggregate('root', #persons)"/> <p:output name="data" ref="data"/> </p:processor> _______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
