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/05/01 20:10:56 UTC
[jira] Created: (SLING-411) Remove Dependency on Sling API from
jcr/base module
Remove Dependency on Sling API from jcr/base module
---------------------------------------------------
Key: SLING-411
URL: https://issues.apache.org/jira/browse/SLING-411
Project: Sling
Issue Type: Bug
Components: Repository
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: 2.0.0
The jcr/base module has a dependency on the Sling API because the RepositoryAccessor class defines an internal Exception class which extends the SlingException. This exception is only thrown by the RepositoryAccessor.getRepositoryFromURL in case the url parameter is null. This use case is questionable as the existing NullPointerException should be used in these cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-411) Remove Dependency on Sling API from
jcr/base module
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-411.
-----------------------------------
Resolution: Fixed
Committed said fix in Rev. 652610.
> Remove Dependency on Sling API from jcr/base module
> ---------------------------------------------------
>
> Key: SLING-411
> URL: https://issues.apache.org/jira/browse/SLING-411
> Project: Sling
> Issue Type: Bug
> Components: Repository
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> The jcr/base module has a dependency on the Sling API because the RepositoryAccessor class defines an internal Exception class which extends the SlingException. This exception is only thrown by the RepositoryAccessor.getRepositoryFromURL in case the url parameter is null. This use case is questionable as the existing NullPointerException should be used in these cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.