[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24219#action_24219
]
Hudson CI server commented on MAGNOLIA-2360:
--------------------------------------------
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia_main-trunk
#1001|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1001/]
added test for getRepositoryProvider()
throws an IllegalArgumentException instead of letting an NPE blow up later
when an unknown workspace/repository provider is asked for
MAGNOLIA-2745 ContentRepository.getRepository() now yields a meaningful
exception (and actually logs the error, which wasn't even the case before)
> Need a clear warning or exception when a repo/workspace does not exist.
> -----------------------------------------------------------------------
>
> Key: MAGNOLIA-2360
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2360
> Project: Magnolia
> Issue Type: Improvement
> Components: core
> Reporter: Grégory Joseph
> Assignee: Grégory Joseph
> Fix For: 4.1.1
>
> Attachments: tree-wrong-workspace-name-exception.txt
>
>
> Currently, if you do MgnlContext.getHierarchyManager("some-random-name"),
> there's a high chance you'll end up with an intricate NullPointerException.
> This should fail early with a clear exception message.
> See attachment for an example of a stacktrace when one tries to instanciate a
> tree with a wrongly configured workspace name. (see MGNLDMS-99)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
