Do you know if the limitation is in Mina or the Camel-Mina component?
It in the mina component sync determines the exchange pattern:
// set sync or async mode after endpoint is created
if (sync) {
endpoint.setExchangePattern(ExchangePattern.InOut);
} else {
endpoint.setExchangePattern(ExchangePattern.InOnly);
}
From:
http://svn.apache.org/viewvc/activemq/camel/tags/camel-1.5.0/components/camel-mina/src/main/java/org/apache/camel/component/mina/MinaComponent.java?view=markup
http://svn.apache.org/viewvc/activemq/camel/tags/camel-1.5.0/components/camel-mina/src/main/java/org/apache/camel/component/mina/MinaComponent.java?view=markup
Is this because it has to for proper mina operatio or camel component
reasons?
--
View this message in context:
http://www.nabble.com/Can-mina%3A%3Atcp-do-asyncronous-bidirectional-messages--tp20431804s22882p20441499.html
Sent from the Camel - Users mailing list archive at Nabble.com.
