Hi I'm confused with situation when not well-formed xml document is returned by oxf:delegation processor calling web-service. As I've found the output for this processor consists of soap operation output content. For instance I have following SOAP msg in reply: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header /> <soapenv:Body> <response xmlns="http://www.intalio.com/bpms/workflow/ib4p_20051115"> <taskMetaData> <nextTaskId>e14ef3769ae36e8b:3cfb57c6:10ea339c627:-7fd8192.168.0.163589826</nextTaskId> <nextTaskURL>/ChainedExecution/Payment.xform</nextTaskURL> </taskMetaData> <status> OK </status> </response> </soapenv:Body> </soapenv:Envelope> The content of <response> consists of two elements. It is exactly what oxf:delegation processor gives me as output. And, you guess it, - I cannot use it further in xpl as it is not well-formed xml, it does not have exactly one root element. I'm using the OPS3.1 and only in the process of migration to 3.5. Is there simple solution, or the answer is only migrate to 3.5M. Is it solved in 3.5M? Thank you, Oleg -- mailto:[hidden email] -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
My beloved Oleg,
the answer is to use attribute "select" for element "operation" in the config input of "oxf:delegation" processor. In your particular case when you want to have a whole "response" element as output of processor it would look like: <p:processor name="oxf:delegation"> <p:input name="interface"> <config> <service ...> <operation ... select="/*:Envelope/*:Body/text() | /*:Envelope/*:Body/*"/> </service> </config> </p:input> <p:input name="call" href="#..."/> <p:output name="data" id="..."/> </p:processor> I've found that in sources, so - replying to myself. It could be of use to others. I'm bad lister actually. Regards anyway to the Orbeon team: I'm excited with product. Oleg -- mailto:[hidden email] Wednesday, November 1, 2006, 2:52:01 PM, Oleg: > Hi > I'm confused with situation when not well-formed xml document is returned by oxf:delegation > processor calling web-service. As I've found the output for this processor consists of soap > operation output content. For instance I have following SOAP msg in reply: > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> > <soapenv:Header /> > <soapenv:Body> > <response xmlns="http://www.intalio.com/bpms/workflow/ib4p_20051115"> > <taskMetaData> > > <nextTaskId>e14ef3769ae36e8b:3cfb57c6:10ea339c627:-7fd8192.168.0.163589826</nextTaskId> > <nextTaskURL>/ChainedExecution/Payment.xform</nextTaskURL> > </taskMetaData> > <status> > OK > </status> > </response> > </soapenv:Body> > </soapenv:Envelope> > The content of <response> consists of two elements. It is exactly what oxf:delegation processor > gives me as output. And, you guess it, - I cannot use it further in xpl as it is not well-formed > xml, it does not have exactly one root element. > I'm using the OPS3.1 and only in the process of migration to 3.5. Is there simple solution, or the > answer is only migrate to 3.5M. Is it solved in 3.5M? > Thank you, > Oleg -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Administrator
|
> I've found that in sources, so - replying to myself. It could be of use to others.
> I'm bad lister actually. > > Regards anyway to the Orbeon team: I'm excited with product. Thanks :-) -Erik -- Orbeon - XForms Everywhere: http://www.orbeon.com/blog/ -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Free forum by Nabble | Edit this page |