You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Craeg Strong <cs...@arielpartners.com> on 2007/01/08 13:20:06 UTC
catalog resolution for xsl:import in cocoon transformer not working
for me
Hello:
I am just getting back into Cocoon after a long hiatus. I am using
cocoon 2.1.10 on JDK 1.5 via Jetty server on Windows XP.
I have an xslt file with the following import:
txsl:import href="-//OASIS//XSL HTML DocBook V5.0//EN"
which I am trying to resolve using a catalog file:
PUBLIC "-//OASIS//XSL HTML DocBook V5.0//EN"
"thirdparty/docbook-xsl.1.71.1/xhtml/docbook.xsl"
The xslt is invoked as part of a very simple pipeline: map:transform
src="context://src/com/arielpartners/knowledgebase/xsl/paper-html.xsl
I receive the following error message:
java.io.FileNotFoundException:
C:\ade\src\com\arielpartners\knowledgebase\xsl\-\OASIS\XSL HTML DocBook
V5.0\EN (The system cannot find the path specified)
So obviously the entity is not being resolved. I believe my situation
is unique because I use Docbook specializations that are
accomplished by overriding certain docbook XSLT rules (and therefore
importing docbook).
This technique works perfectly in Ant using the xmlcatalog type.
Shouldn't this work in cocoon? Has anyone gotten something like this to
work?
I searched the archives and documentation and couldn't find any examples
that matched my usage pattern.
I guess my alternative would be to re-write my xslt as a preprocessor or
postprocessor on the docbook xslt output and do it in
a two stage pipeline...?
Thanks in advance!
--Craeg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: catalog resolution for xsl:import in cocoon transformer not working
for me
Posted by Joerg Heinicke <jo...@gmx.de>.
On 08.01.2007 13:20, Craeg Strong wrote:
> I have an xslt file with the following import:
> txsl:import href="-//OASIS//XSL HTML DocBook V5.0//EN"
>
> which I am trying to resolve using a catalog file:
> PUBLIC "-//OASIS//XSL HTML DocBook V5.0//EN"
> "thirdparty/docbook-xsl.1.71.1/xhtml/docbook.xsl"
>
> The xslt is invoked as part of a very simple pipeline: map:transform
> src="context://src/com/arielpartners/knowledgebase/xsl/paper-html.xsl
>
> I receive the following error message:
> java.io.FileNotFoundException:
> C:\ade\src\com\arielpartners\knowledgebase\xsl\-\OASIS\XSL HTML DocBook
> V5.0\EN (The system cannot find the path specified)
>
> So obviously the entity is not being resolved. I believe my situation
> is unique because I use Docbook specializations that are
> accomplished by overriding certain docbook XSLT rules (and therefore
> importing docbook).
>
> This technique works perfectly in Ant using the xmlcatalog type.
>
> Shouldn't this work in cocoon? Has anyone gotten something like this to
> work?
> I searched the archives and documentation and couldn't find any examples
> that matched my usage pattern.
>
> I guess my alternative would be to re-write my xslt as a preprocessor or
> postprocessor on the docbook xslt output and do it in
> a two stage pipeline...?
I only remember having done this in Ant as well. But are you sure the
catalogue is used? There are samples delivered with Cocoon. Do they
actually work on your machine?
http://cocoon.zones.apache.org/demos/21branch/samples/catalog/welcome
Regards
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org