[
https://issues.apache.org/jira/browse/JCR-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650485#action_12650485
]
angela commented on JCR-1877:
-----------------------------
> Angela, what's the current status in spi2dav?
there are a couple of things i'd like to be addressed before we promote the
spi2dav sandbox:
- rework the URIResolver (see TODOs in the code)
- setup automated test execution
- do some more testing
> Should we target at releasing it in Jackrabbit 1.6?
- i would be nice if we managed to do that for 1.6 but i can't promise that i
have the time.
> 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
> Issue Type: New Feature
> Components: sandbox
> Affects Versions: jcr-server 1.4.1
> Reporter: Ken Yue
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
