Thanks Jiang,
I understand why control should not go to service impl. But now my concern
is why we need to write the impl class at all. As in below example I have
create a web service called FeatureService, and in cxf:rsServer tag's
serviceClass attribute we need to pass the above FeatureService's
Hi,
a CXF RS Blueprint extension is available (resourceClass attribute) that
can be used to have only the interface supporting the endpoint, I did
not use it but Yuhan showed it to me and it looked very cool
Cheers, Sergey
On 29/09/14 08:15, vrahul wrote:
Thanks Jiang,
I understand why
This became a code quality concern for us. Can you please explain that why
cxf-rs server bean implementation behave is different with camel. is there
any way i can implement cxf-rs services the same way as it is.
--
View this message in context:
camel-cxfrs consumer just need to route the message into camel route, if the
implementation method is called, the camel route cannot process the request
message any more.
If you just want to call the implementation class’s method, you can use cxf-rs
directly.
--
Willem Jiang
Red Hat, Inc.
Hi
It is not possible to use jaxrs:server in combination with cxfrs, it is
only possible to do
jaxrs:server id=userManagerREST address=camel:/route
/jaxrs:server
and then direct to from the camel route typically starting from a
servlet. This approach is somewhat limited unless one is
Willem pointed earlier on to the possibility of using ProducerTemplate.
I saw the example somewhere today of using the native CXF JAX-WS
declarations with the endpoint implementations additionally being
injected with CamelContext - getting ProducerTemplate and invoking on
the route - the same
It could be more easy if we just use the SimpleConsumer binding which can let
us deal with REST message in a simple generic way in Camel route. Please check
out Simple Binding Style[1] page for more information.
