You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Torsten Curdt <tc...@dff.st> on 2000/08/10 10:43:53 UTC
taglib within XSL?
Let's say I have a namespace based taglib.
I know I can use it in XSP but what's up
with XSL? Can I also access a taglib from
a XSL? ... Even if there is XSP in it?
puzzled
--
Torsten
Re: taglib within XSL?
Posted by Sebastien Koechlin <sk...@ivision.fr>.
Torsten Curdt wrote:
> Let's say I have a namespace based taglib.
> I know I can use it in XSP but what's up
> with XSL? Can I also access a taglib from
> a XSL? ... Even if there is XSP in it?
XSL is XML, so you can have an XSP produced XSL.
BUT, as XSP is processed only when you make an HTTP
request, you have to give an absolute URL for your
stylesheet:
<?stylesheet type="text/xsl" href="http://my.host/xsl/my-xsl.xsp"?>
It works, but it costs: your stylesheet is writen to a
stream and parsed back.
A great feature would be to load them through
cocoon, and to be able to add <?cocoon-process..?>
to its.
Will/Does Cocoon2 solves this ? Is it possible to
have a tree of processors to build the final document ?
Something like :
A.xml -[XSL]-> A1.xsp -[XSP]-> A2.xml
B.xsl / |
|
C.xml -[SQL]-> C1.xml ->[XInclude]
|
D.xml \ |
E.xsl -[XSL] V
| A3.xml
V |
D1.xsp -[XSP]-> D2.xsp -[XSL]
|
V
A4.xml
--
Sébastien Koechlin