NPE in Console

Hi guys, I am getting a NPE in the console when I click on the "Configuration" tab using the latest trunk code: Root cause: java.lang.IllegalArgumentException: Argument 'modelObject' may not be null. at org.apache.wicket.util.lang.Args.notNull(Args.java:41) at org.apache.wicket.model.C

NPE in Console

Hi guys, I am getting a NPE in the console when I click on the "Configuration" tab using the latest trunk code: Root cause: java.lang.IllegalArgumentException: Argument 'modelObject' may not be null. at org.apache.wicket.util.lang.Args.notNull(Args.java:41) at org.apache.wicket.model.

Console update issue

Hi all, I've noticed a (minor) issue when I create a new user in Syncope (1.0.5) with a virtual attribute + propagage to a backend (H2 database). If I change the virtual attribute in the backend, and then edit the user in Syncope again, the old value of the virtual attribute is displayed. The valu

Schema mappings usability thought

Hi all, When creating schema mappings in the Console, if you select the "AccountId" or "Password" checkbox the "external attributes" tab gets blanked out. Should the "Mandatory" value also change to "true" by default for each of these cases (but remain editable)? I would imagine that for most case

Re: NPE in Console

Colm O hEigeartaigh ha scritto: >Hi guys, > >I am getting a NPE in the console when I click on the "Configuration" >tab >using the latest trunk code: > >Root cause: > >java.lang.IllegalArgumentException: Argument 'modelObject' may not be >null. > at org.apache.wicket.util.lang.Args.notNull(Ar

Re: NPE in Console

Hi Francesco, I think this may be a genuine bug...I can reproduce the problem by generating a new archetype for 1.1.0-SNAPSHOT, and copying the "context.xml" from "core/src/main/resources" to "core/src/test/resources" and then editing it to remove the "SyncPolicy" definition: Starting the conso