On Jul 19, 2010, at 12:42 PM, Jerome Dochez wrote:
>> The child element getFailureDetection() has both @NotNull and
>> @Element(required=true).
>>
>> We are definitely being impacted by defaulting since manually
>> adding an attribute in domain.xml addresses the issue.
> ok let me try to understand.
>
> you add @NotNull to getGroupManagementService() and you get a
> instance back.
> that GroupManagementService has a child element FailureDetection
> which is also annotated with @NotNull but it's null.
>
> so the parent is not null, but the child is ?
No, everything is null. getGroupManagementService is returning null.
There may be more to this: after we add the @NotNull to this element
and rebuild config-api, do we need to rebuild anything else to make
sure this annotation is processed?
Thanks,
Bobby