Fixed the wrong creation of security origin db

[Issue#] N/A
[Problem] Exception settings creation is failed
[Cause] Creator use wrong PkgID
[Solution] Adding the PkgID getting process
[SCMRequest] N/A

Change-Id: I4bbe867ada718643438e738fc3ab8fc662d9a1f7

diff --git a/webapp-detail/exceptionsview.cpp b/webapp-detail/exceptionsview.cpp
index 7108666..7e90741 100755 (executable)
--- a/webapp-detail/exceptionsview.cpp
+++ b/webapp-detail/exceptionsview.cpp
@@ -24,6 +24,7 @@
 #include <dpl/foreach.h>
 #include <dpl/assert.h>
 #include <dpl/string.h>
+#include <dpl/wrt-dao-ro/widget_dao_read_only.h>
 #include <wrt-commons/security-origin-dao/security_origin_dao.h>
 
 //#include <ui-gadget.h>
@@ -62,9 +63,11 @@ const char* const TEXT_NAVIFRAME_TITLE = "Exceptions Settings";
 ExceptionsView::ExceptionsView(Evas_Object* navi, DPL::String appID) :
     m_naviframe(navi)
 {
+    WrtDB::WidgetDAOReadOnly dao(appID);
+    WrtDB::TizenPkgId pkgName = dao.getTizenPkgId();
     m_securityOriginDao =
         SecurityOriginDB::SecurityOriginDAOPtr(
-            new SecurityOriginDB::SecurityOriginDAO(appID));
+            new SecurityOriginDB::SecurityOriginDAO(pkgName));
 }
 
 ExceptionsView::~ExceptionsView(void)