&quot;scott.stark(a)jboss.org&quot; wrote : | Good point, the EarStructure is where this should be done. The AltDD interface would need to be in the deployer project so that the general handling of the alt path can be handled in AbstractVFSParsingDeployer. | | If were using the AltDD interface as the typed path/key, wouldn't the programtic usage be: | | | addAttachment(Class<T> type, T attachment); | | VFSDeployment d = new VFSDeployment(ejbjar); | | AltDD altDD = ...("al.ternatelocation"); | | d.addAttachment(AltDD.class, altDD); | | | You could use a class rather than a String to recognise the AltDD, but you'd need more than one. Remember a deployment can be both an EJB and a Web Deployment, e.g. webservices where the web metadata is constructed programmatically by the ws deployers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139623#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...