Awesome! Thanks for working on a fix so quickly. I did try it with the SingletonFactory and the WebServiceContext itself was always null. That is why I ended up using the PerRequestFactory.
Chris On Tue, Jan 10, 2012 at 10:06 AM, Daniel Kulp <[email protected]> wrote: > > I was able to reproduce the issue and have logged a bug: > > https://issues.apache.org/jira/browse/CXF-4018 > > Testing a fix now. > > > > It seems to work fine if I explicitly set the invoker (and use the > > PerRequestFactory). But this might be too much hacking. Let me know if > this > > a supported approach. > > I wouldn't use the PerRequestFactory unless you really need that behavior. > The default is the SingletonFactory. That said, if you set the singleton > bean right no the factory, that should work fine as well. > > > Dan > > > On Tuesday, January 10, 2012 9:03:19 AM cbwhitebu wrote: > > Daniel, > > > > It seems to work fine if I explicitly set the invoker (and use the > > PerRequestFactory). But this might be too much hacking. Let me know if > this > > a supported approach. > > > > JaxWsServerFactoryBean factory = new JaxWsServerFactoryBean(); > > factory.setBus(BusFactory.getDefaultBus()); > > factory.setServiceName(new QName("http://mediStor.org/x-rays", > > "xRayStorage")); > > factory.setEndpointName(new QName("http://mediStor.org/x-rays", > > "XRaySOAPPort")); > > factory.setServiceClass(FirstService.class); > > factory.setAddress("http://localhost:8080/xray"); > > factory.setWsdlLocation("test.wsdl"); > > factory.setInvoker(new JAXWSMethodInvoker(new > > PerRequestFactory(factory > > .getServiceClass()))); > > Server srv = factory.create(); > > > > Chris > > > > -- > > View this message in context: > > > http://cxf.547215.n5.nabble.com/WebServiceContext-with-WebServiceProvider-t > > p5127015p5134617.html Sent from the cxf-user mailing list archive at > > Nabble.com. > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com >
