No, that kind of thing is not covered by this work. We have ‘requires’ metadata for an attribute that names other attributes that must be set if the given attribute is set, but that’s just a relationship based on defined vs undefined, not on any particular defined value. There would need to be some sort of new metadata added to cover what you describe. Perhaps something like “requires-if => [ { “value” => true, “attributes” => [“another”, “athird”] }, { “value” => false, “attributes” => [“afourth”, “afifth”] }, ] Note that for something like that we couldn’t support it for attributes that allow expressions, as the validation of the constraint would need to happen before we’re able to accurately resolve expressions. But for enum attributes like your example I don’t think that would be an issue. I don’t imagine using an expression to control an enum would be a typical thing. -- Brian Stansberry Manager, Senior Principal Software Engineer JBoss by Red Hat