jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2255) activity storage path
Date Tue, 11 Aug 2009 13:40:14 GMT

    [ https://issues.apache.org/jira/browse/JCR-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741866#action_12741866
] 

Tobias Bocanegra commented on JCR-2255:
---------------------------------------

the only workspace that is shared among all others is the version workspace and it is virtually
mounted at /jcr:system/jcr:versionStorage. creating a new persistent workspace for just the
activities is a bit overkill, also in the light of the upcoming restructure of the jcr:system
shared space.
the problem is that a virtual item state provide can only have 1 root, so the activities were
put below /jcr:system/jcr:versionStorage/jcr:activities.

to change this we could:
1) try to allow multiple roots for virtual providers
2) introduce a activities workspace and create a virtual provider just for this
3) try to create a shared node at /jcr:system/jcr:activities

i favor to relax the spec in this respect, but will try if i can implement (1)

> activity storage path
> ---------------------
>
>                 Key: JCR-2255
>                 URL: https://issues.apache.org/jira/browse/JCR-2255
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: versioning
>            Reporter: Julian Reschke
>
> JSR-283 states in 15.12.3:
> "15.12.3 Activity Storage
> Activities are persisted as nodes of type nt:activity under system-generated
> node names in activity storage below /jcr:system/jcr:activities."
> As far as I can tell, this is currently not the case.
> A related test case, org.apache.jackrabbit.test.api.version.ActivitiesTest#testActivitiesPath,
apparently was taken out accidentally.
> If Jackrabbit can't implement this JCR requirement, we either need to document it, or
raise it as issue in the JCR Expert Group.

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