Hmm, its probably not actually necessary for either one. The Undertow one
was originally copied from the JBoss Web subsystem, and it looks like this
is just a copy paste error.


On Tue, Nov 26, 2013 at 2:09 PM, Paul Ferraro <notifications@github.com>wrote:

> In
> clustering/jgroups/src/main/java/org/jboss/as/clustering/jgroups/deployment/ClusteringDependencyProcessor.java:
>
> > +import org.jboss.as.server.deployment.module.ModuleDependency;
> > +import org.jboss.as.server.deployment.module.ModuleSpecification;
> > +import org.jboss.modules.Module;
> > +import org.jboss.modules.ModuleIdentifier;
> > +import org.jboss.modules.ModuleLoader;
> > +
> > +/**
> > + * {@link DeploymentUnitProcessor} that adds the clustering api to the deployment classpath.
> > + * @author Paul Ferraro
> > + */
> > +public class ClusteringDependencyProcessor  implements DeploymentUnitProcessor {
> > +
> > +    private static final ModuleIdentifier API = ModuleIdentifier.create("org.wildfly.clustering.api");
> > +    private static final ModuleIdentifier SINGLETON = ModuleIdentifier.create("org.wildfly.clustering.singleton");
> > +
> > +    static {
>
> I based this DUP off of the UndertowDependencyProcessor - but I see your
> point. The subsystem add handler seems more appropriate.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/wildfly/wildfly/pull/5523/files#r7923484>
> .
>