I am not still sure what you mean by using the dispatch API in camel.
Willem already answered to your question and I am adding a few info.
The actual dispatching part (i.e., sending out a generic message) is
there in Camel. The message constructing part isn't there because in
camel, you
Hi ,
Could you please elaborate a bit more about the Camel CXF endpoint.
We dont want to use the spring based configuration as we are evaluating this
for our product
The same reason we have used CXF For e.g.
For Ws-Addressing we are using the dispatch api as follows
import static
Current camel-cxf doesn’t support the dispatch API, you can use the PAYLOAD
message data format to do the something.
BTW, if you still want to use the CXF dispatch API, you can use bean[1] or
processor[2] to integration the invocation within Camel route.
[1]http://camel.apache.org/bean.html
Thanks a lot for the suggestion, do we have any samples specific to cxf
that i can try out?
I need some more clarification between the relationship of the beans and
processors and how they fit in together?
I believe we can have an anonymous innerclass of processor to define the
custom business
Here are some discussions[1] about the different between the bean and processor.
An anonymous interclass can do the job for you.
As Current camel-cxf is using CXF client to send the invocation and PAYLOAD
data format can do the same job, we don’t have the plan to leverage the
dispatch API to
Our application is already using its webservice engine as CXF via the
dispatch api,
Now we are evaluating to add camel to utilize its EIP capabilities and
still yse CXF.
I could find no documentation whatsoever for using Camel with CXF dispatch
API.
Any hep is highly appreciated in this regard.
