synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ruwan Linton (JIRA)" <>
Subject [jira] Commented: (SYNAPSE-223) AMQP Transport
Date Fri, 11 Apr 2008 05:16:04 GMT


Ruwan Linton commented on SYNAPSE-223:

Rajith, I must say that I did a mistake when checking the AMQP compilation test. I skipped
the unit tests, and i seems some of the unit tests are failing due to a jar conflict with
the existing once. 

Can you please run through all the test cases and see what are the jars which are conflicting
with the existing once and exclude them? Basically, build fails with the test cases, if you
enable the AMQP transport for the moment. 

> 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