[starksm64]

The commit should be a result of the jacc policy bean starting. The jacc policy object should depend on the policy configuration objects for the deployment units. The output of the SecurityDeployer should be:

+ JaccPolicy
- PC1
- PC2
...

where each PCn is a policy configuration for the associated deployment unit, and the JaccPolicy has a dependency on the PCn. Once all PCs have been started, the JaccPolicy is started and at that point the PCs can be linked.

[anil.saldhana]

That made sense.

I also want to move the xacml policy registration to the Security Deployer. This is an on-demand process currently done by the component deployments.

[anil.saldhana]

The changes to the security deployer are ready. Now the components (web,ejb) do not do anything with jacc policy but the policy configuration lifecycle is surrounding the component lifecycles.

I will be checking in the changes on Wednesday along with the security context changes.

The top level jacc policy service bean is dependent on policy configuration facade service beans for the components and commits the parent when its subcomponents have all started.