hi,
On 09/03/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Gerald
From my understanding QPid fully passes the JMS TCK, so you can use
AMQP out-of-the-box with the existing JMS plug today. So in answer to
your question its trivial to use AMQP.
In general, there seems to be a mismatch between AMQP features and the
JMS API, in particular with the concept of an Exchange missing from
JMS.
Qpid claims to support "All features required by the Sun JMS 1.1
specification". Last time i checked, though, i wasn't able to write a
Qpid client without resorting to the Qpid-specific API - but i'll
certainly try again and try to hook it up to Synapse/Axis2. Will keep
this list posted...
For example, without any coding you should be able to put an XML
message onto AMQP and have Synapse read it, and then route it to a
WS-ReliableMessaging endpoint - for example a Microsoft .NET server.
I think the interesting question is whether we can do tighter
integration, and we'd love any input on what that could be.
for instance: the ability to dynamically declare AMQP exchanges,
queues and bindings (which wire an exchange to a queue) from Synapse
(possibly based on incoming message properties, etc.), since these
dynamic capabilities are a core feature of AMQP that is missing from
JMS.
I'm also interested interested in the wider questions around reliable
messaging protocols, so if you're in a position to share your thoughts
around AMQP I'd love to hear those too.
i should consolidate my thoughts first ;-) but it is my impression
that AMQP is still in a very early stage of its lifecycle:
- there is no standardised Java binding
- even the abstracted API that the spec defines is in flux (e.g. the
new message class)
- i'm unsure as to the interoperability of different AMQP
implementations (which is, after all, one central goal for AMQP)
- it promisses on-the-wire interoperability without compromising
performance, though
- it's not firewall-friendly
- the spec is very well written ;-)
cheers,
gerald
Paul
On 3/9/07, Gerald Loeffler <[EMAIL PROTECTED]> wrote:
> Hi asankha,
>
> thanks for your quick response. AMQP transport in Synapse/Axis2 is not
> an immediate requirement for us but something that we will want to be
> able to do in the not-to-distant future without incurring too much
> effort (based on one of the open-source AMQP implementations i
> mentioned). So it is important to know that you don't consider it a
> difficult task adding it to Axis2. I'll have a look at the relevant
> Axis2 APIs and the code for the JMS transport to get a better idea...
>
> As to who is going to do it: that entirely depends on our schedule
> when the concrete need for AMQP arises from our project...
>
> thanks again,
> gerald
>
> On 09/03/07, Asankha C. Perera <[EMAIL PROTECTED]> wrote:
> > Hi Gerald
> > > Can you please give me a rough idea of what it entails to add support
> > > for a new transport to Synapse? I would want to add support for AMQP
> > > (http://www.amqp.org/), which has a JMS-like Java client API (see
> > > http://cwiki.apache.org/qpid/, http://www.rabbitmq.com/). Is this
> > > trivial or a major task? Since Synapse does not build on JBI, it must
> > > have its own APIs for doing this...
> > Adding a new transport to Synapse is the same as adding a new transport
> > for Axis2 - and is not a difficult task. There are certain Axis2 API's
> > you need to implement, and the existing transports should provide
> > adequate examples and code to help guide the effort.
> >
> > Would you be interested in developing an AMQP transport for
> > Synapse/Axis2 yourself, or looking at how you could get the AMQP support
> > built into Synapse through the community? Either way I think having an
> > actual user requiring a new transport would help in its implementation,
> > scope and testing efforts. I will read through some of the links you
> > have provided meanwhile..
> >
> > asankha
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> http://www.gerald-loeffler.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://www.gerald-loeffler.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
