|
From: <ad...@jb...> - 2006-06-29 14:33:12
|
The deployer creates the DeploymentInfo (and classloader) like the old rar deployer, Except now the rar metadata is from ra.xml and the xxx-rar.xml overrides. There is just an additional source of metadata from the xxx-ra.xml it would also be that one that is watched for hotdeployment purposes. I'm not saying you should do it this way. It is one possible way to achieve the externalization of the overrides. Another would be an even more generic deployer that has something like: | <deploy> | <file>xxx.Xar</file> | <alt-dd-file>/some/location</alt-dd-file> | or | <alt-dd> | <!--inline stuff--> | </alt-dd> | </deploy> | But that has problems with the current way we use extensions to derive the deployment ordering. Again not an insurmountable problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954389#3954389 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954389 |