You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/01/11 14:32:54 UTC
[jira] Created: (JCR-2459) Improved error reporting from
JcrUtils.getRepository
Improved error reporting from JcrUtils.getRepository
----------------------------------------------------
Key: JCR-2459
URL: https://issues.apache.org/jira/browse/JCR-2459
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: jackrabbit-jcr-commons
Reporter: Jukka Zitting
Assignee: Jukka Zitting
Priority: Minor
The service provider mechanism and the null return value used by the RepositoryFactory API makes it a bit difficult to troubleshoot cases where a repository can not be accessed. It would be helpful if the JcrUtils.getRepository methods reported as accurate failure information as possible in case the requested repository is not found.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-2459) Improved error reporting from
JcrUtils.getRepository
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-2459.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0-beta6
Done in revision 897858.
> Improved error reporting from JcrUtils.getRepository
> ----------------------------------------------------
>
> Key: JCR-2459
> URL: https://issues.apache.org/jira/browse/JCR-2459
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-commons
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 2.0-beta6
>
>
> The service provider mechanism and the null return value used by the RepositoryFactory API makes it a bit difficult to troubleshoot cases where a repository can not be accessed. It would be helpful if the JcrUtils.getRepository methods reported as accurate failure information as possible in case the requested repository is not found.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2459) Improved error reporting from
JcrUtils.getRepository
Posted by "Alaksandr Voitau (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876223#action_12876223 ]
Alaksandr Voitau commented on JCR-2459:
---------------------------------------
URISyntaxException is swallowed.
{code:java}
public static Repository getRepository(Map<String, String> parameters)
throws RepositoryException {
..
try {
...
} catch (URISyntaxException e) {
// Ignore invalid URIs
}
{code:java}
This catch block was probably left empty by some intention. However if URI is incorrect, no message indicating this reason will be in log.
> Improved error reporting from JcrUtils.getRepository
> ----------------------------------------------------
>
> Key: JCR-2459
> URL: https://issues.apache.org/jira/browse/JCR-2459
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-commons
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 2.0-beta6
>
>
> The service provider mechanism and the null return value used by the RepositoryFactory API makes it a bit difficult to troubleshoot cases where a repository can not be accessed. It would be helpful if the JcrUtils.getRepository methods reported as accurate failure information as possible in case the requested repository is not found.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.