"scott.stark(a)jboss.org" wrote : The only issue is how to generically integrate the alt-dd path. Most ee descriptor has an alt-dd child of the root element, so one way to handle this would be to extend AbstractParsingDeployerWithOutput to have an alt-dd property that specifies element name of the alt-dd, and createMetaData(DeploymentUnit unit, String name, String suffix, String key) would do a simple jaxp query of the document to see if alt-dd path name exists. It would have to be encapsulated in another abstract method like: | | | | protected abstract String getAltName(DeploymentUnit unit, String name) throws Exception; | | | | as we don't know how to obtain the input stream for the name at the AbstractParsingDeployerWithOutput level. The jaxp default impl would have to be added to AbstractVFSParsingDeployer. | | http://jira.jboss.com/jira/browse/JBDEPLOY-27 | Why don't you make an interface, e.g. | public interface AltDD | { | String getAltDD(); | } | Then the metadata classes could implement it and parsing deployers check it regardless of where it appears. On Alex's point, these just need to be added as attachments by the EarStructure and checked by the relevant parsing deployer. In principle it should be possible to do the same thing programmatically even for non-ears. | VFSDeployment d = new VFSDeployment(ejbjar); | d.addAttachment("EJBAltDD", "al.ternatelocation"); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139273#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...