You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Vadim Gritsenko <va...@verizon.net> on 2002/05/01 06:28:12 UTC

RE: Including generated content

> From: Avi Kivity [mailto:avi@argo.co.il]
> 
> I'd like to include content generated by on XSP in another. Looks like
I
> have three options:
> 
> 1. Use <map:aggregate/> - I don't want to do that as it doesn't allow
me
> control of where to place content (I'd like to place one document
inside
> another, not alongside).

Yes, there is not. You could use XSLT to move things around.


> 2. The xinclude/cinclude transformers - two problems: they don't work
> with absolute URLs (eg cocoon://mydoc.xsp; I patched this) and they

IIRC, for xinclude one must use <ns:xinclude base="protocol:/path/"
href="file"/> or something like this.


> don't understand the cocoon: protocol (anybody know how to work around
> this?)

Don't know how could you miss this one:

http://cvs.apache.org/viewcvs.cgi/xml-cocoon2/src/webapp/docs/samples/xs
p/aggregate.xsp?rev=1.4&content-type=text/vnd.viewcvs-markup

It's working from the day one.

Vadim
 
> 3. Use <util:include-uri/> from the util logicsheet. This is limited
to
> one XSP including some other content, but is good enough for me except
> that it doesn't understand cocoon: either.
> 
> Any pointers?
>
> Thanks,
> Avi
> 
> 
> --
> This space for rent.
 


---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>


Re: Including generated content

Posted by Avi Kivity <av...@argo.co.il>.
Vadim Gritsenko was heard to say, On 05/01/2002 07:28 AM:
>> From: Avi Kivity [mailto:avi@argo.co.il]
>> 
>> I'd like to include content generated by on XSP in another. Looks like
> I
>> have three options:
>> 
>> 1. Use <map:aggregate/> - I don't want to do that as it doesn't allow
> me
>> control of where to place content (I'd like to place one document
> inside
>> another, not alongside).
> 
> Yes, there is not. You could use XSLT to move things around.


I'd rather not write code like that.

> 
> 
>> 2. The xinclude/cinclude transformers - two problems: they don't work
>> with absolute URLs (eg cocoon://mydoc.xsp; I patched this) and they
> 
> IIRC, for xinclude one must use <ns:xinclude base="protocol:/path/"
> href="file"/> or something like this.

It's xml:base. However, href="absolute uri" should work and doesn't. I 
consider that a bug. I provided a patch earlier that fixes it (by 
calling new URL(base, href), which handles relative and ansolute URLs 
correctly).

> 
> 
>> don't understand the cocoon: protocol (anybody know how to work around
>> this?)
> 
> Don't know how could you miss this one:
> 
> http://cvs.apache.org/viewcvs.cgi/xml-cocoon2/src/webapp/docs/samples/xs
> p/aggregate.xsp?rev=1.4&content-type=text/vnd.viewcvs-markup


I tested xinclude: and extrapolated to cinclude. Sorry about that. Will 
test cinclude shortly.

> 
> It's working from the day one.
> 
> Vadim

Avi


---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>