You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@cocoon.apache.org by defe <de...@free.fr> on 2004/08/08 21:33:24 UTC

flowscript conception problem

hi,

is it possible to use flowscripts for generating internal xml parts.

<map:aggregate element="page">
    <map:part src="cocoon;//pathto/foo.xml"/>
     <map:part .../>
     ...
</map:aggregate>

elsewhere,

<map:pipeline internal-only="true">
    <map:match pattern="foo.xml">
        <map:call function="foo"/>
    </map:match>

    <map:match pattern="foo.jx">
        <map:generate type="jx" ../>
            ...
        <map:serialize type="xml"/>
    </map:match>
</map:pipeline>

thanks.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: flowscript conception problem

Posted by Mark Lundquist <ml...@wrinkledog.com>.

On Aug 8, 2004, at 12:33 PM, defe wrote:

> hi,
>
> is it possible to use flowscripts for generating internal xml parts.
>
> <map:aggregate element="page">
>    <map:part src="cocoon;//pathto/foo.xml"/>
>     <map:part .../>
>     ...
> </map:aggregate>
>
> elsewhere,
>
> <map:pipeline internal-only="true">
>    <map:match pattern="foo.xml">
>        <map:call function="foo"/>
>    </map:match>
>
>    <map:match pattern="foo.jx">
>        <map:generate type="jx" ../>
>            ...
>        <map:serialize type="xml"/>
>    </map:match>
> </map:pipeline>

Sure.  No problem.  Except in your example, the matcher won't match the 
pattern for the src in your aggregate part... but you have the right 
idea.

~ml


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org