I'm working on a web-service application that is meant to be configurable at deploy-time for any host machine - i.e., we don't know the WSDL port of the target host machine at build time.
What standard ways are there to set the WSDL port at deploy-time rather than at build time? The only solution I have so far is to leave a mock value in the WSDL and replace it with a deployment tool that actually modifies the WSDL file during install of the service. However if there's a more standard way to do this with an external properties file - whether or not it's a JBoss-specific technique - I'd be grateful to know about it. TIA, Chris View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859670#3859670 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859670 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
