camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ciaran Wood (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-3823) Upgrade to CometD 2.1.0
Date Tue, 19 Apr 2011 10:56:06 GMT

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

Ciaran Wood updated CAMEL-3823:
-------------------------------

    Attachment: Adding_support_for_cometd_2_1_0.patch

Attached is a patch to upgrade the camel-cometd component to use cometd 2.1.0. I have tested
applying the patch to trunk and it applies cleanly.

A quick note on some behaviour that has changed between cometd versions:
Before, any client could subscribe to /service/** channels and receive all publishes to that
channel, regardless of whether they published the message. The behaviour in the new version
is that /service/** channels work in a request-reply style. You subscribe to the channel,
publish to that channel and only the publisher should receive a reply. This works quite well
with the InOut pattern in camel, so in the CometdConsumer, we check the exchange pattern and
if it is InOut, send a reply.

The previous InteractiveMain tests used to subscribe on /service/test, I have changed that
to subscribe to /channel/test, which exhibits the older behaviour. I have added an InOut test
which uses the /service/test channel.

> Upgrade to CometD 2.1.0
> -----------------------
>
>                 Key: CAMEL-3823
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3823
>             Project: Camel
>          Issue Type: Task
>    Affects Versions: 2.6.0
>            Reporter: Joshua Watkins
>            Priority: Minor
>             Fix For: Future
>
>         Attachments: Adding_support_for_cometd_2_1_0.patch
>
>
> The current version of the Cometd component uses Cometd 1.0.1. Cometd 2.1.0 has better
support for the InOut messaging pattern.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message