Ah ok .. so you still have your cxf jms config. That is fine.
Using the camel transport for cxf is not that complicated but it has
it´s drawbacks. For example it does not
support streaming like cxf does. So as long as you don´t need to use
camel and cxf in the same route you will
probably be better off with the little extra redundancy.
Christian
Am 08.02.2011 19:28, schrieb Jeffrey Knight:
On Tue, Feb 8, 2011 at 1:11 PM, Christian Schneider
<ch...@die-schneider.net> wrote:
Ok so you did not really need a CXF Endpoint for your current project but
only wanted to have a camel JMS config
based on a CXF JMS config? I thought you wanted CXF and Camel to work both
on the same jms config.
I understood you were giving me two options:
1. use the camel transport for CXF to attach a CXF endpoint to a camel
jms destination.
2. have it redundant and use properties for each param you want to configure.
#1 would have been ideal, but #2 seemed the path of least resistance
and it'll serve our purposes for the moment.
--
----
http://www.liquid-reality.de
