Red Hat Bugzilla – Bug 815305
Min/max constraints on PropertyList not honored
Last modified: 2013-09-01 06:16:46 EDT
<c:list-property> it is possible to specify the min/max number of occurrences of items of the contained
Unfortunately this is not honored at all in core gui.
Digging into it, shows that the PropertyDefinitionList has the min/max attribute marked as
@Transient -> so they are not even stored in the database.
This would be needed to to say that an XA-Datasource in as7 needs at least one XA-property
setting priority to medium per BZ triage 4/23 (crouch, santos, oleary, foley)
See also https://bugzilla.redhat.com/show_bug.cgi?id=802467#c4
Created attachment 597887 [details]
Max bounds alert
Created attachment 597888 [details]
Min bounds alert
Master commit id: 46f6c86
UI now detects the min and max attributes on the PropertyDefinitionList and validates the number of elements based on the plugin xml config values. See attached screen shots for what the alerting looks like.
this is the description from 5 years ago - JBNADM-1595, created by Heiko:
Heiko is always ahead of his time :-)
Testcase in PluginHandlingTest.testListPropertyMinMax()
name and description are correctly set, but not min and max
Looking at PropertyDefinitionList shows that the properties min/max are transient. IMHO this makes the properties useless.
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.