The point I was trying to make before was that it probably be easier
for the mangement layer to deal with a map, so an alternative markup
might be to define on the collection:
| @MangementObject
| public class SecurityDeployment
| {
| // login-config.xml has many policies
| @ManagedProperty(managed=true map-id="name"
id-qualifier="SecurityDomain")
| Collection<SecurityPolicy> getPolicies();
| }
|
Then the profile service when it does getProperty("policies")
would get a TableMetaValue of String(id/name)->ManagedObject
instead of having to iterate over an array of managed objects.
It's still a Collection underneath, we've just exposed it as a map
(since we know it has a unique id) for ease of use.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070708#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...