[Exist-open] Upgrading to 0.9.2 : necessary?

[Olivier R. <ol...@ri...>]

Hi all,

I'm currently the previous 0.9.1 version of eXist. 

I get null pointer exception when I run un nested xpath query on a
document that occurs in the local implementation of the XPAth service. I
can run a standard xpath query on an existing document, but not on
document returned by a previous xpath query: the query method which
takes an XMLResource. Here the stack trace:

java.lang.NullPointerException
        at
org.exist.xmldb.LocalXPathQueryService.query(LocalXPathQueryService.java
:100)
        at
org.exist.xmldb.LocalXPathQueryService.query(LocalXPathQueryService.java
:76)

I watched exist's example to create my nested query and I'm casting the
XPAthService to XPAthServiceImpl as shown. 

First of all, I'm using Jboss 3.2.1. The first time I installed eXist, I
had to make some changes both to cocoon and to eXist because jBoss was
complaining a console appender was incorrectly configured. But the worst
was that jBoss logging was redirected to the log files managed by both
cocoon and exist. I managed to remove logkit both from cocoon and exist
to avoid this.

But now, my hacks doesn' work anymore. I'm getting randomly Outmemory
errors (why?), or at best, Cocoon refuses to start up.

Well here my questions:
1. Do I need to upgrade my version of eXist to use nested xpath queries?
Well, I'm not really fond of upgrading exist as this could imply a long
migration problem for me. If this solves my problem with nested queries,
I'm ready to do it. 2. In the case I need to upgrade, has anyone got rid
of this logging problems with jBoss? We are parsing our jBoss log files
and having new log files would be a pain for us.


Regards.

Olivier.