jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2362) Drop the jackrabbit-jcr-client component
Date Wed, 28 Oct 2009 10:47:59 GMT

    [ https://issues.apache.org/jira/browse/JCR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770891#action_12770891

Tobias Bocanegra commented on JCR-2362:

i try to explain it better.
the idea is to have 1 jar (like a jdbc driver) that encapsulates all code (but nothing more)
that allows you to access a repository remotely.
all you will need in your classpath is the jackrabbit-jcr-client.jar and the jcr.jar.

preferably, it will also contain some classloader magic, that hides the client classes from
the overall classpath. so that it can be used in
projects where other libs are present (e.g. hide commons-io).

> Drop the jackrabbit-jcr-client component
> ----------------------------------------
>                 Key: JCR-2362
>                 URL: https://issues.apache.org/jira/browse/JCR-2362
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr-client
>            Reporter: Jukka Zitting
> The new GenericRepositoryFactory class and JcrUtils.getRepository methods introduced
in JCR-2360 implement an improved version of the jackrabbit-jcr-client functionality.
> Thus I propose that we drop the jackrabbit-jcr-client component.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message