Or supply a ParameterValidator which looks for the alternatives? That will happen in the
MODEL stage
On 19 Apr 2012, at 13:04, Jeff Mesnil wrote:
Replying to my own question.
I can subclass AbstractWriteAttributeHandler.applyUpdateToRuntime() to
verify the attribute alternatives for the resource (e.g.
HttpManagementWriteAttributeHandler).
The only difference is that this occurs at RUNTIME step, not at VERIFY.
Is it a big difference? (in case of an alternative already defined, I
flag the context as rollback only anyway).
thanks to tomaz for pointing this out
jeff
--
Jeff Mesnil
JBoss, a division of Red Hat
http://jmesnil.net/
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev