Rupert Smith wrote:
So, how do we let a JMS application do something that is more AMQP
like? For
example, there is no way in the current JMS implementation to do JMS
over a
headers exchange. Some suggestions:
1. Use the management console to set up the headers exchange and bind a
queue to it. The JMS just accesses this queue already set up.
2. Do the same thing, but you specify this in the properties that you
pass
to the JNDI context, to get your connection factory from. Not exactly
a nice
solution.
Both these approaches are pure JMS compliant. If you changed to a
different
JMS product, you'd have to figure out their way of doing it.
And these may well be sufficient.
3. Provide an extension API that gives you access to AMQP features, or
just
make the lower level AMQ API available publicly.
Once an app starts doing 3, its not plain JMS anymore, so can't change
to a
different JMS provider. At least its the application writers choice to
move
outside of JMS.
I think the only clean way to do this would be to have the functionality
added through Java Community Process, which is not an easy thing to do.
But should that prevent us from making additional functionality
available in the native Java AMQ binding?
Jonathan
