scussion below:
http://camel.465427.n5.nabble.com/publish-subscribe-with-camel-netty4-tp5801431p5802787.html
To unsubscribe from publish/subscribe with camel-netty4, click
here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?ma
t channel from pool {}", existing);
}
} catch (Exception e) {
exchange.setException(e);
callback.done(true);
return true;
}
...
}
Does anybody know a better solution?
Thanks,
Jörg
--
View this message in context:
http://camel.465427.n5.nabble.com/publish-subscribe-with-camel-n
class)))
;
--
View this message in context:
http://camel.465427.n5.nabble.com/publish-subscribe-with-camel-netty4-tp5801431p5801683.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi everybody,
I have to create an interface which should communicate to a server over tcp/ip.
After an initial registration request, the server will publish all upcoming
events on the same socket (and channel).
My first idea was to create two routes, one for the request the other one
acting as
