John,
That's very helpful. I saw in the documentation that replacing JMS was one goal - so that is consistent.
Of course as usual when you read the marketing blurb its difficult to understand what is actually going on as they use all those great feel good words - open standard, global, messaging, etc, etc!
So my original prognosis and Dale's synopsis that this is something that can potential coexist with our work is the good news.
Definately would be something that could be of interest to possibly actually try out at some point.
There's obviously some use cases that could be mutually cool to do. I'm coming at this from the TWIST perspective - and their original vision of an e-Marketplace workflow - so something like receiving a confirmation that funds have been deposited - and then releasing the shipping notice to the freightforwarder would count.
Where the ebXML system would do the external orchestration - and pass messages to the AMQP backend middleware to confirm the financial transaction. Heck you could even use something like Oracle's BPEL and Oracle A/S ebXML for this over the top of an ERP - to control the business process logic... and then the freightforwarder would have a nice lightweight ebXML solution.