Hi,
On 6/4/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
On 6/4/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> jackrabbit-jcr-servlet (depends on jackrabbit-jcr-commons)
> jackrabbit-jcr-rmi-servlet (depends on jackrabbit-jcr-rmi,
> jackrabbit-jcr-servlet)
> jackrabbit-core-servlet (depends on jackrabbit-core,
jackrabbit-jcr-servlet)
No, I would say that there is only one single component for the
servlet integration case. Of course you would get dependencies on the
jcr-commons (you have this any probably) on rmi (true, but i you
require rmi, you need rmi) and core (worst actually, but if you create
a repository, you need this anyway).
If we start adding container support to the different components,
there is no apparent stop - or would you add support for Spring, Pico
Container, Nano Container, whatever-container to each of the
components ?
Makes sense. I guess we could make the jackrabbit-jcr-rmi and
jackrabbit-core dependencies of the potential jackrabbit-servlet
component optional so a client would need to explicitly add those
dependencies if it wants to use those servlets.
BTW: rmi depends on Xerces. Just to support XML import, this is rather
heavy, isn't it ?
Agreed. Time for an improvement issue?
BR,
Jukka Zitting
