camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicky Sandhu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-133) add support for a MessageExchangePattern enum property on Exchange and make MINA support both InOnly and InOut
Date Wed, 19 Sep 2007 16:32:22 GMT

     [ https://issues.apache.org/activemq/browse/CAMEL-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nicky Sandhu updated CAMEL-133:
-------------------------------

    Attachment: patch.txt

I was in need to communicate with a text based protocol socket. I am adding a patch to configure
codec via URI parameters. This patch also allows for InOut ExchangePattern on the MinaProducer
and waits for response.

There is test case (MinaTcpWithInOutTest)  using the ReverserServer from mina examples. The
test case only works when stepping via debugger and not when run... I think its related to
the AsyncProcessor changes. Please take a look


> add support for a MessageExchangePattern enum property on Exchange and make MINA support
both InOnly and InOut
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-133
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-133
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core, camel-mina
>            Reporter: James Strachan
>             Fix For: 1.2.0
>
>         Attachments: patch.txt
>
>
> currently MINA assumes InOnly; we should make it easy to configure things to be InOut
or InOnly - maybe also defaulting the MEP via a URI parameter?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message