[
https://issues.apache.org/jira/browse/JCR-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688629#action_12688629
]
angela edited comment on JCR-1877 at 3/24/09 9:29 AM:
------------------------------------------------------
as announced on the dev list: i will go ahead and promoting the spi2dav and
spi2davex sandbox projects to the jackrabbit top level even if there are still
open todos.
in a first step this includes:
- moving spi implementations from jackrabbit/sandbox to
jackrabbit/trunk/jackrabbit-spi2dav
- adding new component to JIRA and moving open issues.
as soon as we have the component released:
- adjust jackrabbit webpage and replace references to spi2dav sandbox project
by links to the
released project.
as time and resources permit:
- address the open issues
- setup automated test execution
regarding the open RepositoryFactory issue:
- as this applies to all spi implementations, i would suggest to create a
separate module
for that. proposed name: jackrabbit-jcr-client. i will put that into a
separate issue. (see JCR-2041)
was (Author: anchela):
as announced on the dev list: i will go ahead and promoting the spi2dav and
spi2davex sandbox projects to the jackrabbit top level even if there are still
open todos.
in a first step this includes:
- moving spi implementations from jackrabbit/sandbox to
jackrabbit/trunk/jackrabbit-spi2dav
- adding new component to JIRA and moving open issues.
as soon as we have the component released:
- adjust jackrabbit webpage and replace references to spi2dav sandbox project
by links to the
released project.
as time and resources permit:
- address the open issues
- setup automated test execution
regarding the open RepositoryFactory issue:
- as this applies to all spi implementations, i would suggest to create a
separate module
for that. proposed name: jackrabbit-jcr-client. i will put that into a
separate issue.
> the spi2dav sandbox project should be put into a common release cycle
> ---------------------------------------------------------------------
>
> Key: JCR-1877
> URL: https://issues.apache.org/jira/browse/JCR-1877
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: sandbox
> Affects Versions: jcr-server 1.4.1
> Reporter: Ken Yue
> Assignee: angela
>
> Remoting JSR170 calls requires obviously both server and client sides. The
> server is available for download, as JCR WebDAV Server in both
> http://www.apache.org/dyn/closer.cgi/jackrabbit/binaries/jackrabbit-jcr-server-1.4.1.jar
> and
> http://www.apache.org/dyn/closer.cgi/jackrabbit/binaries/jackrabbit-webapp-1.4.war.
> However, the client is just casually mentioned as "can be found in the
> Jackrabbit sandbox." This issue is to request that the SPI2DAV client code
> (especially a ResponseFactory that returns a JCR2SPI Repository
> implementation) be available for download as well.
> Furthermore, please make the RepositoryFactory implements
> javax.naming.spi.ObjectFactory so that only configuration (vs. Java coding)
> is needed in order to use it. This is how
> org.apache.jackrabbit.rmi.client.ClientRepositoryFactory works.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
