camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem jiang <>
Subject Re: Camel Fabric example
Date Mon, 11 Nov 2013 00:41:34 GMT
Camel-Fabric is only provided in Fuse. If you don’t want to use Fuse, you have to implement
the services publish and locator yourself.

Willem Jiang

Red Hat, Inc.
Blog: ( (English)
 ( (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem

On Monday, November 11, 2013 at 8:07 AM, pmp.martins wrote:

> So far all my test projects use sockets or HTTP endpoints; each client
> wishing to communicate with another server (or service) needs to know all
> the available network addresses of each implementation (e.g. a list of
> protocols, host name & ports).
> To fix this, I remembered a suggestion made by a user here, that pointed me
> to Camel Fabric. According to the Fuse documentation, it "(...) /provides a
> way to reuse Fabric's discovery mechanism to expose physical socket & HTTP
> endpoints into the runtime registry using a logical name /(...)"
> However, I have not found any living examples on how to use this in the
> Camel in Action book, nor on the Internet. Everything I find requires JBoss
> tools and Fuse.  
> Consequently I have a question:  
> 1. Does Camel support this feature? If yes, where can I find an example to
> study?
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at (

View raw message