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

[jira] Resolved: (SLING-256) Use null for the workspace name in JCR calls if configured name is empty

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

Bertrand Delacretaz resolved SLING-256.
---------------------------------------

    Resolution: Fixed

Implemented as described above in revision 629058

I have checked all uses of SlingRepository.getWorkspace() for potential NPEs, should be fine unless I missed something.

> Use null for the workspace name in JCR calls if configured name is empty
> ------------------------------------------------------------------------
>
>                 Key: SLING-256
>                 URL: https://issues.apache.org/jira/browse/SLING-256
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>
> The goal is to use the JCR rule [1] that says ""if workspaceName is null, a default workspace is automatically selected by the repository implementation".
> Code changes:
> -SlingRepository.getDefaultWorkspace() returns null if an empty name is configured
> -Check that this doesn't cause NPEs
> -Document the configuration variables that set this value, to indicate that an empty value means "let the JCR Repository select the default workspace".
> [1] http://www.day.com/maven/jsr170/javadocs/jcr-1.0/javax/jcr/Repository.html#login(javax.jcr.Credentials,%20java.lang.String)

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