You could probably handle that by having a seperate .xml file for the
deployment:
foo.war
foo.war.settings.xml
Or something like that. I don't really like it though, as if you just
copy both in there and are not using .dodeploy its possible for the
deployment to be deployed before the xml file has been copied (you could
argue this is user error I suppose).
Stuart
Jaikiran Pai wrote:
By the way, I just realized last night that if we go by this approach
of
setting up child resources of deployment resource, then it won't work
with filesystem based deployments since those deployments do not have
their info persisted in the standalone*.xml.
-Jaikiran