Anyone? I'm using this with a Camel recipientList. I've now written an small service invoker class which pulls the name of the service interface, the operation name and concatenates them with bean: in order to invoke the associated OSGi service instead of going through routes. But I'm still left with the problem of multiple set ups of CXF endpoints with duplicated information and I can't seem to find any good examples that don't do it that way.
On Fri, Feb 26, 2016 at 10:04 PM, Ranx <[email protected]> wrote: > And is there a way to set that up so that the service interfaces/endpoints > are just a list? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/CXF-server-versus-endpoints-tp5778342p5778343.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
