Hi Scott,
I have not yet used the @Produce style myself. Perhaps there is
something special to configure here. I guess you could ask on the Camel
User list why your one Example worked and the other did not.
I guess cxfrs could really be worth a try.
Btw. Is there any reason why you use seda: instead of direct:? I guess
direct endpoints could be more efficient.
Perhaps there is even a way to avoid CXF at all. You could try to use a
jetty http endpoint and parse the request with jaxb.
At least if jaxb unmarshalling is all you need of rest it could work:
<route>
<from uri="jetty:http://myurl"/>
<unmarshal ref="myJaxb"/>
<to uri="activemq:myqueue"/>
</route>
The following page explains jaxb in Camel:
http://camel.apache.org/jaxb.html
Greetings
Christian
Scott Parkerson schrieb:
On Fri, 2009-09-11 at 15:31 -0400, Scott Parkerson wrote:
Ok, now had I tried your actual suggestion using @EndpointInject things
would have gone more smoothly for me. I changed my code to:
@EndpointInject(uri = "seda:webrequestqueue")
private ProducerTemplate<Exchange> webRequestProducer;
.
.
.
webRequestProducer.sendBody(sendFooRequest);
and all is well.
I guess my only complaint is that this doesn't "hide middleware" as
suggested in the docs. Then again, perhaps I'll eventually come around
to binding a cxfrs: URI to my routes. :D
Any further suggestions?
--sgp
I'm beginning to think I've got the wrong approach to this, but humor me
and tell me how I can just send the Foo object.
--sgp
