As described on the orbeon blog
, there is a way to see the live content of the xforms instances.
<widget:xforms-instance-inspector xmlns:widget="http://orbeon.org/oxf/xml/widget"/>
This will now display something like this on top of the rendered xforms.
In the log4j.properties file, be sure you have not commented out the DebugProcessor logger:
log4j.category.org.orbeon.oxf.processor.DebugProcessor=INFO
In any xpl code, you can now add a debug tag to any variables, like the following:
<p:input name="xpl-input" href="#data" debug="mydata"/>
that will show up in the logs, with its current content.
This is also useful to see what data is sent from the form manager to the different tempo services.
From within the xFormsManager webapp, you can use the following command
jar xvf WEB-INF/lib/orbeon-resources-public-*.jar
to expand the public resources of orbeon.
Now you can see the code content, and work more efficiently with Orbeon javascript files.
We change the default configuration file a bit for orbeon, so the files should be expanded in the workflow folder.
Most of the files expanded are found in the ops folder.
If you want to see the javascripts used, notably xforms.js, be sure to make the following change in WEB-INF/workflow/config/properties.xml
from:
<property as="xs:boolean" name="oxf.xforms.minimal-resources" value="true"/>
to
<property as="xs:boolean" name="oxf.xforms.minimal-resources" value="false"/>
