[jboss-dev-forums] [Design of POJO Server] - Re: JACC: Policy Configuration needs to be linked with child

[anil.saldhana@jboss.com]

Some information from Scott on this:

  | ***I don't believe the jacc policy linking is being handled correctly currently. In the discussions we had around this in the forums I believed we needed to separate out linking into a separate aspect that had component deployers registering their local policies on whatever the root policy was in the deployment graph. The lifecycle of the aspect is what should be triggering the policy refresh and commit behaviors. This should not be done by deployers.
  | 
  | ***but we are overusing deployers. Deployers should not be manipulating the runtime state of components. Deployers should only be manipulating metadata that is consumed by the kernel deployer at which point, the lifecycle of the components triggers the correct transition to running objects based on dependencies and aspects associated with the component.
  | 
  | ***
  | maybe its just that we are not comfortable with the new model. A large part of it is that what the legacy deployers do is wrong under the mc model, and moving to the correct way of doing this is not a trivial port of code. As the profile service is brought into the picture, we will have to be even more clear about deployer operation as an assembly line that takes metadata in and outputs its transformation without doing too much in terms of assumptions regarding runtime behavior of components.
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992037#3992037

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992037