You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xsp-dev@xml.apache.org by Tagunov Anthony <at...@nnt.ru> on 2001/03/15 08:21:12 UTC
Re: util:include + xsp problem
On Thu, 15 Mar 2001 03:21:42 +0000 (UTC), Forge wrote:
>
>HI there,
>
>I wish to include some xml data in my first xml file.
>This works.
>
>But my taglib cannot access the included data..
>
>I know why, because the code that inserts the xml file is nicely placed
>between the code that examines it..
>
>Is there any way to do this (nicely?)
>Maybe it's time to add XInclude support?
>
>Btw, I know one way to do it and that is using a logicsheet as stylesheet,
>and defining a template that inserts the xml data..
>If all goes well, this stylesheet is first applied to the input xml data,
>and then my logicsheet is applied to that data..
>
>Would this approach work?
Yes, sure it will.
What we really want (i want things like that too) is too include
some code BEFORE the XSP is run. A sort of PRE-PROCESSING
before XSP.
util:include is not the trick, as you pointed out.
XInclude is not the case because nothing should run
before xsp processor in C1 (actually you can
place <?cocoon-process type="xinclude"?>
before <?cocoon-process type="xsp"?>
but this should be considered a hack and will
have the drawback that whenever you change the
file being included the cache will be cleaned for the
page, but the page really won't be recompiled.
Using external XML entities is another solution
but they look ugly, and changes on them also
do not get detected by the caching system
I actually have been asking the developers if
they think that <xsp:include> functionality
would be a good complement to
<util:include>, xinclude, external entities and
xsl logicsheets technologies. I see it
as a pre-processor inside the xsp mechanism,
something like <xsp:include href=".."/>
Maybe this still is a good idea..
Best regards, Tagunov Anthony
Re: util:include + xsp problem
Posted by Matt Sergeant <ma...@sergeant.org>.
On Thu, 15 Mar 2001, Tagunov Anthony wrote:
> Using external XML entities is another solution
> but they look ugly, and changes on them also
> do not get detected by the caching system
>
> I actually have been asking the developers if
> they think that <xsp:include> functionality
> would be a good complement to
> <util:include>, xinclude, external entities and
> xsl logicsheets technologies. I see it
> as a pre-processor inside the xsp mechanism,
> something like <xsp:include href=".."/>
>
> Maybe this still is a good idea..
No it's still a bad idea. Fix the broken implementation, not add work
arounds! Cocoon needs some serious work in the area of cache invalidation,
maybe now would be a good time to take a look at it.
--
<Matt/>
/|| ** Founder and CTO ** ** http://axkit.com/ **
//|| ** AxKit.com Ltd ** ** XML Application Serving **
// || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
// \\| // ** mod_perl news and resources: http://take23.org **
\\//
//\\
// \\
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: util:include + xsp problem
Posted by Matt Sergeant <ma...@sergeant.org>.
On Thu, 15 Mar 2001, Tagunov Anthony wrote:
> Using external XML entities is another solution
> but they look ugly, and changes on them also
> do not get detected by the caching system
>
> I actually have been asking the developers if
> they think that <xsp:include> functionality
> would be a good complement to
> <util:include>, xinclude, external entities and
> xsl logicsheets technologies. I see it
> as a pre-processor inside the xsp mechanism,
> something like <xsp:include href=".."/>
>
> Maybe this still is a good idea..
No it's still a bad idea. Fix the broken implementation, not add work
arounds! Cocoon needs some serious work in the area of cache invalidation,
maybe now would be a good time to take a look at it.
--
<Matt/>
/|| ** Founder and CTO ** ** http://axkit.com/ **
//|| ** AxKit.com Ltd ** ** XML Application Serving **
// || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
// \\| // ** mod_perl news and resources: http://take23.org **
\\//
//\\
// \\
---------------------------------------------------------------------
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: util:include + xsp problem
Posted by Matt Sergeant <ma...@sergeant.org>.
On Thu, 15 Mar 2001, Tagunov Anthony wrote:
> Using external XML entities is another solution
> but they look ugly, and changes on them also
> do not get detected by the caching system
>
> I actually have been asking the developers if
> they think that <xsp:include> functionality
> would be a good complement to
> <util:include>, xinclude, external entities and
> xsl logicsheets technologies. I see it
> as a pre-processor inside the xsp mechanism,
> something like <xsp:include href=".."/>
>
> Maybe this still is a good idea..
No it's still a bad idea. Fix the broken implementation, not add work
arounds! Cocoon needs some serious work in the area of cache invalidation,
maybe now would be a good time to take a look at it.
--
<Matt/>
/|| ** Founder and CTO ** ** http://axkit.com/ **
//|| ** AxKit.com Ltd ** ** XML Application Serving **
// || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
// \\| // ** mod_perl news and resources: http://take23.org **
\\//
//\\
// \\