Sebastian Koske wrote:
This script will then create all datasources, queues, topics and security domains and so on and also deploy the archive into the running server. I think this will be acceptable and maybe also suitable for you?
Yes, such an approach will be acceptable for the deployment to our servers. Since we use the tool Fabric for deployment, we might even be able to copy the script out of the EAR and then run it programmatically to already achieve the affect Jesper intended with his .cli archives.
I'm thinking how to best support local development though. Currently our system is such that a developer simply has to checkout the EAR project in Eclipse, add it to the JBoss tools server runtime and he or she is good to go.
Letting the developer run the script once is painful, but doable. However, during development resources can be added, removed or renamed at any time and I'm not sure how to best handle that.