That makes sense! :-)
A web service endpoint implementation here is useless.
Thank you!
________________________________
Betreff: Re: Web Service Consumer Route: service class implementation vs.
exchange.getOut().setBody("")
camel-cxf consumer just route the request (or the invocation message ) to the
camel route, we don't want to handle the request in the implementation there.
If you want to use the implementation to handle the request, you can just use
CXF directly.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Thursday, December 13, 2012 at 7:31 PM, Hildegard Schedthelm wrote:
> Hello folks!
>
> As I have started to build up a web service by a web service consumer route I
> had difficulties to grasp how to accommodate the web service implementation
> to this approach.
> Now I have figured out that the web service response is done by
>
> exchange.getOut().setBody("RESPONSE");
>
> in any processor or bean the route has configured.
>
>
> But what about the serviceClass I have configured for the cxf endpoint?
> Actually there
> is already an implementation but ignored because what matters is what
> happens
>
> inside the route.
>
> from("cxf://http://localhost:9090/OrderEndpointPort?serviceClass=camel.testcamel.OrderEndpointImpl";)
>
> package camel.testcamel;
>
>
> @WebService(endpointInterface = "camel.testcamel.OrderEndpoint", serviceName
> = "OrderEndpointService")
> public class OrderEndpointImpl implements OrderEndpoint {
>
> @Override
> public String order(String partName, int amount, String customerName) {
> return "" + amount;
> }
>
> }
>
>
> I am a little bit confused about the implementation bypass but ask you to give
> me a confirmation that this is the proper approach camel intended.
>
> Cheers
> Hilde
