[
https://issues.apache.org/jira/browse/SYNAPSE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556263#action_12556263
]
Rajith Attapattu commented on SYNAPSE-223:
------------------------------------------
I have commited an initial code drop to trunk (Committed revision 609189.).
There is still some outstanding work to be done.
Most notable issue is that Qpid hasn't done a 0-10 client release (neither the
AMQP WG has released the 0-10 spec).
So changes to the transport code is expected but will be transparent to the
user.
Currently I have Qpid jars hosted in my private maven repo as a temp measure.
We may see an official release form Qpid in mid April.
Once the AMQP transport stabilizers, I am planning to move it to Axis2 with
Asankha's help.
Rajith
> AMQP Transport
> --------------
>
> Key: SYNAPSE-223
> URL: https://issues.apache.org/jira/browse/SYNAPSE-223
> Project: Synapse
> Issue Type: New Feature
> Reporter: 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]
