A few months ago David H Nebinger published a blog article with the
title BND and @Meta
Deprecations - you can find it here.
The post is very helpful but it does not consider a critical problem
of the configuration interface.
If you use the "required = true" property even for just one
@Meta.AD() you can no longer find the configuration values in the
various portlets or services of the application.
@Meta.AD( deflt = "", name = "some.configuration.field", description = "some.configuration.field.desc", required = true, type = Meta.Type.String ) public String someConfigurationField();
The "required = true" element breaks the configuration.
Only "required = false" can be used.
I confirm this issue in LP 7.4.3 GA 101.
Can anyone else confirm they found this issue?
In my opinion this is a critical issue in the Liferay configuration
framework and perhaps warrants opening a JIRA Ticket.
