My Opinion:
-Change the build process to allow multiple Runtime Adaptations to the
Xindice core. The xindice core should be accessible through a (Xindice)
standard set of interfaces.
1. Default Adaptation: Utilizing a servlet engine
a) Packaged with Tomcat 4.0.4+ (most people will want to
untar, and start it up.
b) Packaged as a separate war so anyone can run it in
the servlet environment of their choice (assuming they don't want
tomcat).
2. Other Adaptations: Whatever anyone else wants to contribute
This gives us the flexibility for an out-of-the-box server, a webapp
plugin, or anything else we can dream up.
-Kevin
-----Original Message-----
From: Per Nyfelt [mailto:[EMAIL PROTECTED]
Sent: Friday, July 19, 2002 8:49 AM
To: [EMAIL PROTECTED]
Subject: RE: Servlet Engine - Opinions
> 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
