[
https://issues.apache.org/jira/browse/SYNAPSE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556449#action_12556449
]
Rajith Attapattu commented on SYNAPSE-223:
------------------------------------------
Asankha,
Please exclude the AMQP tranport when u make the 1.1.1 branch. Even though the
code will be ready before the release, Qpid will not have a release and we will
be stuck with snapshots which is a big problem for the Synapse release. After a
chat with Paul, I think Synapse 1.2 release would be the time we can include
AMQP transport due to the Qpid release cycle.
Another option is we can rollback the commit I made and then commit after you
are done with cutting a branch. I am ok with both options, so feel free to do
what you feel is best.
Asankha I wasn't sure what to do, so put them in a private repo as temp
messure. Any chance you can host them in the wso2 repo with a different name,
so we can get rid of the problems Andreas is seeing?
I have more to commit, but will hold on until we sort the current problems.
Regards,
Rajith
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
