As quoted from Upayavira <[EMAIL PROTECTED]>:
> Another way you can do it is read your original content from disc, then transform it 
> into something like:
> <xml>
>   <source:write>
>     <content>Blah</content>
>   </source:write>
>   <content>Blah</content>
> </xml>
> This way you repeat your content twice, once to go into the SWT, and once to go on 
> to the output. Your following transformer then just strips out any nodes in the SWT 
> namespace.
> Make sense?
> Can you explain a little more _why_ you want to be writing to disk? That'll help me 
> understand how best you can achieve your requirements.

The thing is I generate a stylesheet in B which is used in A (and in other

<match pattern="B">
  <map:generate src="resources/{filename}.xml"/>
  <map:transform src="styles/Meta_output.xsl"/>
  <map:serialize type="xml"/>

Note that the output of B is a stylesheet (say output.xsl).

Then the first thing that comes to mind is using the Cocoon protocol to read
this output.xsl as the src of the transformer in A:

<match pattern="A">
  <map:generate src="resources/bla.xml"/>
  <map:transform src="cocoon:/B"/>
  <map:serialize type="html"/>
But unfortunately this does not work. (I have posted messages on this matter a
few days ago). The output of A is not what it should be at all. 

So I thought a workaround is to write the output.xsl to file and then read it in
A. But then I had the issue of dependencies....

I hope i have been clear enough. By the way have you ever tried to use cocoon:/
as the src of a Transformer?


> Regards, Upayavira
> <map:match ...>
>   <map:generate src="original source">
>   <map:transform src="make_
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- Ali Mesbah, West Consulting B.V.,, +31 15 2191600

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to