Hi Rex, For me normally having the address fixed in the wsdl is not a good idea. For example if we move applications through the DTAP the endpoint address is changing based on which environment you are working/testing. If the address is fixed in the wsdl, I would need to create wsdl version per environment and every installation for example. Of course an build per environment could solve this hassle but having a dynamic address creation based on the environment where you are running on is often the thing that you would like to have. If needed you can always override it with the property as you mentioned. I am not sure that is the story behind the scene :) but just my opinion.
regards, John On Thu, Feb 21, 2013 at 8:06 AM, Rex Wang <rwo...@gmail.com> wrote: > Hi, devs > > Currently if I set the autoRewriteSoapAddress=false, and have a wsdl file > contained in the application, and the wsdl file specified the soap address, > for example: > <soap:address location="http://a.b.com/services/hello"/> > then, after deployment, the soap:address still will be replaced by such > string > <soap:address location="/HelloService"/> > > Is there any story behind the scene why not just used the one in the wsdl > file, i.e. http://a.b.com/services/hello? > > I ask because with that I don't need specify the publishedEndpointUrl > property explicitly, but could define it in the wsdl file. > > Any comments are appreciated. > > -- > Lei Wang (Rex) > rwonly AT apache.org >
