AH! Now I understand how people are running into this issue! Thanks! I've never been able to reproduce this (without it being a missing dependency issue). Your test project was perfect.
Basically, when we initialize the bus, we search the classpath for all the META-INF/cxf/cxf.extension file it can find and use that to load the Bus extensions. The issue is the assembly plugin doesn't know how to merge those from the various cxf-rt-XXXX jars into a single extension file. Couple of solutions: 1) Instead of depending on individual cxf modules, depend on cxf-bundle. The cxf-bundle has everything properly merged together. 2) Instead of using assembly plugin, use the maven shade plugin with filters to merge things together. See the pom we use to create the bundle: https://svn.apache.org/repos/asf/cxf/trunk/distribution/bundle/all/pom.xml The AppendingTransformer things are key. The stuff for the spring.handlers and spring.schemas is important as well. Dan On Monday 20 October 2008 5:31:35 pm [EMAIL PROTECTED] wrote: > Thanks for the link and for your comments Glen. > > > I don't think I ever needed the cxf.xml file on the client just > > for bringing in the Spring beans mentioned in your example. I > > wonder if you're missing a CXF dependency > > Yeah, the tutorials on the Internet that specifically mention clients > generally omit any reference to a cxf.xml file. That's why I was so > dismayed the client didn't work without it. > > At any rate, my project definitely does not work without the cxf.xml file. > I zipped up the entire Maven project and put it on my web site in case > anyone wants to download and try it: > http://www.logicsector.com/justin/java/weather-client.zip > > If anyone can let me know which dependency I'm missing, I'll happily > update the blog with the updated info. > > Cheers, > > Justin > > > Hmmm...I don't think I ever needed the cxf.xml file on the client just > > for bringing in the Spring beans mentioned in your example. I wonder if > > you're > > missing a CXF dependency in your Maven POM that is requiring you to do > > that. > > But it's been awhile since I created a client-only project so I may very > > well be wrong here--I need to update my own example so I can check again. > > > > Anyway, I added your article to our resources page[1]--you should see it > > within a few hours, after the site refreshes. > > > > Thanks, > > Glen > > > > [1] http://cxf.apache.org/resources-and-articles.html > > > > jmorgan-2 wrote: > >>> is this file required even if you use the commented out > >>> JaxWsProxyFactoryBean method of instantiating your client? > >> > >> Yes, it's required either way. In fact, using JaxWsProxyFactoryBean is > >> the original way I wrote my client; I discovered the current way (which > >> I > >> think is cleaner) while Googling around for CXF client examples. > >> > >> Cheers, > >> > >> Justin > >> > >>> Justin, > >>> > >>> Interesting read. The one question I have though, since I've not had > >>> to > >>> include a cxf.xml config file for my clients (that I know of), is this > >>> file required even if you use the commented out JaxWsProxyFactoryBean > >>> method of instantiating your client? > >>> > >>> Thanks, > >>> John > >>> > >>> [EMAIL PROTECTED] wrote: > >>>> Hi all, > >>>> > >>>> After resolving my recent trouble creating a basic SOAP client with > >>>> CXF, > >>>> I > >>>> thought I'd write up a quick "Hello World" tutorial. Hopefully it > >>>> will > >>>> be > >>>> of use to anyone starting out with CXF in the future. > >>>> > >>>> "How to create a WSDL-first SOAP client in Java with CXF and Maven" > >>>> http://logicsector.wordpress.com/2008/10/19/how-to-create-a-wsdl-first > >>>>-soap-client-in-java-with-cxf-and-maven/ > >>>> > >>>> Same URL as TinyURL: http://tinyurl.com/65l5o > > > > -- > > View this message in context: > > http://www.nabble.com/How-to-create-a-WSDL-first-SOAP-client-with-CXF-and > >-Maven-tp20052351p20067485.html Sent from the cxf-user mailing list > > archive at Nabble.com. -- Daniel Kulp [EMAIL PROTECTED] http://dankulp.com/blog
