Promoting SPI from contrib

[Jukka Zitting <ju...@gmail.com>]

Hi,

The SPI project is becoming more mature, and people are starting to
use it for connector and other stuff. The full round-trip from JCR to
SPI and back using the jcr2spi and spi2jcr components is also mostly
finished, which means that it is quite easy to hook up various JCR
stuff with the SPI. It would also be good to start taking the first
steps in integrating SPI with jackrabbit-core. Thus I would like to
start promoting the SPI components from contrib with a goal of having
at least a part of them included in the Jackrabbit 1.4 release.

First and foremost we would promote the following:

    * spi/spi into jackrabbit-spi
    * spi/commons into jackrabbit-spi-commons

At this point we could make jackrabbit-core depend on spi and
spi-commons for some of the generic functionality, even though we
wouldn't still use the RepositoryService or the other central
interfaces in jackrabbit-core.

Then, as things settle, we would promote the following:

    * spi/jcr2spi into jackrabbit-jcr2spi
    * spi/spi2jcr into jackrabbit-spi2jcr

This would preferably be the set of SPI components to be included in
Jackrabbit 1.4. We might also want to consider including the SPI RMI
component in case it already shows a marked performance improvement
over JCR RMI.

BR,

Jukka Zitting

Re: Promoting SPI from contrib

[Angela Schreiber <an...@day.com>]

hi jukka

 > Thus I would like to start promoting the SPI components
 > from contrib with a goal of having at least a part of them
 > included in the Jackrabbit 1.4 release.

i'm obviously in favour of the promotion.
however, i would prefer to promote not only

 >    * spi/spi into jackrabbit-spi
 >    * spi/commons into jackrabbit-spi-commons

but also the 2 components that allow to use the SPI as
an alternative JCR implementation and to create connectors
on released code.

 >   * spi/jcr2spi into jackrabbit-jcr2spi
 >   * spi/spi2jcr into jackrabbit-spi2jcr

jukka, how is the official procedure for the promotion?
will there be an extra vote or can we continue on this
if nobody objects?

angela

Re: Promoting SPI from contrib

[Stefan Guggisberg <st...@gmail.com>]

On 7/3/07, Felix Meschberger <fm...@gmail.com> wrote:
> Hi,
>
> I agree to moved SPI to prime time, with one single exception:
>
> > At this point we could make jackrabbit-core depend on spi and
> > spi-commons for some of the generic functionality, even though we
> > wouldn't still use the RepositoryService or the other central
> > interfaces in jackrabbit-core.
>
> If we would want to have jackrabbit-core agnostic of spi, we should not
> add a dependency on it. This would possibly require adding the spi
> libraries to any web application without any pressing need.

i share felix' concerns. why would we want to make jackrabbit-core
depend on spi?

cheers
stefan

>
> So, I am not convinced, that this would a good idea.
>
> Regards
> Felix
>
>

Re: Promoting SPI from contrib

[Jukka Zitting <ju...@gmail.com>]

Hi,

On 7/3/07, Felix Meschberger <fm...@gmail.com> wrote:
> > At this point we could make jackrabbit-core depend on spi and
> > spi-commons for some of the generic functionality, even though we
> > wouldn't still use the RepositoryService or the other central
> > interfaces in jackrabbit-core.
>
> If we would want to have jackrabbit-core agnostic of spi, we should not
> add a dependency on it. This would possibly require adding the spi
> libraries to any web application without any pressing need.
>
> So, I am not convinced, that this would a good idea.

My rationale is to get us started on the path of reconciliation for
the two transient space implementations (jackrabbit-core and jcr2spi)
we currently have in Jackrabbit.

However, I agree that it's bad to bundle this goal with the issue of
promoting SPI from contrib, so consider this "jackrabbit-core depends
on spi" idea withdrawn until I come up with a more convincing
rationale or roadmap in a separate thread.

BR,

Jukka Zitting

Re: Promoting SPI from contrib

[Felix Meschberger <fm...@gmail.com>]

Hi,

I agree to moved SPI to prime time, with one single exception:

> At this point we could make jackrabbit-core depend on spi and
> spi-commons for some of the generic functionality, even though we
> wouldn't still use the RepositoryService or the other central
> interfaces in jackrabbit-core.

If we would want to have jackrabbit-core agnostic of spi, we should not
add a dependency on it. This would possibly require adding the spi
libraries to any web application without any pressing need.

So, I am not convinced, that this would a good idea.

Regards
Felix