Re: [Exist-open] saxon xslt 2.0 + xalan conflict and temp fix/hack

[Adam R. <ad...@ex...>]

<snip/>

> I just did some testing that disproves that hypothesis -- but I'm
> still not entirely sure what the problem is.  My hack/fix works even
> if the xalan jar is completely removed from the lib folder, so it
> can't possibly be relying on Xalan.  Apparently, what causes the bug
> is simply Saxon offering itself as an implementation of
> javax.xml.transform.TransformerFactory.  This implies that my removal
> of this service caused eXist to use some other jar instead.  This
> can't be it, though, because I looked through all other jar files both
> in eXist and tomcat to see if something else has this under
> META-INF/services, and nothing else does.

Actually, if you are using JDK 1.5 or JDK 1.6 then a version of Xalan
is shipped in the JDK itself. So it may be falling back to that,
inspecting the Transformer object with the debugger during execution
is the only easy way to tell.

>> Also, you mention serving an XQuery from Cocoon, I am very familiar
>> with eXist and XSLT, but have no knowledge of Cocoon, how do YOU serve
>> the XQuery from Cocoon?
>
> Just put this in sitemap.xmap inside <map:pipeline> and navigate to
> exist/namespace-test:
>
>      <map:match pattern="namespace-test">
>
>        <map:generate src="namespace-test.xq" type="xquery"/>
>
>        <map:serialize encoding="UTF-8" type="xml"/>
>
>      </map:match>
>

This leads me to believe that this is actually a Cocoon issue rather
than an eXist one, but I am happy to investigate further if you can
show me that this is an eXist issue. I suspect if it is Cocoon then
the problem is in the reconfiguration of Cocoon as described in the
Wiki article.

What happens if you store your XQuery inside the eXist database as a
.xql file and execute it from REST?
eXist uses its own XQuery engine, whereas Cocoon relies on either
Xalan or Saxon. So in the case of eXist this cannot be a Saxon/Xalan
issue as eXist only uses Saxon/Xalan for XSLT which you are not using
in your XQuery.

I will take a look at the issue regardless when I have a moment and
see if I can find the problem in what I suspect is the Cocoon
configuration...

Thanks Adam.


-- 
Adam Retter

eXist Developer
{ England }
ad...@ex...
irc://irc.freenode.net/existdb