synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SYNAPSE-223) AMQP Transport
Date Sun, 06 Jan 2008 21:16:34 GMT

    [ https://issues.apache.org/jira/browse/SYNAPSE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556425#action_12556425
] 

Andreas Veithen commented on SYNAPSE-223:
-----------------------------------------

The commit actually breaks the build in my case. It seems that Maven takes the Qpid artifacts
from the Apache snapshot repository instead of Rajith's private repository.

> AMQP Transport
> --------------
>
>                 Key: SYNAPSE-223
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-223
>             Project: Synapse
>          Issue Type: New Feature
>            Reporter: Rajith Attapattu
>            Assignee: Rajith Attapattu
>
> 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
parameters.
> * 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: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org


Mime
View raw message