I'm not clear if you're creating a SOAP client or web service provider. Generally speaking, use cxf.xml only for SOAP clients; for web service providers, unless you're doing some big-time CXF surgery, cxf-servlet.xml or anythingelse.xml as shown in Steps #7 and #8 here is preferable: http://www.jroller.com/gmazza/date/20080417#WFstep7
At any rate, for providers, the config file needs to be in the WEB-INF folder, as shown above in step #8. For SOAP clients using Maven, the cxf.xml should be in src/main/resources[1]. The cxf.xml (along with everything else in resources) will then get copied to the classpath during mvn install. HTH, Glen [1] http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html 2008-06-06 jsolderitsch wrote: > Still looking for help on this. > > I want to learn where to place my custom cxf.xml in my source tree so that > is does get picked up during wsdl2java. > > After some more googling, I see that others have reported a similar error > and that the problem is seen with 2.0.6 and 2.1 (not with 2.0.2). > > Any pointers appreciated -- Dan Kulp?? > > > > jsolderitsch wrote: > > > > I see the following in my maven console when running a build that uses > > cxf: > > > > Jun 4, 2008 4:41:52 PM > > org.springframework.context.support.AbstractApplicationContext > > prepareRefresh > > INFO: Refreshing [EMAIL PROTECTED]: > > display name [EMAIL PROTECTED]; > > startup date [Wed Jun 04 16:41:52 EDT 2008]; root of context hierarchy > > Jun 4, 2008 4:41:52 PM org.apache.cxf.bus.spring.BusApplicationContext > > getConfigResources > > INFO: No cxf.xml configuration file detected, relying on defaults. > > > > We have a cxf.xml file in a resources folder in our source hierarchy but > > maybe not the right one. > > > > First we build a jar and then package the result up into a war. > > > > The resources folder where we have cxf.xml is in the jar folder. > > > > I am having issues getting security headers to work, and some security > > declarations are in my cxf.xml so I suspect that this INFO text is really > > an error in my case. > > > > Does this look familiar to folks using mvn with cxf. We are using cxf > > 2.0.6 at the moment. > > > > Thanks > > > > Jim > > >
