You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Ken Yue (JIRA)" <ji...@apache.org> on 2008/12/10 20:20:44 UTC
[jira] Updated: (JCR-1877) the spi2dav sandbox project should be put into a common release cycle

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

Ken Yue updated JCR-1877:
-------------------------

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

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


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