You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "James Strachan (JIRA)" <ji...@apache.org> on 2007/08/31 17:22:22 UTC
[jira] Created: (CAMEL-133) add support for a
MessageExchangePattern enum property on Exchange and make MINA support both
InOnly and InOut
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
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.
[jira] Updated: (CAMEL-133) add support for a
MessageExchangePattern enum property on Exchange and make MINA support both
InOnly and InOut
Posted by "Nicky Sandhu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicky Sandhu updated CAMEL-133:
-------------------------------
Attachment: (was: patch.txt)
> 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
>
>
> 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.
[jira] Commented: (CAMEL-133) add support for a
MessageExchangePattern enum property on Exchange and make MINA support both
InOnly and InOut
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40065 ]
James Strachan commented on CAMEL-133:
--------------------------------------
now you can do endpoint.createExchange(pattern) to specify an exact ExchangePattern to be used on an endpoint
> 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
>
>
> 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.
[jira] Resolved: (CAMEL-133) add support for a
MessageExchangePattern enum property on Exchange and make MINA support both
InOnly and InOut
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Strachan resolved CAMEL-133.
----------------------------------
Resolution: Fixed
patch applied with huge thanks Nicky! Great job!
> 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.
[jira] Updated: (CAMEL-133) add support for a
MessageExchangePattern enum property on Exchange and make MINA support both
InOnly and InOut
Posted by "Nicky Sandhu (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CAMEL-133) add support for a
MessageExchangePattern enum property on Exchange and make MINA support both
InOnly and InOut
Posted by "Nicky Sandhu (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CAMEL-133) add support for a
MessageExchangePattern enum property on Exchange and make MINA support both
InOnly and InOut
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40064 ]
James Strachan commented on CAMEL-133:
--------------------------------------
trunk now supports Exchange.getExchangePattern() which is-a ExchangePattern
> 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
>
>
> 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.