This week I have rewritten the Security Deployer (or more precisely to split into
deployers based on the type of metadata). It is ready and I am checking it in tomorrow.
The classes look as follows:
| public abstract class AbstractSecurityDeployer<T extends IdMetaData>
| extends AbstractDeployer
| {
| public AbstractSecurityDeployer()
| {
| setStage(DeploymentStages.POST_CLASSLOADER);
| ...
| setOutput(ServiceMetaData.class);
| ...
| }
| }
|
| public class EarSecurityDeployer extends
AbstractSecurityDeployer<JBossAppMetaData>
| {
| }
|
| public class EjbSecurityDeployer
| extends AbstractSecurityDeployer<JBossMetaData>
| {}
|
| public class WarSecurityDeployer extends
AbstractSecurityDeployer<JBossWebMetaData>
| { }
|
An issue that exists for addDependencies/addAttributes api addition to ServiceMetaData is
that the internal data structures are Lists (rather than Sets) and hence there can be
duplication of dependencies.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130920#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...