I would suggest ripping it out of the installations for Cocoon and Xindice, and only having it in your JDK installation endorsed dirs.
I think they both require the latest versions anyway, so they shouldn't complain.



Upayavira wrote:

[EMAIL PROTECTED] wrote:

You need to put Xalan and Xerces jars into jre/lib/endorsed for them to be taken into account over and above the crappy default JDK jars.


Problem is, if I'm using Xindice in embedded mode within Cocoon, both Cocoon and Xindice share an endorsed folder, but need different Xalan and Xerces jars.

Therefore, I've switched to running Xindice standalone in a separate webapp (which can have a separate endorsed folder). Now I've just got to work out what xmldb:xindice:// URL to use to access my database.

Thanks,

Upayavira


WH



Upayavira wrote:

Tom Bradford wrote:

What you're seeing is a Xalan versioning conflict. You probably have a version of Xalan on your classpath, or as part of your servers libraries that is inconsitent with what Xindice is expecting. Xindice is currently expecting version 2.4.0. That error message looks to me as though the version of Xalan that's on your class path is much older than expected. Are you using Xindice with a version J2EE? J2EE bundles an older version of Xalan.




I tried Xalan 2.6, which comes with Cocoon, but that failed too with a XMLDBException: NAMESPACE_ERR. So I just removed Xalan from my classpath, to use the one that comes with JDK1.4.1, which works okay in one environment but not the other. Maybe there's still a rogue Xalan in my servlet container classpath.

So it looks like I've got to work out how to tell Jetty (my servlet container) to use a specific Xalan (endorsed.libs=xxx, etc).

Thanks for this. I'll give it a go.

Regards, Upayavira


-- Tom Bradford - http://www.tbradford.org/ CTO - The dbXML Group - http://www.dbxml.com/ Project Labrador - http://www.dbxml.com/labrador/


Upayavira wrote:

[EMAIL PROTECTED] wrote:

This depends on what search do you want.
If you want to search "hello" string within music node then you should use //music[contains(string(),'hello')]


or if you want to search "hello" within the the document as under :

<music>
<title>hello</title>
</music>

then you may use //music/title[contains(string(),'hello')]


Avik,

I've managed to get: //music[filename[contains(string(),"athe")]] to work from my unit tests, but with the same query run within Cocoon I still get:
java.lang.NoSuchMethodError: org.apache.xpath.compiler.OpMap.getOpMap()[I


So there's something different between my two environments. Hmm. Both use the xindice-1.1b1.jar. Hmm.

Any ideas?

Thanks for getting me this far.

Regards, Upayavira

Avik


----- Original Message ----- From: Upayavira <[EMAIL PROTECTED]> Date: Tuesday, December 9, 2003 2:28 pm Subject: What XPATH is available



I am trying the following XPath:

//music[contains(title, 'hello')]

which gives me an error:
java.lang.NoSuchMethodError: org.apache.xpath.compiler.OpMap.getOpMap()[I
This suggests that this XPath expression is not supported by XIndice. Can someone tell me what XPath I do have access to? Is it just the //music[title = 'hello'] kind? If so, this is rather limited/limiting.


Thanks,

Upayavira



























Reply via email to