On Mon, Feb 07, 2005 at 10:47:56AM -0800, Alessandro Vernet wrote: > See the XUpdate in the attached test case. If I understand what you are > trying to do correctly, that should do the trick. It assumes that in the > "target document" you have the same structure as in the "source document".
OK, thanks, I will give it a try, but in the meantime I pass the full (changed) instance back somewhere in the action's data and use this to replace the full instance with XUpdate. This brought me to another idea: wouldn't it be handy to have the possibility to have an optional instance output parameter for the action pipelines (like also done with the model pipelines), that (*if* given back) is used i.s.o. the original instance from then on (after the action, staring with the <result>'s XUpdate), in case the matching <result> has no page attribute? This would the action pipeline give full capabilities of changing the instance without using the less powerful XUpdate code (compared to XSLT etc.). I guess this is pretty trivial to implement. What do you think? -- -- Jos Vos <[EMAIL PROTECTED]> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ orbeon-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/orbeon-user
