But, I have a question. For the grep implementation to work, the XMLRPC server needs to find an org.apache.xindice.server.rpc.messages.<method-name> class, right? What would be the recommended way of adding a new class without having to recompile the Xindice.jar file each time I want to add a new RPC handler?
I was primarly thinking of the package org.apache.xindicex.* (x like in javax)
Of course this is only a first idea and we may have to (re)use the standard org.apache.xindice but I really would like to have a clear separation.
As for the rpc.messages, I would say that the current solution can be modified to fit new needs. You could try an ugly
try {
class.forName(...xindice...)
} catch () {
class.forName(...xindicex...)
}but it's definitively too ugly. My fingers almost refused to type the code :-)
So it will be up to you to propose a nice solution :-)
I would like to start organizing the source tree a little bit better. So since the addons are not part of the project, there no reason that the code is mixed with the rest of the main source. A root project "addons" would make sense IMO. Simple and efficient.
addons
src
lib
classes
dist
build.xml-Vladimir
-- Vladimir R. Bossicard Apache Xindice - http://xml.apache.org/xindice
