Fix compilation issue due to generic Exception 15/32115/1
authorJim Hahn <jrh3@att.com>
Mon, 19 Feb 2018 16:17:19 +0000 (11:17 -0500)
committerJim Hahn <jrh3@att.com>
Mon, 19 Feb 2018 16:18:45 +0000 (11:18 -0500)
After modifying common to remove generic Exceptions, drools-pdp would
no longer compile.  Had to modify drools-pdp to accomodate the
specific exception.

Change-Id: Ib804da2ebfc7dbf5f4035ba3d48832ffe541f902
Issue-ID: POLICY-246
Signed-off-by: Jim Hahn <jrh3@att.com>
feature-state-management/src/main/java/org/onap/policy/drools/statemanagement/DroolsPDPIntegrityMonitor.java

index 382f01e..46bba91 100644 (file)
@@ -430,14 +430,14 @@ public class DroolsPDPIntegrityMonitor extends IntegrityMonitor
                }
        }
 
-       public static DroolsPDPIntegrityMonitor getInstance() throws Exception{
+       public static DroolsPDPIntegrityMonitor getInstance() throws IntegrityMonitorException{
                if(logger.isDebugEnabled()){
                        logger.debug("getInstance() called");
                }
                if (im == null) {
                        String msg = "No DroolsPDPIntegrityMonitor instance exists."
                                        + " Please use the method DroolsPDPIntegrityMonitor init(String configDir)";
-                       throw new Exception(msg);
+                       throw new IntegrityMonitorException(msg);
                }else{
                        return im;
                }