It's on the client side. The "NewServlet" is a client to the actual web
service.
In the simple front-end case, <property name="address"
value="${xyz.loginServiceAdress}"/> points CXF to the WSDL, and I figure that's
how CXF can auto-generate the stub on the fly behind the scene. In my code
first approach, I don't go through the step of generating binding code from a
WSDL.
In the CXF/Camel case I tried, there is no reference to an actual WSDL, so I
figure that's where the disconnect lies.
Going to try Christian proposal and look into the WSDL first examle to see if I
can modify it to go with a code-first/code-only approach...
Thanks...
--- On Sun, 11/22/09, Willem Jiang <[email protected]> wrote:
> From: Willem Jiang <[email protected]>
> Subject: Re: CXF & Camel & Spring & ActiveMQ Integration Problems
> To: [email protected]
> Date: Sunday, November 22, 2009, 7:34 PM
> Hi,
>
> Did the SEI class is created by using WSDL2Java?
> If so , it must have some @WebService annotation, which let
> you get the
> trouble of WebServiceException.
>
> But from Stack trace I think the error is thrown from the
> service side,
> it have nothing to do with you client configuration.
>
> Can you recheck the configuration on the server side?
>
> Willem
>
> Coder One wrote:
> > Well, the app started, but as soon I invoked the
> function, I got this...
> >
> > SEVERE: Servlet.service() for servlet NewServlet threw
> exception
> > javax.xml.ws.WebServiceException: Could not find
> wsdl:binding operation info for web method
> getMyHelloService
> >
> > Do I absolutely need to have a local WSDL? I
> already got the "interface" classes from the server.
> >
> > I think that's because I use frontend-simple and I
> have no WSDL locally. Here is what I used to just need
> on the client side for another project.
> >
> > <bean
> id="loginServiceAegisDataBinding"
> class="org.apache.cxf.aegis.databinding.AegisDatabinding"/>
> >
> > <bean id="loginService"
> >
> class="abc.xyz.services.loginmgmt.LoginService"
> >
> factory-bean="loginServiceClientFactory"
> factory-method="create"/>
> >
> > <bean
> id="loginServiceClientFactory"
> class="org.apache.cxf.frontend.ClientProxyFactoryBean">
> > <property
> name="serviceClass"
> value="abc.xyz.services.loginmgmt.LoginService"/>
> > <property
> name="address" value="${xyz.loginServiceAdress}"/>
> > <property
> name="dataBinding" ref="loginServiceAegisDataBinding"/>
> > </bean>
> >
> >
> > Thanks,
> >
> > --- On Sat, 11/21/09, Coder One <[email protected]>
> wrote:
> >
> >> From: Coder One <[email protected]>
> >> Subject: Re: CXF & Camel & Spring &
> ActiveMQ Integration Problems
> >> To: [email protected]
> >> Date: Saturday, November 21, 2009, 9:19 AM
> >> You are right. After removing
> >> <context:annotation-config/>", it works. My
> webapp
> >> loaded the wrong spring-context.xml.
> >>
> >> Thanks,
> >>
> >> --- On Sat, 11/21/09, Christian Schneider <[email protected]>
> >> wrote:
> >>
> >>> From: Christian Schneider <[email protected]>
> >>> Subject: Re: CXF & Camel & Spring
> &
> >> ActiveMQ Integration Problems
> >>> To: [email protected]
> >>> Date: Saturday, November 21, 2009, 8:35 AM
> >>> Hmm,
> >>>
> >>> after looking closer at your context there was
> no
> >>> annotation config. But the stacktrace still
> seems to
> >> point
> >>> to the CommonAnnotationBeanPostProcessor. Are
> you sure
> >> the
> >>> context you posted is complete?
> >>> If yes it seems spring is configured in some
> other way
> >> to
> >>> interpret annotations. Are you using junit 4
> tests
> >>> somewhere?
> >>>
> >>> Greetings
> >>>
> >>> Christian
> >>>
> >>>
> >>> Christian Schneider schrieb:
> >>>> Hi,
> >>>>
> >>>> this is probably a bug in camel cxf that I
> found
> >>> recently.
> >>>> https://issues.apache.org/activemq/browse/CAMEL-2112
> >>>>
> >>>> I guess you are using
> >>> <context:annotation-config/> somewhere
> in your
> >>> application context. If you leave this out it
> should
> >> work.
> >>> The bug is fixed in current trunk in
> subversion
> >> already so
> >>> the next camel version should have this fix.
> If you
> >> need a
> >>> quick solution you can check out the camel
> source code
> >> and
> >>> apply the patch from the issue above by hand.
> So you
> >> can
> >>> make your own version that works.
> >>>> Greetings
> >>>>
> >>>> Christian
> >>>>
> >>>>
> >>> --
> >>> Christian Schneider
> >>> ---
> >>> http://www.liquid-reality.de
> >>>
> >>>
> >>
> >>
> >>
> >
> >
> >
> >
>
>
