There was a second, more important reason to retire the AMQP
transport: it started as a fork of the JMS transport, but after that
fork was done, we discovered some very serious issues in the JMS
transport. They have been fixed in the JMS transport, but the AMQP
transport probably inherited them, basically making it unsuitable for
production use.

Andreas

On Wed, Nov 25, 2009 at 18:43, Asanka Abeysinghe <asan...@wso2.com> wrote:
> Hi Lahiru,
> There was a native AMQP implementation done in the synapse code base
> (org.apache.synapse.transport.amqp) sometime back and removed due to
> dependencies it had with an unreleased QPid version (M3 or M4).
> Currently Synapse do support AMQP using JMS. There is a working sample with
> AMQP and FIX (Sample #260).
> Thx
> Asanka
>
> On Wed, Nov 25, 2009 at 7:52 PM, Lahiru Gunathilake <glah...@gmail.com>
> wrote:
>>
>> Hi all,
>>
>> I like to do some work with synapse AMQP trasport and like to know the
>> status of the trasport in current synapse code base.
>>
>> Regards
>> Lahiru
>>
>> --
>> Apache Qpid, Worlds dominant messaging middleware..!!!
>
>
>
> --
> Asanka Abeysinghe
> Architect - WSO2, Inc.
> m: +94 77 7340064      p: +94 11 2688451/3
> e: asan...@wso2.com w: http://www.wso2.com
> b: http://www.asankama.com
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Reply via email to