Hello, one way to deal with this issue is to have your xinclude url
refer another pipeline defined in your sitemap. For example if I had the
following fragment in my sitemap:
sitemap.xmap:
...
<match pattern="/components/*.xsp">
<generate type="xsp" src="/components/{1}.xsp"/>
<serialize type="xml"/>
</match>
...
Then, my xsp file had the following xinclude:
...
<xi:include href="cocoon://components/somefile.xsp"/>
...
This would only work if your xsp files are independent of each other.
Another approach would be to use XSP logicsheets instead of xinclude. I am
still new to Cocoon2 and learning as I go along, so take my advice with a
grain of salt! Perhaps others on this list have can offer a better
solution.
Regards,
--mike
On Wed, 5 Sep 2001, Andrew Answer wrote:
> Hello cocoon-users,
>
> how to do xsp xincluding? Because xinclude is a transformer, i can't
> push it before xsp generator in sitemap pipeline...
> But i can't also do xsp processing later because of xsp is a
> generator and i must place it first in pipeline...
> What i can do?
>
> --
> Best regards,
> Andrew mailto:[EMAIL PROTECTED]
>
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
