Since you have multiple people interested in this and none of them are current committers, the easiest thing to do is just create a sourceforge project. You don't have to run it long term, just use the resources for a while. I'd still use this mailing list though. Once there's actual working code then we can roll it into the core project here and get commit for whoever wants to work on it long term.

Really though, this code should be fairly simple. You have two example XML:
DB implementations for Xindice already, as well as both the CORBA and XML-RPC server components. All you're really doing is moving the code from the server components, directly into the XML:DB implementation. Thereby cutting out the network layer. The only thing a little tricky will be bootstrapping the database, but you can look at org.apache.xindice.server.
services.XindiceService to see how it works.


There's also a set of Unit tests that are part of the XML:DB reference implementation download from http://www.xmldb.org/xapi.

On Friday, June 14, 2002, at 09:09  AM, Mark J. Stang wrote:

Since this is an Apache project, I don't quite know where to
start.   Also, we need advice from Kimbro on where to start.
And someone will need commit, maybe we can submit through
someone else on the project.

Mark

Matt Liotta wrote:

If need be, I can assign one of my engineers as well. I would rather get
started myself and see how things go before assigning additional
resources though.

-Matt

-----Original Message-----
From: Mark J. Stang [mailto:[EMAIL PROTECTED]
Sent: Friday, June 14, 2002 7:55 AM
To: [EMAIL PROTECTED]
Subject: Re: Xindice as a servlet?

It appears that we have about three of us who are interested.
Matt also expressed interest.   Anyone else?

Mark

Vanessa Williams wrote:

Mark J. Stang wrote:

I agree. I think you are right, the core pieces need to be
defined
as Interfaces. Everyone should code to those.

That would be great.

Right now everyone sees the XML:DB as the interface to Xindice, as
I
do
also. In reality, there is a Xindice interface defined through
the
org.apache.xindice.core.* classes.   The CORBA and XML-RPC
interfaces provide an API to use these classes.   That API is the
one
defined by XML:DB.

So it seems the first step should be to define interfaces to the
"core" of
Xindice. And then implement the XML:DB API on top of that,
without
using CORBA or XML-RPC.   When that is done, we should be able
to talk to Xindice either remotely or embedded with the same API.

This would also make me a happy camper.

You asked "Does anyone else need this bad enough to sit down and
write
the
code?" I suppose I'm getting to the point where I do. I'm trying to
build a
commercial server product on top of Xindice and in its current form
that's
not practical. While I'd rather spend my time writing my app, it
seems I
am
spending a fair bit of time poking around Xindice anyway (or trying
to),
so...given some direction and an appropriately-sized chunk to bite
off,
I'd
be willing to help.

--
Mark J Stang
Architect
Cybershop Systems



-- Mark J Stang Architect Cybershop Systems

-- Mark J Stang Architect Cybershop Systems


Kimbro Staken
Java and XML Software, Consulting and Writing http://www.xmldatabases.org/
Apache Xindice native XML database http://xml.apache.org/xindice
XML:DB Initiative http://www.xmldb.org



Reply via email to