grenoml wrote:
1. XUpdate
This does not work with the current 1.1 code. I have been
working with Vladimir on this issue and it looks like he has figured
out the problem. There is already a posting on this issue on
xindice-users if you want more info "1.1: problem performing XUpdate
operation from servlet". Please excuse some of my ranting.
I opened bug #14839 on this issue.
I see that Vladimir is actively working on it, I'll leave this to him.
2. Command-line scripts
The current scripts do not work with JDK1.4. On windows boxes
they don't work if you install Xindice in a directory that contains any
spaces in the path.
I opened bug #14369 and provided a fix for the problem. A
complete set of new and tested Unix and Windows scripts that fixes
these problems is attached to the bug. I also added a new script
'xindicewar' that utilizes only the classes in the WAR and not java/lib
in the dev tree. That way the command-line script and the servlet are
in-sync with each other. I also sent Vladimir an Xindice build.xml
file that adds this new script to the WAR so that you now have a
self-contained unit that you can just drop into Tomcat and its
command-line interface script is located in WEB-INF for users to
utilize.
I'm using your scripts (cool job!) but I'm also facing some strange problems (the xindice.bat file calls :lcp with pseudo-absolute pathnames so the classpath is built as \config;\dist\xindice-1.1b.jar and so on.. obviously not working). I'll see what I can do: meanwhile, would you mind posting the build.xml diff to Bugzilla (same bug) so that I can try it out?
3. Context Config File
Xindice needs a context config file for Tomcat so that you can
map the context path to the WAR structure name. That way your url can
always stay http://localhost:8080/Xindice... no matter what you name
your WAR file. I created/tested a sample context config file for
Vladimir and sent it to him. He may have already checked this in.
The file is there I suppose (config/xindice.xml), but here I disagree. I tend to think that there shouldn't be anything like a Catalina configuration file, Catalina is not the only app server around. The idea is that the WAR should be as app-server agnostic as possible, so it's OK to add a configuration snippet, but I'd rather call the WAR Xindice.war so that there are no misunderstandings.
Ciao,
-- Gianugo Rabellino
