On Tuesday 12 October 2010 12:33:25 pm Benson Margulies wrote: > I guess this goes onto the list of CXF JAX-WS extensions that we need > to document: that SIB-only annotations work on the SEI. I could have > sworn that I proved that targetNamespace had to be on the SIB to be > fully effective, but I guess I was wrong.
Well, it depends on the namespace. :-) If both the SEI and SIB are in the same package and DON'T define any targetNamespace, you're fine. The generated namespaces would match. If they are in different packages, then there would be an issue. If you define targetNamespace on one and not the other, and the targetNamespace doesn't match the auto generated one, then there would also be an issue. Dan > > On Tue, Oct 12, 2010 at 12:14 PM, jaybytez <[email protected]> wrote: > > Thank you both very much for your help. > > > > I finally got it to work, I had a bug in my web.xml because I thought I > > could wildcard context files that exist in jars and that appears not to > > be valid. > > > > I appreciate both your responses. Looks like I can point implementor at > > the SIB and implementorClass at the SEI and I can successfully use CXF > > to send a web service request through > > org.apache.cxf.jaxws.JaxWsProxyFactoryBean and successfully consume that > > message through my service endpoint all by disconnecting the SEI and > > SIB. The only relationship I have is that the SIB implements the SEI. > > > > Thanks for the input...Jay > > -- > > View this message in context: > > http://cxf.547215.n5.nabble.com/implementor-and-implementorClass-tp32080 > > 80p3209148.html Sent from the cxf-user mailing list archive at > > Nabble.com. -- Daniel Kulp [email protected] http://dankulp.com/blog
