synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SYNAPSE-223) AMQP Transport
Date Mon, 07 Jan 2008 05:14:34 GMT

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

Asankha C. Perera commented on SYNAPSE-223:
-------------------------------------------

Rajith

I must apologize that I actually excluded the AMQP transport when I cut the branch yesterday..
I am ok keeping it in the trunk for now, but we should sort out the repository issues in the
trunk so that builds work. I think the right place for apache snapshots is the apache m2 snapshot
repo..  and you can upload it there manually (i.e. by hand).. Anyway, as Andreas has experienced,
maven picks up whatever it finds as the latest for a SNAPSHOT artifact if it exists in multiple
repos, so putting it on the wso2 repo will not help, neither hosting it privately in your
repo, as long as apache snapshots has a copy too.. 

Do you know why versions found there may differ from what you have in your private branch?
one solution is to build (or rename) the snapshot you have as a revision (e.g. check what
we have done for commons.vfs - I built a revision and uploaded the binary and the source of
it to the repo) .. then you can force maven to pick up the point version..

once we sort out the repo issues and online builds correctly, you can check in future changes
to the trunk and it should be fine :)

thanks
asankha

> 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