Matthew,
There is no good solution to this problem right now. The value of the page attribute for now has to be static.
But if you were not copying over data from the initial page to the Type1, etc. pages, you could go to a generic page that would generate dynamically the XForms model. The only problem with this is how to decide which form to generate. We should probably think about how to address that kind of scenario better.
-Erik
Matthew J. Graham wrote:
I have the following in my page-flow.xml:
<action when="/form/action = 'edit'" action="publish/find-resource.xpl">
This returns:
<result> <resourceType> <document> </result>
resourceType can presently have 10 values but this will expand and each resourceType has a different XForm to it so at the moment I have:
<result page="Type1" when "/result/resourceType = 'Type1'"> <xu:update select="/form/document"> <xu:copy-of select="document('oxf:action')/result/document/*"/> </xu:update> </result>
and similarly for each possible value of resourceType. This seems needless repetition, however, and I was wondering how I could just do something like to handle all possibilities:
<result page="[value of /result/resourceType]"> <xu:update select="/form/document"> <xu:copy-of select="document('oxf:action')/result/document/*"/> </xu:update> </result>
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ orbeon-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/orbeon-user
