From: Ben Young <byoung@bj...> - 2003-01-21 21:40:07
I'm working with the exist xmldb protocol under 0.9 and 2.0.4. I'm running
into some very strange things.
When I try and create a cocoon matcher that looks like this:
I get nothing returned. I've tried this both in the root of my web app and
in the subsitemap that was originally the one that came with the eXist
distribution. In the root I get a "resource not found" error and the log
DEBUG (2003-01-21) 16:24.37:442 [access] (/test.xml)
Thread-37/AbstractEnvironment: Resolving 'xmldb:exist:///db/bible/eph'; in
DEBUG (2003-01-21) 16:24.37:443 [access] (/test.xml)
Thread-37/AbstractEnvironment: Resolved to 'xmldb:exist:///db/bible/eph';
WARN (2003-01-21) 16:24.37:447 [access] (/test.xml)
Thread-37/CocoonServlet: The resource was not found
xmldb:exist:///db/bible/eph not found
It seems to be using the file protocol for some reason.
I'll post more about this later. I've got to run for now.
Thanks for any help you might have,
From: Wolfgang Meier <meier@if...> - 2003-01-22 11:51:39
I just recognized that XMLResource.getContentAsSAX sometimes throws an er=
saying something about a "wrong protocol". This happens if you use=20
getContentAsSAX() after calling getContent() on the resource. The reason =
that the resource caches the returned string, which is reused by=20
getContentAsSAX(). While this behaviour is ok when the db is remote, it i=
useless in local mode. The CVS version fixes this.