[ https://issues.apache.org/jira/browse/SYNCOPE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564310#comment-13564310 ]
Colm O hEigeartaigh edited comment on SYNCOPE-292 at 1/28/13 2:54 PM: ---------------------------------------------------------------------- Thanks Jan! Fix confirmed. However, I am seeing something else which is slightly odd. If I browse to the Configuration page, and to "Synchronization Policies", I see: 0 Synchronization Policy Same goes for Account Policies + Password Policies. Instead of listing a policy with id of "0" for each case, it should just not list any policy right? Colm. Ps. An error appears in the logs: SEVERE: Servlet.service() for servlet [syncope-core-rest] in context with path [/syncope] threw exception [Request processing failed; nested exception is org.apache.syncope.core.persistence.dao.NotFoundException: No account policy found] with root cause org.apache.syncope.core.persistence.dao.NotFoundException: No account policy found at org.apache.syncope.core.rest.controller.PolicyController.getGlobalAccountPolicy(PolicyController.java:205) was (Author: coheigea): Thanks Jan! Fix confirmed. However, I am seeing something else which is slightly odd. If I browse to the Configuration page, and to "Synchronization Policies", I see: 0 Synchronization Policy Same goes for Account Policies + Password Policies. Instead of listing a policy with id of "0" for each case, it should just not list any policy right? Colm. > NPE when accessing Configuration page with no global sync policy > ---------------------------------------------------------------- > > Key: SYNCOPE-292 > URL: https://issues.apache.org/jira/browse/SYNCOPE-292 > Project: Syncope > Issue Type: Bug > Components: console > Affects Versions: 1.1.0 > Reporter: Francesco Chicchiriccò > Assignee: Jan Bernhardt > Fix For: 1.1.0 > > > As reported in ML [1], there is an issue when no global sync policy exists. > [1] http://syncope-dev.1063484.n5.nabble.com/NPE-in-Console-tt5712327.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira