> What I was referring to is simply that Xindice has to this point always > been considered a server. Because of this we need to continue to ship > something that runs as a server, so we need to pick a mechanism to enable > that.
What about describing the Xindice as a set of XML repository services that can run as a stand-alone server or imbedded in another server engine such as Tomcat, an EJB server, etc. ? Now that Kernel seems to be going away there needs to be some other assembly point for those services. JMX would be a great framework for this and you could shutdown, restart and configure services in runtime etc. When running Xindice stand-alone we just start a JMX spine and let it be the server where the services start up. When running embedded you just add those services to an existing spine making integration with tomcat, Jboss, Weblogic etc. etc. very easy ;). For those servers that are not JMX based we provide a way for simple lifecycle administration (start and shutdown) of the stand-alone server without calls to System.exit() and the like. My 2 cents, Per Nyfelt
