Marijan Milicevic pushed to branch bugfix/HSTTWO-3808 at cms-community / 
hippo-site-toolkit


Commits:
2d1debc4 by Marijan Milicevic at 2016-10-20T11:16:54+02:00
HSTTWO-3808 ResourceContainer: Don't log warning when resource path is 
invalid
- just log message at  info level

- - - - -


1 changed file:

- 
commons/src/main/java/org/hippoecm/hst/core/linking/AbstractResourceContainer.java


Changes:

=====================================
commons/src/main/java/org/hippoecm/hst/core/linking/AbstractResourceContainer.java
=====================================
--- 
a/commons/src/main/java/org/hippoecm/hst/core/linking/AbstractResourceContainer.java
+++ 
b/commons/src/main/java/org/hippoecm/hst/core/linking/AbstractResourceContainer.java
@@ -1,5 +1,5 @@
 /*
- *  Copyright 2010-2014 Hippo B.V. (http://www.onehippo.com)
+ *  Copyright 2010-2016 Hippo B.V. (http://www.onehippo.com)
  * 
  *  Licensed under the Apache License, Version 2.0 (the "License");
  *  you may not use this file except in compliance with the License.
@@ -173,12 +173,7 @@ public abstract class AbstractResourceContainer implements 
ResourceContainer {
        } catch (PathNotFoundException e) {
            log.debug("Cannot find resource node for path '{}' beloning to 
pathInfo '{}'", actualPath, pathInfo);
        } catch (RepositoryException e) {
-           final String message = e.getMessage();
-           if (log.isDebugEnabled()) {
-               log.warn("RepositoryException: '{}'", message);
-           } else if (message != null && !message.startsWith("Invalid path:")) 
{
-               log.warn("RepositoryException: '{}'", message);
-           }
+           log.info("RepositoryException: '{}'", e.getMessage());
        }
         return null;
     }



View it on GitLab: 
https://code.onehippo.org/cms-community/hippo-site-toolkit/commit/2d1debc40fa04324de92d7a776e1df073c4884a6
_______________________________________________
Hippocms-svn mailing list
Hippocms-svn@lists.onehippo.org
https://lists.onehippo.org/mailman/listinfo/hippocms-svn

Reply via email to