synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera (JIRA)" <>
Subject [jira] Updated: (SYNAPSE-223) AMQP Transport
Date Wed, 02 Apr 2008 14:47:27 GMT


Asankha C. Perera updated SYNAPSE-223:

Is this completed? Can you fix the dependency versions now.. if so, I would like to see an
example usage of this in our samples

> AMQP Transport
> --------------
>                 Key: SYNAPSE-223
>                 URL:
>             Project: Synapse
>          Issue Type: New Feature
>            Reporter: Rajith Attapattu
>            Assignee: Rajith Attapattu
>             Fix For: 1.2
> The AMQP transport will be based on the Apache Qpid project.
> Apache Qpid has a JMS client implementation over AMQP. Since Synapse has a JMS transport,
you could use that to get AMQP support as well.
> However a native client has the following advantages.
> * You can use any exchange, not just direct (JMS Queues) or topic (JMS Topics). Ex. fannout,
headers or a custom exchange.
> * Ability to customise the exchange type, exchange name, routing key and other AMQP specific
> * More fine grained control of AMQP concepts
> * Possibility of streaming large attachments off the disk. (need to figure out how to
leverage the AXIOM support here).

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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message