You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by narend <na...@gmail.com> on 2007/10/16 19:46:40 UTC
Simple FrontEnd CXF deployment error
Hi all
I was able to get the standalone Simple FrontEnd HelloWorld to work. Now I
would like to deploy it as a war . I followed the instructions from the CXF
User guide on setting up a CXFServlet & I get the below error. Supporting
Artifacts are included below (cxf-servlet.xml & web.xml)
I'm not familiar with Spring and I'm trying the HelloWorld example. The
error seems to be because I'm missing some definition in spring? Has anyone
else had success with Simple FrontEnd deployment.. I really like the ease of
setting up services with it. Would appreciate any thoughts on this one..
Thanks!
http://www.nabble.com/file/p13238695/cxf-servlet.xml cxf-servlet.xml
http://www.nabble.com/file/p13238695/web.xml web.xml
12:35:17,556 ERROR [STDERR] ::: Oct 16, 2007 12:35:17 PM
org.apache.cxf.bus.spring.SpringBusFactory createBus
WARNING: Failed to create application context.
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean
named 'cxf' is defined
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:345)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getMergedBeanDefinition(AbstractBeanFactory.java:894)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:243)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:229)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
at
org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:703)
at
org.apache.cxf.bus.spring.SpringBusFactory.finishCreatingBus(SpringBusFactory.java:69)
at
org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:84)
at
org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:65)
at
org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:52)
at
org.apache.cxf.transport.servlet.CXFServlet.loadSpringBus(CXFServlet.java:159)
at
org.apache.cxf.transport.servlet.CXFServlet.init(CXFServlet.java:98)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
--
View this message in context: http://www.nabble.com/Simple-FrontEnd-CXF-deployment-error-tf4635682.html#a13238695
Sent from the cxf-user mailing list archive at Nabble.com.
RE: simple-frontend.html
Posted by Benson Margulies <bi...@basistech.com>.
The 'nice idea' is fine if you understand the constraints. The two ends
have to come up with the same answer for the hidden internal model of
the service. If this is your situation, my suggestion is to avoid
interfaces and stick with classes in terms of communicating with CXF or
any similar toolkit.
> -----Original Message-----
> From: Jonathan Slate [mailto:jslate@mtl.mit.edu]
> Sent: Wednesday, October 17, 2007 9:04 AM
> To: cxf-user@incubator.apache.org
> Subject: Re: simple-frontend.html
>
> Ok, now I think I understand the crux of the issue. As it's working
for
> me now, I have to wonder... should I change it or go ahead with the
old
> "if it ain't broke don't fix it?" No need to answer, rhetorical
> question. :)
>
> It is a nice idea that you can setup your services/clients using CXF
and
> not worry about all the hairy details, requiring that the client use
the
> WSDL seems to interfere with that goal a bit, but as the WSDL is the
> real contract I guess it will be hard to guarantee that the server and
> client will match up when building both off of the interface. So maybe
> it's unavoidable.
>
> Anyway, thanks for the "gut feeling" explanation, we can now make an
> intelligent choice on how to handle this, I hope. :)
>
> -Jonathan
>
> Benson Margulies wrote:
> > My opinion is that using the Simple front end with an interface (as
> > opposed to a WSDL) is a gun pointed firmly at the user's foot, and
we
> > should prohibit it.
> >
> > Jonathan, I can't prove it today, but my gut feeling is that you are
> > still experiencing the client constructing a different contract than
the
> > server is using. Consuming the WSDL is the only really reliable way
to
> > get them in sync. At least, I'd suggest trying the WSDL-consumption
> > alternative and see if it works, and we can go from there.
> >
> >
> >> -----Original Message-----
> >> From: Jonathan Slate [mailto:jslate@mtl.mit.edu]
> >> Sent: Wednesday, October 17, 2007 8:26 AM
> >> To: cxf-user@incubator.apache.org
> >> Subject: Re: simple-frontend.html
> >>
> >> Thanks Jeff for making this change, it's certainly more visible.
> >> However, I'm not sure that this is the same problem. The JIRA talks
> >> about the argument name being wrong (arg0 vs. title) but in my
case,
> >>
> > the
> >
> >> argument is arg0 and it worked fine w/out changing that. The
problem
> >>
> > was
> >
> >> the xmlns="http://example.hello/" argument appearing in the
argument's
> >>
> > tag.
> >
> >> I don't think someone would figure out from looking at the JIRA
that
> >> they should use JaxWsProxyFactoryBean to avoid this problem. Or
maybe
> >>
> > it
> >
> >> *should* work with ClientProxyFactoryBean as documented and I'm
doing
> >> something wrong, which would be nice to know. But I think it's ok,
> >> because that's what the Spring client example uses...
> >>
> >> -Jonathan
> >>
> >> Jeff Yu wrote:
> >>
> >>> At the bottom of simple-frontend.html, there is a tip talked about
> >>> this, see this JIRA for detail:
> >>> https://issues.apache.org/jira/browse/CXF-897
> >>>
> >>> I updated it "Others" title to "Well-Known issue" for easily to
get
> >>> people's attention.
> >>>
> >>> Thanks
> >>> Jeff
> >>>
> >>> Jonathan Slate wrote:
> >>>
> >>>> Just wanted to ask about an issue I had and a possible problem
with
> >>>> the documentation on the Web site.
> >>>>
> >>>> In trying to learn CXF, I created a HelloWorld service using
Spring
> >>>>
> > ,
> >
> >>>> following the instructions on this page:
> >>>>
http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
> >>>>
> >>>> I then created a separate client application (not using Spring)
> >>>>
> > using
> >
> >>>> the instructions on this page:
> >>>> http://cwiki.apache.org/CXF20DOC/simple-frontend.html (under
> >>>>
> > heading
> >
> >>>> ClientProxyFactoryBean)
> >>>>
> >>>> This did not work, the "text" argument was null when the sayHi
> >>>>
> > method
> >
> >>>> was called. So I set up a Spring client following the
instructions
> >>>>
> > on
> >
> >>>> the first page mentioned above. That worked. Eventually I figured
> >>>>
> > out
> >
> >>>> that the Spring example had me creating a new
JaxWsProxyFactoryBean
> >>>> whereas the simple frontend example had me creating a new
> >>>> ClientProxyFactoryBean. This resulted in slightly different SOAP
> >>>> calls, specifically in the "arg0" tag:
> >>>>
> >>>> <arg0 xmlns="http://example.hello/">World</arg0>
> >>>> (ClientProxyFactoryBean)
> >>>> <arg0>World</arg0> (JaxWsProxyFactoryBean)
> >>>>
> >>>> For some reason, the former causes the method to be called with
> >>>>
> > arg0
> >
> >>>> as null. Also, with the ClientProxyFactoryBean, the result
returned
> >>>> to the client is null, despite the fact that the soap message
> >>>> contains the return value "Hello null."
> >>>>
> >>>> Anyway, at this point it's working for me. But I'm wondering if
> >>>>
> > there
> >
> >>>> is a simple explaination for this, and if perhaps the simple
> >>>>
> > frontend
> >
> >>>> documentation should be updated to use JaxWsProxyFactoryBean.
> >>>>
> >>>> Thanks,
> >>>> Jonathan Slate
> >>>>
> >>>>
> >>>>
> >
> >
Re: simple-frontend.html
Posted by Jonathan Slate <js...@mtl.mit.edu>.
Ok, now I think I understand the crux of the issue. As it's working for
me now, I have to wonder... should I change it or go ahead with the old
"if it ain't broke don't fix it?" No need to answer, rhetorical question. :)
It is a nice idea that you can setup your services/clients using CXF and
not worry about all the hairy details, requiring that the client use the
WSDL seems to interfere with that goal a bit, but as the WSDL is the
real contract I guess it will be hard to guarantee that the server and
client will match up when building both off of the interface. So maybe
it's unavoidable.
Anyway, thanks for the "gut feeling" explanation, we can now make an
intelligent choice on how to handle this, I hope. :)
-Jonathan
Benson Margulies wrote:
> My opinion is that using the Simple front end with an interface (as
> opposed to a WSDL) is a gun pointed firmly at the user's foot, and we
> should prohibit it.
>
> Jonathan, I can't prove it today, but my gut feeling is that you are
> still experiencing the client constructing a different contract than the
> server is using. Consuming the WSDL is the only really reliable way to
> get them in sync. At least, I'd suggest trying the WSDL-consumption
> alternative and see if it works, and we can go from there.
>
>
>> -----Original Message-----
>> From: Jonathan Slate [mailto:jslate@mtl.mit.edu]
>> Sent: Wednesday, October 17, 2007 8:26 AM
>> To: cxf-user@incubator.apache.org
>> Subject: Re: simple-frontend.html
>>
>> Thanks Jeff for making this change, it's certainly more visible.
>> However, I'm not sure that this is the same problem. The JIRA talks
>> about the argument name being wrong (arg0 vs. title) but in my case,
>>
> the
>
>> argument is arg0 and it worked fine w/out changing that. The problem
>>
> was
>
>> the xmlns="http://example.hello/" argument appearing in the argument's
>>
> tag.
>
>> I don't think someone would figure out from looking at the JIRA that
>> they should use JaxWsProxyFactoryBean to avoid this problem. Or maybe
>>
> it
>
>> *should* work with ClientProxyFactoryBean as documented and I'm doing
>> something wrong, which would be nice to know. But I think it's ok,
>> because that's what the Spring client example uses...
>>
>> -Jonathan
>>
>> Jeff Yu wrote:
>>
>>> At the bottom of simple-frontend.html, there is a tip talked about
>>> this, see this JIRA for detail:
>>> https://issues.apache.org/jira/browse/CXF-897
>>>
>>> I updated it "Others" title to "Well-Known issue" for easily to get
>>> people's attention.
>>>
>>> Thanks
>>> Jeff
>>>
>>> Jonathan Slate wrote:
>>>
>>>> Just wanted to ask about an issue I had and a possible problem with
>>>> the documentation on the Web site.
>>>>
>>>> In trying to learn CXF, I created a HelloWorld service using Spring
>>>>
> ,
>
>>>> following the instructions on this page:
>>>> http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
>>>>
>>>> I then created a separate client application (not using Spring)
>>>>
> using
>
>>>> the instructions on this page:
>>>> http://cwiki.apache.org/CXF20DOC/simple-frontend.html (under
>>>>
> heading
>
>>>> ClientProxyFactoryBean)
>>>>
>>>> This did not work, the "text" argument was null when the sayHi
>>>>
> method
>
>>>> was called. So I set up a Spring client following the instructions
>>>>
> on
>
>>>> the first page mentioned above. That worked. Eventually I figured
>>>>
> out
>
>>>> that the Spring example had me creating a new JaxWsProxyFactoryBean
>>>> whereas the simple frontend example had me creating a new
>>>> ClientProxyFactoryBean. This resulted in slightly different SOAP
>>>> calls, specifically in the "arg0" tag:
>>>>
>>>> <arg0 xmlns="http://example.hello/">World</arg0>
>>>> (ClientProxyFactoryBean)
>>>> <arg0>World</arg0> (JaxWsProxyFactoryBean)
>>>>
>>>> For some reason, the former causes the method to be called with
>>>>
> arg0
>
>>>> as null. Also, with the ClientProxyFactoryBean, the result returned
>>>> to the client is null, despite the fact that the soap message
>>>> contains the return value "Hello null."
>>>>
>>>> Anyway, at this point it's working for me. But I'm wondering if
>>>>
> there
>
>>>> is a simple explaination for this, and if perhaps the simple
>>>>
> frontend
>
>>>> documentation should be updated to use JaxWsProxyFactoryBean.
>>>>
>>>> Thanks,
>>>> Jonathan Slate
>>>>
>>>>
>>>>
>
>
RE: simple-frontend.html
Posted by Benson Margulies <bi...@basistech.com>.
My opinion is that using the Simple front end with an interface (as
opposed to a WSDL) is a gun pointed firmly at the user's foot, and we
should prohibit it.
Jonathan, I can't prove it today, but my gut feeling is that you are
still experiencing the client constructing a different contract than the
server is using. Consuming the WSDL is the only really reliable way to
get them in sync. At least, I'd suggest trying the WSDL-consumption
alternative and see if it works, and we can go from there.
> -----Original Message-----
> From: Jonathan Slate [mailto:jslate@mtl.mit.edu]
> Sent: Wednesday, October 17, 2007 8:26 AM
> To: cxf-user@incubator.apache.org
> Subject: Re: simple-frontend.html
>
> Thanks Jeff for making this change, it's certainly more visible.
> However, I'm not sure that this is the same problem. The JIRA talks
> about the argument name being wrong (arg0 vs. title) but in my case,
the
> argument is arg0 and it worked fine w/out changing that. The problem
was
> the xmlns="http://example.hello/" argument appearing in the argument's
tag.
>
> I don't think someone would figure out from looking at the JIRA that
> they should use JaxWsProxyFactoryBean to avoid this problem. Or maybe
it
> *should* work with ClientProxyFactoryBean as documented and I'm doing
> something wrong, which would be nice to know. But I think it's ok,
> because that's what the Spring client example uses...
>
> -Jonathan
>
> Jeff Yu wrote:
> > At the bottom of simple-frontend.html, there is a tip talked about
> > this, see this JIRA for detail:
> > https://issues.apache.org/jira/browse/CXF-897
> >
> > I updated it "Others" title to "Well-Known issue" for easily to get
> > people's attention.
> >
> > Thanks
> > Jeff
> >
> > Jonathan Slate wrote:
> >> Just wanted to ask about an issue I had and a possible problem with
> >> the documentation on the Web site.
> >>
> >> In trying to learn CXF, I created a HelloWorld service using Spring
,
> >> following the instructions on this page:
> >> http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
> >>
> >> I then created a separate client application (not using Spring)
using
> >> the instructions on this page:
> >> http://cwiki.apache.org/CXF20DOC/simple-frontend.html (under
heading
> >> ClientProxyFactoryBean)
> >>
> >> This did not work, the "text" argument was null when the sayHi
method
> >> was called. So I set up a Spring client following the instructions
on
> >> the first page mentioned above. That worked. Eventually I figured
out
> >> that the Spring example had me creating a new JaxWsProxyFactoryBean
> >> whereas the simple frontend example had me creating a new
> >> ClientProxyFactoryBean. This resulted in slightly different SOAP
> >> calls, specifically in the "arg0" tag:
> >>
> >> <arg0 xmlns="http://example.hello/">World</arg0>
> >> (ClientProxyFactoryBean)
> >> <arg0>World</arg0> (JaxWsProxyFactoryBean)
> >>
> >> For some reason, the former causes the method to be called with
arg0
> >> as null. Also, with the ClientProxyFactoryBean, the result returned
> >> to the client is null, despite the fact that the soap message
> >> contains the return value "Hello null."
> >>
> >> Anyway, at this point it's working for me. But I'm wondering if
there
> >> is a simple explaination for this, and if perhaps the simple
frontend
> >> documentation should be updated to use JaxWsProxyFactoryBean.
> >>
> >> Thanks,
> >> Jonathan Slate
> >>
> >>
Re: simple-frontend.html
Posted by Jeff Yu <je...@iona.com>.
Oops... My bad, I didn't read it carefully. ;-), but I havent seen this
case before, I will try it to see if I can have this problem as you did
as soon as I get a chance.
Thanks
Jeff
Jonathan Slate wrote:
> Thanks Jeff for making this change, it's certainly more visible.
> However, I'm not sure that this is the same problem. The JIRA talks
> about the argument name being wrong (arg0 vs. title) but in my case,
> the argument is arg0 and it worked fine w/out changing that. The
> problem was the xmlns="http://example.hello/" argument appearing in
> the argument's tag.
>
> I don't think someone would figure out from looking at the JIRA that
> they should use JaxWsProxyFactoryBean to avoid this problem. Or maybe
> it *should* work with ClientProxyFactoryBean as documented and I'm
> doing something wrong, which would be nice to know. But I think it's
> ok, because that's what the Spring client example uses...
>
> -Jonathan
>
> Jeff Yu wrote:
>> At the bottom of simple-frontend.html, there is a tip talked about
>> this, see this JIRA for detail:
>> https://issues.apache.org/jira/browse/CXF-897
>>
>> I updated it "Others" title to "Well-Known issue" for easily to get
>> people's attention.
>>
>> Thanks
>> Jeff
>>
>> Jonathan Slate wrote:
>>> Just wanted to ask about an issue I had and a possible problem with
>>> the documentation on the Web site.
>>>
>>> In trying to learn CXF, I created a HelloWorld service using Spring
>>> , following the instructions on this page:
>>> http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
>>>
>>> I then created a separate client application (not using Spring)
>>> using the instructions on this page:
>>> http://cwiki.apache.org/CXF20DOC/simple-frontend.html (under heading
>>> ClientProxyFactoryBean)
>>>
>>> This did not work, the "text" argument was null when the sayHi
>>> method was called. So I set up a Spring client following the
>>> instructions on the first page mentioned above. That worked.
>>> Eventually I figured out that the Spring example had me creating a
>>> new JaxWsProxyFactoryBean whereas the simple frontend example had me
>>> creating a new ClientProxyFactoryBean. This resulted in slightly
>>> different SOAP calls, specifically in the "arg0" tag:
>>>
>>> <arg0 xmlns="http://example.hello/">World</arg0>
>>> (ClientProxyFactoryBean)
>>> <arg0>World</arg0> (JaxWsProxyFactoryBean)
>>>
>>> For some reason, the former causes the method to be called with arg0
>>> as null. Also, with the ClientProxyFactoryBean, the result returned
>>> to the client is null, despite the fact that the soap message
>>> contains the return value "Hello null."
>>>
>>> Anyway, at this point it's working for me. But I'm wondering if
>>> there is a simple explaination for this, and if perhaps the simple
>>> frontend documentation should be updated to use JaxWsProxyFactoryBean.
>>>
>>> Thanks,
>>> Jonathan Slate
>>>
>>>
>
Re: simple-frontend.html
Posted by Jonathan Slate <js...@mtl.mit.edu>.
Thanks Jeff for making this change, it's certainly more visible.
However, I'm not sure that this is the same problem. The JIRA talks
about the argument name being wrong (arg0 vs. title) but in my case, the
argument is arg0 and it worked fine w/out changing that. The problem was
the xmlns="http://example.hello/" argument appearing in the argument's tag.
I don't think someone would figure out from looking at the JIRA that
they should use JaxWsProxyFactoryBean to avoid this problem. Or maybe it
*should* work with ClientProxyFactoryBean as documented and I'm doing
something wrong, which would be nice to know. But I think it's ok,
because that's what the Spring client example uses...
-Jonathan
Jeff Yu wrote:
> At the bottom of simple-frontend.html, there is a tip talked about
> this, see this JIRA for detail:
> https://issues.apache.org/jira/browse/CXF-897
>
> I updated it "Others" title to "Well-Known issue" for easily to get
> people's attention.
>
> Thanks
> Jeff
>
> Jonathan Slate wrote:
>> Just wanted to ask about an issue I had and a possible problem with
>> the documentation on the Web site.
>>
>> In trying to learn CXF, I created a HelloWorld service using Spring ,
>> following the instructions on this page:
>> http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
>>
>> I then created a separate client application (not using Spring) using
>> the instructions on this page:
>> http://cwiki.apache.org/CXF20DOC/simple-frontend.html (under heading
>> ClientProxyFactoryBean)
>>
>> This did not work, the "text" argument was null when the sayHi method
>> was called. So I set up a Spring client following the instructions on
>> the first page mentioned above. That worked. Eventually I figured out
>> that the Spring example had me creating a new JaxWsProxyFactoryBean
>> whereas the simple frontend example had me creating a new
>> ClientProxyFactoryBean. This resulted in slightly different SOAP
>> calls, specifically in the "arg0" tag:
>>
>> <arg0 xmlns="http://example.hello/">World</arg0>
>> (ClientProxyFactoryBean)
>> <arg0>World</arg0> (JaxWsProxyFactoryBean)
>>
>> For some reason, the former causes the method to be called with arg0
>> as null. Also, with the ClientProxyFactoryBean, the result returned
>> to the client is null, despite the fact that the soap message
>> contains the return value "Hello null."
>>
>> Anyway, at this point it's working for me. But I'm wondering if there
>> is a simple explaination for this, and if perhaps the simple frontend
>> documentation should be updated to use JaxWsProxyFactoryBean.
>>
>> Thanks,
>> Jonathan Slate
>>
>>
Re: simple-frontend.html
Posted by Jeff Yu <je...@iona.com>.
At the bottom of simple-frontend.html, there is a tip talked about this,
see this JIRA for detail: https://issues.apache.org/jira/browse/CXF-897
I updated it "Others" title to "Well-Known issue" for easily to get
people's attention.
Thanks
Jeff
Jonathan Slate wrote:
> Just wanted to ask about an issue I had and a possible problem with
> the documentation on the Web site.
>
> In trying to learn CXF, I created a HelloWorld service using Spring ,
> following the instructions on this page:
> http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
>
> I then created a separate client application (not using Spring) using
> the instructions on this page:
> http://cwiki.apache.org/CXF20DOC/simple-frontend.html (under heading
> ClientProxyFactoryBean)
>
> This did not work, the "text" argument was null when the sayHi method
> was called. So I set up a Spring client following the instructions on
> the first page mentioned above. That worked. Eventually I figured out
> that the Spring example had me creating a new JaxWsProxyFactoryBean
> whereas the simple frontend example had me creating a new
> ClientProxyFactoryBean. This resulted in slightly different SOAP
> calls, specifically in the "arg0" tag:
>
> <arg0 xmlns="http://example.hello/">World</arg0>
> (ClientProxyFactoryBean)
> <arg0>World</arg0> (JaxWsProxyFactoryBean)
>
> For some reason, the former causes the method to be called with arg0
> as null. Also, with the ClientProxyFactoryBean, the result returned to
> the client is null, despite the fact that the soap message contains
> the return value "Hello null."
>
> Anyway, at this point it's working for me. But I'm wondering if there
> is a simple explaination for this, and if perhaps the simple frontend
> documentation should be updated to use JaxWsProxyFactoryBean.
>
> Thanks,
> Jonathan Slate
>
>
simple-frontend.html
Posted by Jonathan Slate <js...@mtl.mit.edu>.
Just wanted to ask about an issue I had and a possible problem with the
documentation on the Web site.
In trying to learn CXF, I created a HelloWorld service using Spring ,
following the instructions on this page:
http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
I then created a separate client application (not using Spring) using
the instructions on this page:
http://cwiki.apache.org/CXF20DOC/simple-frontend.html (under heading
ClientProxyFactoryBean)
This did not work, the "text" argument was null when the sayHi method
was called. So I set up a Spring client following the instructions on
the first page mentioned above. That worked. Eventually I figured out
that the Spring example had me creating a new JaxWsProxyFactoryBean
whereas the simple frontend example had me creating a new
ClientProxyFactoryBean. This resulted in slightly different SOAP calls,
specifically in the "arg0" tag:
<arg0 xmlns="http://example.hello/">World</arg0> (ClientProxyFactoryBean)
<arg0>World</arg0> (JaxWsProxyFactoryBean)
For some reason, the former causes the method to be called with arg0 as
null. Also, with the ClientProxyFactoryBean, the result returned to the
client is null, despite the fact that the soap message contains the
return value "Hello null."
Anyway, at this point it's working for me. But I'm wondering if there is
a simple explaination for this, and if perhaps the simple frontend
documentation should be updated to use JaxWsProxyFactoryBean.
Thanks,
Jonathan Slate
Re: Simple FrontEnd CXF deployment error
Posted by narend <na...@gmail.com>.
Quick update so that it benefits others struggling with the issue
I was able to include the CXFServlet in web.xml to get the SimpleFrontEnd
working. The one change I did was to rename the cxf-servlet.xml to
services.xml(any name will do).... looks like I was mis-led by the simple
front end tutorial that asked me to create a cxf-servlet.xml or I
misunderstood how the CXFServlet & ContextLoader worked.
But anyways now I'm able to get the Simple front end working inside a
container with no need to specify different ports for different services..
find my config below
http://www.nabble.com/file/p13254128/services.xml services.xml
http://www.nabble.com/file/p13254128/web.xml web.xml
narend wrote:
>
> All!
> I was able to resolve this with the help of a co-worker's suggestion. I
> just removed the CXFServlet and it works for me...
> I'm going to try this out on a more complex real-world example to see if I
> got this correct.
>
>
> narend wrote:
>>
>> Hi all
>> I was able to get the standalone Simple FrontEnd HelloWorld to work. Now
>> I would like to deploy it as a war . I followed the instructions from
>> the CXF User guide on setting up a CXFServlet & I get the below error.
>> Supporting Artifacts are included below (cxf-servlet.xml & web.xml)
>> I'm not familiar with Spring and I'm trying the HelloWorld example. The
>> error seems to be because I'm missing some definition in spring? Has
>> anyone else had success with Simple FrontEnd deployment.. I really like
>> the ease of setting up services with it. Would appreciate any thoughts on
>> this one..
>> Thanks!
>>
>> http://www.nabble.com/file/p13238695/cxf-servlet.xml cxf-servlet.xml
>> http://www.nabble.com/file/p13238695/web.xml web.xml
>>
>> 12:35:17,556 ERROR [STDERR] ::: Oct 16, 2007 12:35:17 PM
>> org.apache.cxf.bus.spring.SpringBusFactory createBus
>> WARNING: Failed to create application context.
>> org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean
>> named 'cxf' is defined
>> at
>> org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:345)
>> at
>> org.springframework.beans.factory.support.AbstractBeanFactory.getMergedBeanDefinition(AbstractBeanFactory.java:894)
>> at
>> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:243)
>> at
>> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:229)
>> at
>> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
>> at
>> org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:703)
>> at
>> org.apache.cxf.bus.spring.SpringBusFactory.finishCreatingBus(SpringBusFactory.java:69)
>> at
>> org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:84)
>> at
>> org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:65)
>> at
>> org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:52)
>> at
>> org.apache.cxf.transport.servlet.CXFServlet.loadSpringBus(CXFServlet.java:159)
>> at
>> org.apache.cxf.transport.servlet.CXFServlet.init(CXFServlet.java:98)
>> at
>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
>>
>
>
--
View this message in context: http://www.nabble.com/Simple-FrontEnd-CXF-deployment-error-tf4635682.html#a13254128
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Simple FrontEnd CXF deployment error
Posted by narend <na...@gmail.com>.
All!
I was able to resolve this with the help of a co-worker's suggestion. I just
removed the CXFServlet and it works for me...
I'm going to try this out on a more complex real-world example to see if I
got this correct.
narend wrote:
>
> Hi all
> I was able to get the standalone Simple FrontEnd HelloWorld to work. Now I
> would like to deploy it as a war . I followed the instructions from the
> CXF User guide on setting up a CXFServlet & I get the below error.
> Supporting Artifacts are included below (cxf-servlet.xml & web.xml)
> I'm not familiar with Spring and I'm trying the HelloWorld example. The
> error seems to be because I'm missing some definition in spring? Has
> anyone else had success with Simple FrontEnd deployment.. I really like
> the ease of setting up services with it. Would appreciate any thoughts on
> this one..
> Thanks!
>
> http://www.nabble.com/file/p13238695/cxf-servlet.xml cxf-servlet.xml
> http://www.nabble.com/file/p13238695/web.xml web.xml
>
> 12:35:17,556 ERROR [STDERR] ::: Oct 16, 2007 12:35:17 PM
> org.apache.cxf.bus.spring.SpringBusFactory createBus
> WARNING: Failed to create application context.
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean
> named 'cxf' is defined
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:345)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getMergedBeanDefinition(AbstractBeanFactory.java:894)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:243)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:229)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
> at
> org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:703)
> at
> org.apache.cxf.bus.spring.SpringBusFactory.finishCreatingBus(SpringBusFactory.java:69)
> at
> org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:84)
> at
> org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:65)
> at
> org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:52)
> at
> org.apache.cxf.transport.servlet.CXFServlet.loadSpringBus(CXFServlet.java:159)
> at
> org.apache.cxf.transport.servlet.CXFServlet.init(CXFServlet.java:98)
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
>
--
View this message in context: http://www.nabble.com/Simple-FrontEnd-CXF-deployment-error-tf4635682.html#a13238997
Sent from the cxf-user mailing list archive at Nabble.com.