My understanding of access to the view, xform and model documents of a page, is summarized by the following, still questionable, assertions
1. The xform document is strongly oriented to its presentation role, (corresponding to swing models in the java gui architecture).
2. The page's model document is closely related to the (persistent) source
of the data retrieved for display (corresponding to the JDBC Result object,
in java's database access architecture).
3. In XSLT stylesheet processing of an xsl view document,
a. the 'model' document is mapped as the xslt source document and is
accessible via xpath in the select= attribute on various xsl elements. b. The 'xforms' document IS NOT available to XSLT, and can NOT be
used to control what is generated by XSLT.4. In Processing of an xhtml view document (provided, or xsl-generated):
c. the 'xforms' document content is accessible using xpath in an <xform:output>
element.
d. The 'model' document IS NOT available for presentation by xhtml views.
5. Because of b and d, above the view can not move data between the model and the
xforms docs, and such data manipulation would not be consistent with the MVC
pattern in any case.
6. In a pipeline that provides the model document, the page's xforms document is
available as the only input to the pipeline.
e. The instance is defined in the pipeline by:
<p:param name="instance" type="input"/>
where 'instance' is a pre-defined identifier for the xforms document.
f. xpointer references to the instance take the form
"document('oxf:instance')/some-path".
g. The model-producing pipeline can thus move data between the model (which it
creates) and the page's xforms document, using xupdate or xslt.
7. In an <action> of a <page>:
h. The document produced by pipeline 'some.xpl' on <action ... action="some.xpl">
is accessible in xpointer references of the form:
"document('oxf:action')some-path"
i. Within the <result> element of an action:
i) The originating page's xforms document is availabe
via xpath expressions of the form "document('oxf:instance')/*".ii) The result page's xforms document is available via xpath expressions
of the form "/*"
Thus <xupdate:update> elements within a <result> can be used to transfer data
from the originating xform to the result xform.
j. The model documents of the originating and result pages are NOT accessible
within an action.
Questions
---------
1. Are my assertions of what can NOT be done (mostly things I have not been able to do so far) correct?
The page's 'xforms' document IS NOT available to an xsl stylesheet view.
The page's 'model' document IS NOT available for presentation by an xhtml view.
The 'model' documents of the originating and result pages ARE NOT
accessible within an <action>.
2. Where can I find docuumentation of the OXF document() function, and its arguments?
3. Assuming that 'oxf:instance' and 'oxf:action' are uri's pre-defined to a
oxf-specific implementation of document(), are there any other such uri's?
5. For debugging purposes, is there a way to display the structure of the instance
document from xhtml, like the following xsl code does for the structure of the model
document?
f:xml-source>
<xsl:copy-of select="/*"/>
</f:xml-source>
-- Bill Winspur Manager, Wynnon Systems Inc Mobile: 403-519-5889
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ orbeon-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/orbeon-user
