Note #4 of here[1] shows how the WSDL URL is created when you deploy to
an application server; as you can see, what you have in the wsdl file is
pretty much ignored web-service provider side.

For the client, it is just an issue of modifying the
ENDPOINT_ADDRESS_PROPERTY as shown in Step #7 here[2].  You can use
Spring Dependency Injection for that if helpful.

Glen

[1] http://www.jroller.com/gmazza/date/20071019#notes
[2] http://www.jroller.com/gmazza/entry/using_the_ebay_shopping_api1

Am Montag, den 31.03.2008, 15:07 -0700 schrieb bdm:
> I'm looking for suggestions for a "best practice" in how we accomplish moving
> our CXF code through the various parts of our development lifecycle - i.e.
> development, test, and production.  We have divided these responsibilities
> among three hosts - ws-dev, ws-tst, and ws (production).  We also prefer
> WSDL first development and are supplying our own wsdl to CXF.  
> 
> The problem we have is that we have to either change the wsdl as we move
> through the various stages to reflect the new host, or add ports for each in
> the original wsdl like so:
> 
>     <wsdl:service name="PersonService">
>         <wsdl:port name="PersonPortStg" binding="tns:PersonBinding">
>             <soap:address
>                 location="https://ws-tst/services/personService/PersonSOAP";
> />
>         </wsdl:port>
>         <wsdl:port name="PersonPortDev" binding="tns:PersonBinding">
>             <soap:address
>                 location="https://ws-dev/services/personService/PersonSOAP";
> />
>         </wsdl:port>
>         <wsdl:port name="PersonPortProd" binding="tns:PersonBinding">
>             <soap:address
>                 location="https://ws/services/personService/PersonSOAP"; />
>         </wsdl:port>
>         <wsdl:port name="PersonPortLocal" binding="tns:PersonBinding">
>             <soap:address
>                 location="http://localhost:8080/personService/PersonSOAP"; 
> />
>         </wsdl:port>
>     </wsdl:service>
> 
> We are early enough in the process that we can change our practice without
> much pain right now, but soon we will have to live with what we have.  
> 
> We are really interested in what others are doing to handle this issue.
> 
> 
> Thanks in advance,
> 
> Brent

Reply via email to