camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raul Kripalani <>
Subject Re: Camel CXF: In-VM
Date Thu, 09 Aug 2012 18:36:42 GMT
Have you considered using OSGi services instead?

In case you haven't heard of them, they are: 1) Simple POJOs which contain
your business logic, 2) exposed inside your container (in-VM) for direct
method-to-method invocations, 3) can be looked up dynamically in the OSGi
Service Registry, 4) you can attach attributes to services to express
metadata, 5) can search services by using LDAP-like filters, 6) eventually
you can consider exposing them remotely via Distributed OSGi.

Otherwise, if you decide to stick with the local CXF transport, this
exception "java.lang.IllegalStateException: Local destination does not have
MessageObserver on address" seems to indicate that there's no service
provider attached in the same VM to that address. This makes a lot of

Try to instantiate a CXF endpoint (service provider) on that address,
either by using Spring or the CXF API. As Willem suggested, you need to
instantiate it inside the same VM.

But really, my tip is that you look in the OSGi services direction instead.

Hope that helps,

*Raúl Kripalani*
*Principal Consultant | FuseSource Corp. | <>
skype: raul.fuse | twitter: @raulvk <>,
blog: F3 - Flashes From the


On 9 August 2012 14:06, objectorange <> wrote:

> forgot to add...these cxf services need to be easily configured to be
> exposed
> by wire protocols in addition to the local address.
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message