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 18:36: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

Fixed the previous problem with this patch. It now runs fine ( I learnt that I have to wait
for the response and there is no ReadFuture equivalent of WriteFuture). 

> 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