You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/03/13 09:11:46 UTC

[jira] Closed: (SLING-323) Provide Jackrabbit API over RMI

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

Felix Meschberger closed SLING-323.
-----------------------------------

    Resolution: Fixed

This can be closed for now as the Jackrabbit API is provided over RMI with using the latest Jackrabbit RMI library snapshot.

> Provide Jackrabbit API over RMI
> -------------------------------
>
>                 Key: SLING-323
>                 URL: https://issues.apache.org/jira/browse/SLING-323
>             Project: Sling
>          Issue Type: Bug
>          Components: Repository
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> Discusses as a problem based on the problem report by Vidar Ramdal on the dev list [1]:
> When Sling accesses a repository over RMI, node type registration fails blatantly because the Sling RMI layer does not expose the Jackrabbit API which is required for node type registration as done in Sling.
> BTW: It turns out, that the original problem reported by Vidar most probably is not an RMI problem, but a problem starting the TransientRepository on the server side.
> [1] http://www.mail-archive.com/sling-dev@incubator.apache.org/msg03279.html

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