Hi Leszek:
Hmm.. Try better xinclude. That way you can store this unique application
stuff in a separated xml file. And access it using xpath.
I prefer xinclude because then we can share resource between application
and we know nothing will be broken.
Examples of that you can find in the cocoon samples.
Best Regards,
Antonio Gallardo
Leszek Gawron dijo:
> Is there a way to acces input modules nicely from xslt stylesheet? Right
> now I
> am doing something like:
>
> <map:transform src="cocoon://{global:baseURL}/stylesheets/site2html.xsl">
> <map:parameter name="baseURL"
> value="/{global:baseURL}"/>
> <map:parameter name="appTitle"
> value="{global:appTitle}"/>
> </map:transfrom>
>
> this is all fine if one has only one sitemap (one can use resources to
> work
> with duplicated code) but I have a web application that each app menu
> option
> (application section) has it's own sitemap.
>
> The number of parameters passed to stylesheets gets bigger and bigger with
> time which makes the code harder to read and maintain.
> lg
>
>
> --
> __
> | / \ | Leszek Gawron // \\
> \_\\ //_/ [EMAIL PROTECTED] _\\()//_
> .'/()\'. Phone: +48(501)720812 / // \\ \
> \\ // recursive: adj; see recursive | \__/ |
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
