jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-64) Hi, i am new to JCR, i want to know where the concept of multiple workspace in a JCR comes to play
Date Thu, 17 Mar 2005 14:02:20 GMT
     [ http://issues.apache.org/jira/browse/JCR-64?page=history ]
     
Jukka Zitting resolved JCR-64:
------------------------------

    Resolution: Invalid

Thanks for the question! However, I'd recommend you to send such general design and usage
questions to the jackrabbit-dev mailing list instead of this issue tracker, as the issue tracker
is better suited for tracking bug reports and feature requests than answering usage or API
questions.

Jackrabbit supports multiple workspaces as described in the JSR 170 specification (section
4.10 in the proposed final draft). You can use workspaces either for partitioning your content
repository into separate virtual content areas, or you can use the versioning support to link
content between different workspaces in various staging/live or other setups.

In addition to section 4.10 (Workspaces) of the JSR 170 spec, you should also check out sections
8.2 (Versioning) and 7.1.7 (Updating and Cloning nodes across Workspaces) to get an overall
picture of the workspace and versioning support in JCR.

> Hi, i am new to JCR, i want to know where the concept of multiple workspace in a JCR
comes to play
> --------------------------------------------------------------------------------------------------
>
>          Key: JCR-64
>          URL: http://issues.apache.org/jira/browse/JCR-64
>      Project: Jackrabbit
>         Type: Wish
>   Components: docs
>     Reporter: raj
>     Assignee: Jukka Zitting
>     Priority: Minor

>
> Hi,
>     I went through the JSR 170 specification. Meanwhile i got interested in knowing about
Jackrabbit. I wanted to know where the concept of multiple workspace in a repository comes
to play. In the specification it is given that nodes with same UUID across workspace are corresponding
nodes, also it is given that except UUID all other things like childnode, property, nodetypes
can be different. This is bit confusing which raised my question.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message