[jboss-jira] [JBoss JIRA] (WFCORE-314) Configure child resources as mandatory or its cardinality in ResourceDefinition
Brian Stansberry (JIRA)
issues at jboss.org
Mon Dec 1 15:43:39 EST 2014
[ https://issues.jboss.org/browse/WFCORE-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry moved WFLY-2915 to WFCORE-314:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-314 (was: WFLY-2915)
Affects Version/s: (was: 8.0.0.Final)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: (was: 9.0.0.Beta1)
> Configure child resources as mandatory or its cardinality in ResourceDefinition
> -------------------------------------------------------------------------------
>
> Key: WFCORE-314
> URL: https://issues.jboss.org/browse/WFCORE-314
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Pedro Igor
>
> Currently, the ResourceDefinition does not provide a good way to configure a child resource as mandatory or even its cardinality. Instead of that, manual validations are required inside handlers.
> The idea is remove manual validations and let it be done automatically by the model.
> Considering the following example:
> {code:xml}
> <parent-resource>
> <child-resource/>
> </parent-resource>
> {code}
> Would be useful if we could mark the 'child-resource' above as mandatory. Or even:
> {code:xml}
> <parent-resource>
> <child-resource/>
> <child-resource/>
> <child-resource/>
> <child-resource/> <!-- This is invalid. Only 3 childs are supported. -->
> </parent-resource>
> {code}
> Where we can specify the cardinality for a child-resource so we can configure the min/max occurrences.
> I think the latter approach is more flexible and can be used to get a resource as mandatory or specify its number of occurrence.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
More information about the jboss-jira
mailing list