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 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
implementation.
<cxf:rsServer id="featureServiceServer"
address="http://{{esb.feature.service.host}}:{{esb.feature.service.port}}/featureService";
serviceClass="com.test.esb.service.flm.FeatureServiceImpl"
loggingSizeLimit="30" >
<cxf:providers>
<bean class="org.codehaus.jackson.jaxrs.JacksonJsonProvider"/>
</cxf:providers>
</cxf:rsServer>
Where FeatureServiceImpl implements the FeatureSerivce(Rest service)
interface. Is it possible to omit the need of FeatureServiceImpl when we use
cxf with camel. Please share your thoughts on this.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-Jaxrs-service-implementation-class-s-methods-are-not-executing-tp5749733p5757174.html
Sent from the Camel - Users mailing list archive at Nabble.com.
