[
https://issues.apache.org/jira/browse/JCR-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483228
]
Julian Reschke commented on JCR-801:
------------------------------------
More thoughts on this:
- leaving javax.jcr.tck.workspacename undefined may be too obscure, as an empty
string may be a valid workspace name (and in fact it is in my impl, being the
name of the (single) default workspace)
- another alternative would be to set it to the name of a known-not-to-exist
workspace and just to catch NoSuchWorkspaceExceptions, mapping them to
NotExecutableExceptions -- the drawback here that it may obscure typos in the
config.
Thus my new proposal is to compute once for all whether the repository supports
multiple workspaces (get available workspace names on superuser session, and
check the array size to be > 1), and then throw NotExecutableExceptions
whenever a different workspace is needed.
If there are no objections, I'll add this tomorrow.
> Support for single-workspace repositories
> -----------------------------------------
>
> Key: JCR-801
> URL: https://issues.apache.org/jira/browse/JCR-801
> Project: Jackrabbit
> Issue Type: Improvement
> Components: JCR TCK
> Reporter: Julian Reschke
> Priority: Minor
>
> There should be a way to configure the test cases in a way such that
> NodeTest.java can pass although the repository implementation does not
> support multiple workspaces.
> The cleanest approach probably would be to allow javax.jcr.tck.workspacename
> to stay undefined, and to skip the tests in that case. Alternatives would be
> a special name indicating lack of support for other workspaces, or an
> additional config variable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
