Hi Dhiraj, it looks like sth wrong in your WSDL, most likely the service name defined in your WSDL does not match with the service name specificed in your spring cfg file.
BTW, I don't really get the reason why you want to access to the WSDL metadata like wsdlLocation, serviceName, portName, operation name etc. JAX-WS SEI is WSDL-centric, there is always a direct mapping between SEI's java types/method and WSDL's types/operations, i.e., you look at the WSDL, then you know what kind of request is a valid request that can be sent to server. JAX-WS Provider/Dispatch interface however, is not WSDL-centric, you do not need a wsdl at all to work with a Provider server. The only thing a client who wants to invoke a Provider service need to know is the service publishing address. Of course, you can still specify a WSDL through @WebServiceProvider() or spring configuration, but your Provider service is not bound by this WSDL. In another word, WSDL metadata info like wsdlLocation, serviceName, portName, operation name for Provider are no use and should not be used. Cheers, Jervis > -----Original Message----- > From: Dan Diephouse [mailto:[EMAIL PROTECTED] > Sent: 2007?8?19? 12:31 > To: [email protected] > Subject: Re: Generic Provider<DOMSource> server and WSDL metadata > > > Hmmm I have no idea how that's occurring... Any chance your > wsdl has zero > operations in it? > > - Dan > > On 8/17/07, Bokde, Dhiraj <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > I am trying to build a generic server using > Provider<DOMSource>. But I > > want to make the WSDL metadata, wsdlLocation, serviceName, portName, > > etc. to be user configurable, without having to re-compile > the Provider > > with new WebServiceProvider annotations for every new WSDL. > > > > I thought I'd be able to do this with an empty WebServiceProvider > > annotation for my Provider like below: > > > > <snip> > > @WebServiceProvider() > > @ServiceMode(value = Service.Mode.MESSAGE) > > public final class GenericMessageProvider implements > Provider<DOMSource> > > { > > <snip> > > > > And the jaxws:endpoint element in a spring container > cxf-beans.xml, like > > below: > > > > <snip> > > <jaxws:endpoint id="myEndpoint" > implementor="#genericProvider" > > address="/myLocation/" serviceName="msp:MyService" > > wsdlLocation="classpath:wsdl/MyWSDL.wsdl" > > xmlns:msp="http://my.service";> > > </jaxws:endpoint> > > <snip> > > > > But this throws an NPE when I load the cxf-beans.xml using > Tomcat. The > > relevant log4j logs are attached. > > > > Any ideas what's causing this? > > > > Thanks, > > Dhiraj. > > > > > > > -- > Dan Diephouse > Envoi Solutions > http://envoisolutions.com | http://netzooid.com/blog > ---------------------------- IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
