Problems with url-resolving when using xsltc

[Michael Riedel <me...@gmx.de>]

Hi folks.

I'm just trying to migrate from 2.0.4 to an (almost) current 2.1 version
from CVS, which turns out to be an annoyingly lot of work. In particular, I
face the following problem:

I have a lot of stylesheets which access other files using the document()
function. I know it is often suggested not to use this function, but rather
plug in a xinclude or cinclude transformer after the xslt. But in 2.0.4 it
worked quite fine, and relative paths were resolved according to the
stylessheet location.

However, with 2.1 I could not make work for quite a while. Since paths
relative to the stylesheet did not work, I also tried paths relative to the
sitemap or context. I also tried to use the context:// protocol.

Only a few minutes ago, I found out, that everything works quite fine again,
when I switch back to xalan as xslt-processor. No wonder, since this is the
one used in 2.0.4 by default.

My questions now are:
- Why does the default xslt-processor (xsltc) not support the document()
function? Or do I just have to configure it a different way?
- I've not read the specification, but other sources on xslt imply, that
document() is a standard function, which has to be offered by all xslt
processor. Is xsltc not standarts conform?
- why is xalan not the default xslt processor in cocoon anymore?
- what else do I have to take account of, if I want to change to xsltc?

Sorry I ask those questions here, though I know, I've already read about it
somewhere. But right now I can't find the answers anywere.

Greets, Michael


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org

Re: Problems with url-resolving when using xsltc

[Joerg Heinicke <jo...@gmx.de>]

Hello Michael,

it's simply a bug in XSLTC delivered with Xalan 2.5:

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19324

Regards,

Joerg

Michael Riedel wrote:
> Hi folks.
> 
> I'm just trying to migrate from 2.0.4 to an (almost) current 2.1 version
> from CVS, which turns out to be an annoyingly lot of work. In particular, I
> face the following problem:
> 
> I have a lot of stylesheets which access other files using the document()
> function. I know it is often suggested not to use this function, but rather
> plug in a xinclude or cinclude transformer after the xslt. But in 2.0.4 it
> worked quite fine, and relative paths were resolved according to the
> stylessheet location.
> 
> However, with 2.1 I could not make work for quite a while. Since paths
> relative to the stylesheet did not work, I also tried paths relative to the
> sitemap or context. I also tried to use the context:// protocol.
> 
> Only a few minutes ago, I found out, that everything works quite fine again,
> when I switch back to xalan as xslt-processor. No wonder, since this is the
> one used in 2.0.4 by default.
> 
> My questions now are:
> - Why does the default xslt-processor (xsltc) not support the document()
> function? Or do I just have to configure it a different way?
> - I've not read the specification, but other sources on xslt imply, that
> document() is a standard function, which has to be offered by all xslt
> processor. Is xsltc not standarts conform?
> - why is xalan not the default xslt processor in cocoon anymore?
> - what else do I have to take account of, if I want to change to xsltc?
> 
> Sorry I ask those questions here, though I know, I've already read about it
> somewhere. But right now I can't find the answers anywere.
> 
> Greets, Michael


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org