CXFRS with interface and passthrough

[sysgen]

I'm having trouble trying to create a route where in inbound request comes into CXFRS, the body is passed on to a processor that creates SQL and that is fed to the JDBC component before being transformed and returned to the client

The client uses an interface like this:

@Path("search")

public interface SearchClient {

     @GET

     @Path("insuredAdditionalNameYOA")

     @Produces("application/xml")

     List

[davsclaus]

What version of Camel and CXF are you using?

[sysgen]

4.3.0-fuse-03

[davsclaus]

I would assume CXF-RS would be able to handle marshaling/unmarshal automatic. So all you have to do is to code as if it was java code.

The return type of the operation is List instance containing the response.

Then you dont need the xstream at all.

[davsclaus]

And yeah I think it would be nice if JAX-RS would accept an annotated interface instead of a class.

You can create a JIRA ticket at Apache Camel for this enhancement

http://issues.apache.org/jira/browse/CAMEL

[davsclaus]

We are having a number of webinars on using CXF so you may be interested to attend those.

http://fusesource.com/resources/video-archived-webinars/

The webinars will be recorded and avail for viewing later.

[sysgen]

What I dont understand is how a concrete class at this point would look and function.

Each method on the class requires a return type of List JAX-RS response)  ???

[davsclaus]

To store in the database its much easier to use SpringJdbcTemplate in Java code. That allows you to provide the SQL and bind the parameters.

But using the camel jdbc or sql component is also applicable. However you need to transform the message body beforehand.

So instead you can just do

from

  process(new MyDatabaseProcessor())

  process(new MyResponseProcessor())

And then use a Camel Processor to leverage the Spring JdbcTemplate

And the last Camel processor to set the response.

Instead of using a Camel processor you can use beans if you prefer that.

http://camel.apache.org/bean-binding.html

Chapter 3 and 4 in the Camel book covers this in much more depth.