anonymous wrote :
| Somewhere else there needs to be a type="SecurityDomain' managed object with
a name that matches the SecMetaData.domain value. If the
@ManagedObjectID(type="SecurityDomain") annotation is identifying the key space
of the managed objects of type="SecurityDomain' then I follow. Otherwise I
don't.
|
It is, but I put it on the policy not the deployment. The login-config.xml
can have multiple policies. It is the policy that represents the security domain.
All I'm saying is that where-ever it is, you just need to identify what the id
of the ManagedObject is and its type/qualifier.
From above (but more explicit):
| @MangementObject
| public class SecurityDeployment
| {
| // login-config.xml has many policies
| @ManagedProperty(managed=true)
| Collection<SecurityPolicy> getPolicies();
| }
|
| @ManagedObject
| public SecurityPolicyMetaData
| {
| // This is its id which has qualifier/type/discriminator
"SecurityDomain"
| @ManagedObjectID(type="SecurityDomain")
| public String getName();
| }
|
So the profile service can look at the SecurityPolicyMetaData managed objects
and see they are keyed by "SecurityDomain"/name
and match that with what is on the connection manager metadata.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070703#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...