jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1877) the spi2dav sandbox project should be put into a common release cycle
Date Tue, 24 Mar 2009 15:59:53 GMT

     [ https://issues.apache.org/jira/browse/JCR-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

angela resolved JCR-1877.
-------------------------

    Resolution: Fixed
      Assignee: angela

> 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.


Mime
View raw message