On Mon, Jan 12, 2009 at 7:13 PM, Andrew Clegg <[email protected]> wrote: > 2009/1/12 Alexey Zavizionov <[email protected]>: >> Yes, I have the string "my.service" within my wsdl file for generating >> source of client and server side. >> But, when I triggering the ?wsdl url for a service there is no "my.service". > > I *think* this is because... > > When you hit the ?wsdl URL for a service, the dynamically served copy > of the WSDL uses the URL as provided in the HTTP request to fill in > the soap:address location attribute. > > (Try it: hit the ?wsdl in your browser but use the machine's IP > address instead of hostname.)
Works, you are right. > > But if you generated the client code from the WSDL loaded from the > filesystem, it takes the location attribute literally. Obviously, it > can't know where you're going to deploy the server to... > > Try generating client code but using the WSDL served dynamically from > the server. (i.e. provide the URL rather than a path on your local > filesystem.) I cannot do this. I have no server with this service. I have to develop server and client sides. I guess, that's why I have a long path for 'wsdlLocation' WebService annotation for my service class pointed to file on local system. thanks. > > Andrew. > > -- > New site launched: http://biotext.org.uk/ > > I am retiring my old email addresses. > Please use [email protected] where firstname = andrew. >
