It should not be that difficult to create a template for each <xa:*/>.
What exactly is the update? Moving the nodes from action.xml into the sitemap? You only must no which has higher priority.
If you need help, don't hesitate to ask - maybe offlist, because it's a bit off topic.
Joerg
Scott Warren wrote:
I understand where you are coming from. I am looking at using XSLT to
transform the 'action.xml' file into a stylesheet that then applied to
another document will 'merge' the two. The example I have is using a
sitemap (for example) and an 'action.xml' file of -------------------
<xa:action xmlns:xa="http://ocom.com.au/xmlaction/1.0"
xmlns:map="http://apache.org/cocoon/sitemap/1.0">
<!-- Insert a new Action -->
<xa:insert where="map:sitemap/map:components/map:actions">
<map:action name="BindBean"
src="com.ocom.framework.cocoon.acting.BindBeanAction" />
</xa:insert> <xa:replace where="map:sitemap/map:components/map:generators"> <map:generators>NONE THEY ARE ALL GONE</map:generators> </xa:replace> <!-- Delete an action where @Name="BindBean" --> <xa:delete where="map:sitemap/map:components/map:actions/map:[EMAIL PROTECTED]'DeleteMe ']" /> <xa:update where="map:sitemap/map:component/map:transformers/map:[EMAIL PROTECTED] 'xinclude']" > <map:transformer src="GONE" /> </xa:update> </xa:action> ------------------------ insert/replace/delete are easy and I have implemented them using XSLT but update is really a merge and this it seems is not easy with XSLT.
Regards
Scott Warren
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
