"alex.loubyansky(a)jboss.com" wrote :
| I guess, I misunderstand this. AFAICS, the alt-dd is specified in the application.xml
per module. Like this
|
| ...
|
| The ModuleMetaData has a property for alt-dd but it's not used except in the web
deployer.
Sure, your right, I was thinking it could also show up at the descriptor level. That would
be silly.
"adrian(a)jboss.org" wrote :
| 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.
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);
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139425#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...