On Thursday 14 March 2013 11:00 PM, frowe_at_us.ibm.com wrote:
> I'm ok with it's use on the config property of an java bean, but if
> that was the intent, why didn't we simply update the schema to indicate
> that and allow developers not using annotations to take advantage of
> the same feature?
Marking any config property as mandatory was only possible through
@NotNull (as the required-config-property was only allowed on
ActivationSpec). In 1.6 we were deprecating required-config-property in
favour of @NotNull, so we did not expect users to use
required-config-property on other config-properties beyond
ActivationSpec and use the schema to override them.
Thanks
--Siva.