[CONF] Apache Camel > Using CamelProxy

2011-03-31 Thread confluence
Using CamelProxy Page edited by Claus Ibsen Changes (2) ... For example given this client interface {snippet:id=e1|lang=java|titl

[CONF] Apache Camel > Using CamelProxy

2011-03-31 Thread confluence
Using CamelProxy Page edited by Claus Ibsen Changes (2) ... h3. Asynchronous using Future *Available as of Camel 2.8* By defaul

[CONF] Apache Camel > Using CamelProxy

2010-04-05 Thread confluence
Using CamelProxy Page edited by Claus Ibsen Using CamelProxy Camel allows you to proxy a producer sending to an Endpoint by a regular interface. Then when clients using this interface can work with it as if its regular java code but

[CONF] Apache Camel > Using CamelProxy

2010-04-05 Thread confluence
Using CamelProxy Page edited by Claus Ibsen Using CamelProxy Camel allows you to proxy a producer sending to an Endpoint by a regular interface. Then when clients using this interface can work with it as if its regular java code but

[CONF] Apache Camel > Using CamelProxy

2010-03-15 Thread confluence
Using CamelProxy Page edited by Christian Schneider Using CamelProxy Camel allows you to proxy a producer sending to an Endpoint by a regular interface. Then when clients using this interface can work with it as if its regular java

[CONF] Apache Camel > Using CamelProxy

2009-10-22 Thread confluence
Using CamelProxy Page edited by Claus Ibsen Using CamelProxy Camel allows you to proxy a producer sending to an Endpoint by a regular interface. Then when clients using this interface can work with it as if its regular java code but

[CONF] Apache Camel > Using CamelProxy

2009-10-22 Thread confluence
Using CamelProxy Page added by Claus Ibsen Using CamelProxy Camel allows you to proxy a producer sending to an Endpoint by a regular interface. Then when clients using this interface can work with it as if its regular java code but in realit