You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by Colm O hEigeartaigh <co...@apache.org> on 2013/01/27 14:10:37 UTC
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.ChainingModel.<init>(ChainingModel.java:44)
at org.apache.wicket.model.CompoundPropertyModel.<init>(CompoundPropertyModel.java:61)
at org.apache.syncope.console.pages.panels.PoliciesPanel$PolicyDataProvider.model(PoliciesPanel.java:301)
at org.apache.syncope.console.pages.panels.PoliciesPanel$PolicyDataProvider.model(PoliciesPanel.java:269)
Colm.
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: NPE in Console
Posted by Colm O hEigeartaigh <co...@apache.org>.
> No problems with 1.0.6-SNAPSHOT: guess then that this bug was introduced
by new rest clients.
> I've opened SYNCOPE-292.
Thanks!
Colm.
On Mon, Jan 28, 2013 at 10:08 AM, Francesco Chicchiriccò <
ilgrosso@apache.org> wrote:
> On 28/01/2013 10:55, Francesco Chicchiriccň wrote:
>
>> On 27/01/2013 18:00, Colm O hEigeartaigh wrote:
>>
>>> 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:
>>>
>>> <Policy DTYPE="SyncPolicy" id="1" description="Global Sync Policy"
>>> type="GLOBAL_SYNC"
>>>
>>> specification="%3Corg.apache.**syncope.common.types.**SyncPolicySpec%2F%3E"/>
>>>
>>>
>>> Starting the console in embedded mode gives the NPE in the
>>> "Configuration"
>>> tab as I mentioned earlier. I should be able to start Syncope without
>>> defining a SyncPolicy right?
>>>
>>
>> Hi Colm,
>> I was just able to reproduce the bug you've reported above (only a minor
>> typo, content.xml not context.xml).
>>
>> I will check this on the 1_0_X and then open an issue.
>>
>
> No problems with 1.0.6-SNAPSHOT: guess then that this bug was introduced
> by new rest clients.
>
> I've opened SYNCOPE-292.
>
> Regards.
>
>
> On Sun, Jan 27, 2013 at 2:10 PM, Francesco Chicchiriccň <
>>> ilgrosso@apache.org wrote:
>>>
>>> Colm O hEigeartaigh <co...@apache.org> 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(Args.java:41)
>>>>> at org.apache.wicket.model.**ChainingModel.<init>(**
>>>>> ChainingModel.java:44)
>>>>> at
>>>>> org.apache.wicket.model.**CompoundPropertyModel.<init>(**CompoundPropertyModel.java:61)
>>>>>
>>>>> at
>>>>> org.apache.syncope.console.**pages.panels.PoliciesPanel$**
>>>>> PolicyDataProvider.model(**PoliciesPanel.java:301)
>>>>> at
>>>>> org.apache.syncope.console.**pages.panels.PoliciesPanel$**
>>>>> PolicyDataProvider.model(**PoliciesPanel.java:269)
>>>>>
>>>>> Colm.
>>>>>
>>>> Check your content.xml or database. If possible start from an empty db
>>>> by
>>>> copying the content.xml from SVN.
>>>>
>>>> Due to recent refactory, in fact, many classes were moved or had their
>>>> name changed.
>>>>
>>>> Hope this helps.
>>>> Regards.
>>>>
>>>
>> --
> Francesco Chicchiriccň
>
>
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
> http://people.apache.org/~**ilgrosso/<http://people.apache.org/~ilgrosso/>
>
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: NPE in Console
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 28/01/2013 10:55, Francesco Chicchiriccò wrote:
> On 27/01/2013 18:00, Colm O hEigeartaigh wrote:
>> 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:
>>
>> <Policy DTYPE="SyncPolicy" id="1" description="Global Sync Policy"
>> type="GLOBAL_SYNC"
>>
>> specification="%3Corg.apache.syncope.common.types.SyncPolicySpec%2F%3E"/>
>>
>>
>> Starting the console in embedded mode gives the NPE in the
>> "Configuration"
>> tab as I mentioned earlier. I should be able to start Syncope without
>> defining a SyncPolicy right?
>
> Hi Colm,
> I was just able to reproduce the bug you've reported above (only a
> minor typo, content.xml not context.xml).
>
> I will check this on the 1_0_X and then open an issue.
No problems with 1.0.6-SNAPSHOT: guess then that this bug was introduced
by new rest clients.
I've opened SYNCOPE-292.
Regards.
>> On Sun, Jan 27, 2013 at 2:10 PM, Francesco Chicchiriccò
>> <ilgrosso@apache.org wrote:
>>
>>> Colm O hEigeartaigh <co...@apache.org> 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(Args.java:41)
>>>> at org.apache.wicket.model.ChainingModel.<init>(ChainingModel.java:44)
>>>> at
>>>> org.apache.wicket.model.CompoundPropertyModel.<init>(CompoundPropertyModel.java:61)
>>>>
>>>> at
>>>> org.apache.syncope.console.pages.panels.PoliciesPanel$PolicyDataProvider.model(PoliciesPanel.java:301)
>>>>
>>>> at
>>>> org.apache.syncope.console.pages.panels.PoliciesPanel$PolicyDataProvider.model(PoliciesPanel.java:269)
>>>>
>>>>
>>>> Colm.
>>> Check your content.xml or database. If possible start from an empty
>>> db by
>>> copying the content.xml from SVN.
>>>
>>> Due to recent refactory, in fact, many classes were moved or had their
>>> name changed.
>>>
>>> Hope this helps.
>>> Regards.
>
--
Francesco Chicchiriccò
ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Re: NPE in Console
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 27/01/2013 18:00, Colm O hEigeartaigh wrote:
> 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:
>
> <Policy DTYPE="SyncPolicy" id="1" description="Global Sync Policy"
> type="GLOBAL_SYNC"
>
> specification="%3Corg.apache.syncope.common.types.SyncPolicySpec%2F%3E"/>
>
> Starting the console in embedded mode gives the NPE in the "Configuration"
> tab as I mentioned earlier. I should be able to start Syncope without
> defining a SyncPolicy right?
Hi Colm,
I was just able to reproduce the bug you've reported above (only a minor
typo, content.xml not context.xml).
I will check this on the 1_0_X and then open an issue.
Thanks for reporting.
Regards.
> On Sun, Jan 27, 2013 at 2:10 PM, Francesco Chicchiriccò <ilgrosso@apache.org wrote:
>
>> Colm O hEigeartaigh <co...@apache.org> 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(Args.java:41)
>>> at org.apache.wicket.model.ChainingModel.<init>(ChainingModel.java:44)
>>> at
>>> org.apache.wicket.model.CompoundPropertyModel.<init>(CompoundPropertyModel.java:61)
>>> at
>>> org.apache.syncope.console.pages.panels.PoliciesPanel$PolicyDataProvider.model(PoliciesPanel.java:301)
>>> at
>>> org.apache.syncope.console.pages.panels.PoliciesPanel$PolicyDataProvider.model(PoliciesPanel.java:269)
>>>
>>> Colm.
>> Check your content.xml or database. If possible start from an empty db by
>> copying the content.xml from SVN.
>>
>> Due to recent refactory, in fact, many classes were moved or had their
>> name changed.
>>
>> Hope this helps.
>> Regards.
--
Francesco Chicchiriccò
ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Re: NPE in Console
Posted by Colm O hEigeartaigh <co...@apache.org>.
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:
<Policy DTYPE="SyncPolicy" id="1" description="Global Sync Policy"
type="GLOBAL_SYNC"
specification="%3Corg.apache.syncope.common.types.SyncPolicySpec%2F%3E"/>
Starting the console in embedded mode gives the NPE in the "Configuration"
tab as I mentioned earlier. I should be able to start Syncope without
defining a SyncPolicy right?
Thanks,
Colm.
On Sun, Jan 27, 2013 at 2:10 PM, Francesco Chicchiriccò <ilgrosso@apache.org
> wrote:
> Colm O hEigeartaigh <co...@apache.org> 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(Args.java:41)
> > at org.apache.wicket.model.ChainingModel.<init>(ChainingModel.java:44)
> >at
>
> >org.apache.wicket.model.CompoundPropertyModel.<init>(CompoundPropertyModel.java:61)
> >at
>
> >org.apache.syncope.console.pages.panels.PoliciesPanel$PolicyDataProvider.model(PoliciesPanel.java:301)
> >at
>
> >org.apache.syncope.console.pages.panels.PoliciesPanel$PolicyDataProvider.model(PoliciesPanel.java:269)
> >
> >Colm.
> >
> >--
> >Colm O hEigeartaigh
> >
> >Talend Community Coder
> >http://coders.talend.com
>
> Check your content.xml or database. If possible start from an empty db by
> copying the content.xml from SVN.
>
> Due to recent refactory, in fact, many classes were moved or had their
> name changed.
>
> Hope this helps.
> Regards.
> --
> Francesco Chicchiriccò
>
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
> http://people.apache.org/~ilgrosso/
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: NPE in Console
Posted by Francesco Chicchiriccò <il...@apache.org>.
Colm O hEigeartaigh <co...@apache.org> 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(Args.java:41)
> at org.apache.wicket.model.ChainingModel.<init>(ChainingModel.java:44)
>at
>org.apache.wicket.model.CompoundPropertyModel.<init>(CompoundPropertyModel.java:61)
>at
>org.apache.syncope.console.pages.panels.PoliciesPanel$PolicyDataProvider.model(PoliciesPanel.java:301)
>at
>org.apache.syncope.console.pages.panels.PoliciesPanel$PolicyDataProvider.model(PoliciesPanel.java:269)
>
>Colm.
>
>--
>Colm O hEigeartaigh
>
>Talend Community Coder
>http://coders.talend.com
Check your content.xml or database. If possible start from an empty db by copying the content.xml from SVN.
Due to recent refactory, in fact, many classes were moved or had their name changed.
Hope this helps.
Regards.
--
Francesco Chicchiriccò
ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/