Erik,
Thanks for correcting my assumption.
From now on, I'll think of the 'id' attribute in <output> elements, and the 'name' attribute in <input> elements, as the 'output-doc-id', and 'input-doc-id' attributes, respectively.
Bill.
Bill,
"session" and "instance" refer to either processor outputs defined with:
id="session" id="instance"
or to pipeline inputs defined by:
<p:param type="input" name="session"/> <p:param type="input" name="instance"/>
As you can see, there is nothing implicit here. Also, those ids are not like the HTML id attribute, which can be put on any element. Pipelines are not like an HTML or XHTML DOM. So when you have something like "#session", you are referring to an entire XML document produced by a processor or passed to a pipeline, not just to an element that happens to have the specified id.
So:
1. In the file where you are looking at the xpointer expressions, you should see both "session" and "instance" declared either as processor outputs or pipeline inputs.
2. You will see that the "session" document is generated by a Session generator (should now be a Scope generator). The "instance" document is generated automatically by the XForms engine and passed to action, model, view and epilogue pipelines that declare an "instance" input. You do have access to the request and application context by using the Scope generator and serializer:
http://www.orbeon.com/ois/doc/home-changes#d95540e1333
-Erik
Bill Winspur wrote:
In a fragment of the examples code for accessing the session (add.xpl):
< p : input name ="data" href ="aggregate('cart', #session#xpointer(/cart/item), aggregate('item', #instance#xpointer(string(/form/text))))" />
there are two local references '#session' and '#instance', where 'session' and 'instance' are id's according to the pipeline href expression syntax.
Assuming that id values are those created by id=value attribute expressions on elements, the expression
#instance#xpointer(string(/form/text))))
probably means dereference xpointer(string(/form/text)))) starting at the node identified by 'instance'
Questions
---------
1. Are 'session' and 'instance', id's that are created by the oxf infrastructure rather than by attributes on xml that an app developer writes?
2. Are there any other such infrastructure ids useful to app developers ('request' and 'application' come to mind) ?
-------------------------------------------------------
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
-- 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
