Now that I understand about using axis2.xml to parameterize AAR file settings, I have another problem I need to solve.
We have one WSStack per environment (dev, QA, production, etc). Each environment supported a pair of Brokers: one for the US Vista system accessed through a Broker on one port, and the Global Vista system accessed through a different Broker on a different port.
I can see that the configuration can be flexible enough for multiple settings, but the example shows the use of <service-name="*"> for a generic setting and <service-name=“myservice”> for specific service overrides. I don’t want to have to constantly be changing this file for each new service deployment, but we’ll be adding services in both systems all the time. Is it possible to wild-card a service in the configuration file as such:vista.tcc.etn.com:10103 RPC/SRV1/CALLNAT vista.tcc.etn.com:10203 RPC/SRV1/CALLNAT
…so that any service starting with “GV” will be caught by the exception override?
If not, then how should I handle this so that I don’t need to update this for every new GV web service I create? Do I need to ask for the number of WSStack environments to be doubled?