[
https://issues.jboss.org/browse/AS7-1299?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-1299:
---------------------------------------
If it was flattened out, it could just be a bunch of attributes, each accessible via the
normal read-attribute and write-attribute. The "add" operation handler could
take each attribute as a param.
The nesting comes from the <not> and <any>. The <not/> could be
flattened out with attributes named "not-inet-address"
"not-point-to-point" etc. I suppose the same could be done with "any",
e.g ."any-inet-address=10.0.0.5", "any-point-to-point" etc. Those
attribute names are not very intuitive but TBH I doubt <any/> will be used much.
Emanuel, give some thought to doing it like that; see if there are any gotchas.
Also, I don't think doing it that way would be incompatible with keeping a
"criteria" attribute for backward compatibility.
Interface resource's criteria attribute should be read-write
-------------------------------------------------------------
Key: AS7-1299
URL:
https://issues.jboss.org/browse/AS7-1299
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.0.0.Final
Reporter: Brian Stansberry
Assignee: Emanuel Muckenhuber
Fix For: 7.0.1.Final
http://lists.jboss.org/pipermail/jboss-as7-dev/2011-July/003123.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira