You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by jsolderitsch <js...@gestalt-llc.com> on 2008/06/05 18:36:13 UTC
cxf.xml file not being picked up during maven2 processing
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 org.apache.cxf.bus.spring.BusApplicationContext@c943ba:
display name [org.apache.cxf.bus.spring.BusApplicationContext@c943ba];
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
--
View this message in context: http://www.nabble.com/cxf.xml-file-not-being-picked-up-during-maven2-processing-tp17674372p17674372.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: cxf.xml file not being picked up during maven2 processing
Posted by jsolderitsch <ja...@accenture.com>.
Thanks very much!!
This blog posting opened my eyes to the mistakes we were making in our
attempt to generate client and service from the same WSDL.
I have things mostly working now -- the big breakthrough came when I fully
annotated our server Impl file so that the @WebService declaration included
all of: targetNamespace, portName, serviceName, and endpointInterface.
My beans.xml file also needed a reference to the customer wsdl -- it didn't
have one at first.
Part of the problem was the developer who originally wrote this code was
basing some assumptions on his xfire experiences in the past.
In the end, the message about no cxf.xml file being found did not seem to
matter -- it's still there.
Really appreciate the help.
Glen Mazza-2 wrote:
>
> Resending, forgot to include a link...
>
> 2008-06-07 Glen Mazza wrote:
>> 2008-06-07 jsolderitsch wrote:
>> > We are doing both. We have a customer wsdl that we want to create a
>> client
>> > for AND mock up an implementation of the service provider.
>> >
>> > I believe I am seeing the cxf.xml not found error in regard to the
>> client
>> > generation AND I do have the cxf.xml file where you recommend it to be
>> for
>> > SOAP clients. But we are creating both a client as a jar and service
>> > provider as a war from the same parent pom.
>> >
>>
>> The tutorial link I gave you below uses Maven's assembly plugin, so you
>> can take the JAX-WS artifacts generated by the service and reuse them
>> for the client.
>>
>> Alternatively, you can break out the JAX-WS artifacts into a separate
>> module, as here:
>>
>>
>
> http://www.jroller.com/gmazza/date/20071019
>
> ... (much quoting deleted)
>
>
--
View this message in context: http://www.nabble.com/cxf.xml-file-not-being-picked-up-during-maven2-processing-tp17674372p17740292.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: cxf.xml file not being picked up during maven2 processing
Posted by Glen Mazza <gl...@verizon.net>.
Resending, forgot to include a link...
2008-06-07 Glen Mazza wrote:
> 2008-06-07 jsolderitsch wrote:
> > We are doing both. We have a customer wsdl that we want to create a client
> > for AND mock up an implementation of the service provider.
> >
> > I believe I am seeing the cxf.xml not found error in regard to the client
> > generation AND I do have the cxf.xml file where you recommend it to be for
> > SOAP clients. But we are creating both a client as a jar and service
> > provider as a war from the same parent pom.
> >
>
> The tutorial link I gave you below uses Maven's assembly plugin, so you
> can take the JAX-WS artifacts generated by the service and reuse them
> for the client.
>
> Alternatively, you can break out the JAX-WS artifacts into a separate
> module, as here:
>
>
http://www.jroller.com/gmazza/date/20071019
>
> > Another developer started this project and chose the module organization we
> > have in place. It may be that we need to change our strategy to have a
> > separate customization for the client and server.
> >
> > The provider is supposed to be accessed via https so we have some http
> > conduit items our cxf.xml to cover this.
> >
>
> It depends on what you're doing, but for simple SSL you might not need
> the http conduit items in the cxf.xml:
> http://www.jroller.com/gmazza/entry/upcoming_apache_cxf_2_0
>
> >From this, it may follow that you might not even need a cxf.xml at all,
> at least for the SOAP client.
>
> Glen
>
>
>
>
> > Your URL reference will be valuable I am sure in trying to resolve our
> > issue.
> >
> > This gives me something further to go on.
> >
> > Jim
> >
> >
> > Glen Mazza-2 wrote:
> > >
> > > 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.
> > >>
> > > ...
> > >>
> > >> 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
> > >> org.apache.cxf.bus.spring.BusApplicationContext@c943ba:
> > >> > display name [org.apache.cxf.bus.spring.BusApplicationContext@c943ba];
> > >> > 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.
> > >
> > > ...
> > >
> > >> > Jim
> > >> >
> > >>
> > >
> > >
> > >
> >
Re: cxf.xml file not being picked up during maven2 processing
Posted by Glen Mazza <gl...@verizon.net>.
2008-06-07 jsolderitsch wrote:
> We are doing both. We have a customer wsdl that we want to create a client
> for AND mock up an implementation of the service provider.
>
> I believe I am seeing the cxf.xml not found error in regard to the client
> generation AND I do have the cxf.xml file where you recommend it to be for
> SOAP clients. But we are creating both a client as a jar and service
> provider as a war from the same parent pom.
>
The tutorial link I gave you below uses Maven's assembly plugin, so you
can take the JAX-WS artifacts generated by the service and reuse them
for the client.
Alternatively, you can break out the JAX-WS artifacts into a separate
module, as here:
> Another developer started this project and chose the module organization we
> have in place. It may be that we need to change our strategy to have a
> separate customization for the client and server.
>
> The provider is supposed to be accessed via https so we have some http
> conduit items our cxf.xml to cover this.
>
It depends on what you're doing, but for simple SSL you might not need
the http conduit items in the cxf.xml:
http://www.jroller.com/gmazza/entry/upcoming_apache_cxf_2_0
>>From this, it may follow that you might not even need a cxf.xml at all,
at least for the SOAP client.
Glen
> Your URL reference will be valuable I am sure in trying to resolve our
> issue.
>
> This gives me something further to go on.
>
> Jim
>
>
> Glen Mazza-2 wrote:
> >
> > 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.
> >>
> > ...
> >>
> >> 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
> >> org.apache.cxf.bus.spring.BusApplicationContext@c943ba:
> >> > display name [org.apache.cxf.bus.spring.BusApplicationContext@c943ba];
> >> > 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.
> >
> > ...
> >
> >> > Jim
> >> >
> >>
> >
> >
> >
>
Re: cxf.xml file not being picked up during maven2 processing
Posted by jsolderitsch <ja...@accenture.com>.
We are doing both. We have a customer wsdl that we want to create a client
for AND mock up an implementation of the service provider.
I believe I am seeing the cxf.xml not found error in regard to the client
generation AND I do have the cxf.xml file where you recommend it to be for
SOAP clients. But we are creating both a client as a jar and service
provider as a war from the same parent pom.
Another developer started this project and chose the module organization we
have in place. It may be that we need to change our strategy to have a
separate customization for the client and server.
The provider is supposed to be accessed via https so we have some http
conduit items our cxf.xml to cover this.
Your URL reference will be valuable I am sure in trying to resolve our
issue.
This gives me something further to go on.
Jim
Glen Mazza-2 wrote:
>
> 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.
>>
> ...
>>
>> 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
>> org.apache.cxf.bus.spring.BusApplicationContext@c943ba:
>> > display name [org.apache.cxf.bus.spring.BusApplicationContext@c943ba];
>> > 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.
>
> ...
>
>> > Jim
>> >
>>
>
>
>
--
View this message in context: http://www.nabble.com/cxf.xml-file-not-being-picked-up-during-maven2-processing-tp17674372p17710699.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: cxf.xml file not being picked up during maven2 processing
Posted by Glen Mazza <gl...@verizon.net>.
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 org.apache.cxf.bus.spring.BusApplicationContext@c943ba:
> > display name [org.apache.cxf.bus.spring.BusApplicationContext@c943ba];
> > 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
> >
>
Re: cxf.xml file not being picked up during maven2 processing
Posted by jsolderitsch <ja...@accenture.com>.
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 org.apache.cxf.bus.spring.BusApplicationContext@c943ba:
> display name [org.apache.cxf.bus.spring.BusApplicationContext@c943ba];
> 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
>
--
View this message in context: http://www.nabble.com/cxf.xml-file-not-being-picked-up-during-maven2-processing-tp17674372p17704150.html
Sent from the cxf-user mailing list archive at Nabble.com.