1 of 1 people found this helpful
What if you use a domain?
You can have a couple of servers at different hosts and only connect to the domain-controller deploy your app once and the controller distribute it to all the different servers as configured.
See Domain Setup - JBoss AS 7.1 for more details and ask if you still have questions
Also you can take a look at deployment plans
Thank you for the replies. The domain host would be perfect and that was our original infrastructure. However, these decisions are not in my control and they have opted for standalone instances controlled by an apache load balancer instead of the domain controller for jboss. I think the idea is that they host many different environments and want to be able to support tomcat and other servers with the same architecture, instead of using jboss exclusively.
In any event, I can't use it, but you are correct to suggest that solution
In case it helps someone else, the solution I was able to work out (though it needs a whole lot more testing) is very similar to my original solution. It turns out you can throw the configuration element for jboss-as-maven plugin inside the execution tags, so I can configure the endpoint for each execution element. I was not able to find any posts or examples suggesting this approach and stumbled across it blindly, so in case it helps anyone else, see below: