On Wednesday 16 March 2011 5:13:30 AM Raj Floyd wrote: > Hi, > > The tool wsdl2java -impl option generates the service implementation class. > The class has the mention of WSDL location through @WebService annotation. > My question is: > > 1. What is the advantage of specifying the WSDL location versus not > specifying as you can still get the WSDL upon publshing the service by > invoking http://....?wsdl URL
If you specify the wsdlLocation, then at runtime, we can return the original WSDL (with slight modifications like the soap:address). Things like annotations and schemas and such can be maintained. Without the wsdlLocation, we have to generate a new WSDL at runtime which wouldn't have all of that. Also, if the WSDL has things like WS-Policy fragments in it, we'll need the WSDL at runtime to act on those policies. > 2. To my understanding, it seems WSDL is an abstract artifact and therefore > even if I have the existing WSDL, I still need to provide the > implementation business logic for my service generated from the said WSDL. Right. -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
