Hello there,
I'm trying to diagnose why a XPL I wrote isn't working as expected. So I'm looking for a nifty way to show data (browser, console, logfile, that's all fine) from the pipeline. Would anybody happen to have a hint to to realize this?
Best, Robin -- 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 OW2 mailing lists service home page: http://www.ow2.org/wws |
you may use the file-serializer in conjunction with a converter that will store your xml content to a specified location. <p:processor name="oxf:xml-converter"><p:input name="config"><config><encoding>utf-8</encoding></config></p:input><p:input name="data" href="#my-document"/><p:output name="data" id="converted"/></p:processor><!-- Write the document to a file --><p:processor name="oxf:file-serializer"><p:input name="config"><config><directory>build/doc/reference</directory><file>single-file-doc.html</file><make-directories>true</make-directories><append>false</append></config></p:input><p:input name="data" href="#converted"/></p:processor>
Alexandru On Fri, Jan 29, 2010 at 14:43, Robin Diederen <[hidden email]> wrote:
-- 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 OW2 mailing lists service home page: http://www.ow2.org/wws |
In reply to this post by Robin Diederen
Hi Robin,
The method I favour is to monitor the logs in real time as the xpl is executed. You can configure each processor in a pipeline to print the xml passing through it to the standard orbeon log, with a debug attribute, like so: <p:processor name="oxf:identity"> <p:input name="config" href="#instance" debug="instance-input"/> <p:output name="data" ref="instance" debug="instance-output"/> </p:processor> Make sure that you have logging enabled as described here: http://wiki.orbeon.com/forms/doc/developer-guide/xforms-logging Exactly how you will montior the logs will depend upon your platform. Keep in mind that: If the processor does not execute, nothing will pass through it and nothing will print; Mal-formed XML will cause the processor to throw an exception with the debug attribute set. Hope that helps, Tom |
In reply to this post by Alexandru Ionita
Hello Alexandra, Thanks for the tip, this works like a
charm. Best, Robin Van:
Alexandru Ionita [mailto:[hidden email]] Hello Robin, you may use the file-serializer in conjunction with a
converter that will store your xml content to a specified location. <p:processor name="oxf:xml-converter"><p:input name="config"><config><encoding>utf-8</encoding></config></p:input><p:input name="data" href="#my-document"/><p:output name="data" id="converted"/></p:processor><!-- Write
the document to a file --><p:processor name="oxf:file-serializer"><p:input name="config"><config><directory>build/doc/reference</directory><file>single-file-doc.html</file><make-directories>true</make-directories><append>false</append></config></p:input><p:input name="data" href="#converted"/></p:processor> Alexandru On Fri, Jan 29, 2010 at 14:43, Robin Diederen <[hidden email]> wrote: Hello
there, I'm
trying to diagnose why a XPL I wrote isn't working as expected. So I'm looking
for a nifty way to show data (browser, console, logfile, that's all fine) from
the pipeline. Would anybody happen to have a hint to to realize this? Best,
Robin -- 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 OW2 mailing lists service home page: http://www.ow2.org/wws -- 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 OW2 mailing lists service home page: http://www.ow2.org/wws |
In reply to this post by Tom Grahame
Hi Tom,
Thanks for the tip, I'll give it a try. Best, Robin -----Oorspronkelijk bericht----- Van: Tom Grahame [mailto:[hidden email]] Verzonden: vrijdag 29 januari 2010 14:47 Aan: [hidden email] Onderwerp: [ops-users] Re: Viewing XPL / pipeline output Hi Robin, The method I favour is to monitor the logs in real time as the xpl is executed. You can configure each processor in a pipeline to print the xml passing through it to the standard orbeon log, with a debug attribute, like so: <p:processor name="oxf:identity"> <p:input name="config" href="#instance" debug="instance-input"/> <p:output name="data" ref="instance" debug="instance-output"/> </p:processor> Make sure that you have logging enabled as described here: http://wiki.orbeon.com/forms/doc/developer-guide/xforms-logging http://wiki.orbeon.com/forms/doc/developer-guide/xforms-logging Exactly how you will montior the logs will depend upon your platform. Keep in mind that: If the processor does not execute, nothing will pass through it and nothing will print; Mal-formed XML will cause the processor to throw an exception with the debug attribute set. Hope that helps, Tom -- View this message in context: http://n4.nabble.com/Viewing-XPL-pipeline-output-tp1415414p1415465.html Sent from the ObjectWeb OPS - Users mailing list archive at Nabble.com. -- 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 OW2 mailing lists service home page: http://www.ow2.org/wws |
Free forum by Nabble | Edit this page |