[chrisplough]

HTTP:
I agree - the lack of guaranteed delivery is the Achilles-heel of HTTP.

OAQ:
No, I don't believe it is single-threaded. The biggest issue is that only a couple of OTM clients are using this, so experience with it, within the OTM / G-Log ranks is lacking. With this particular client, it's hard to say if the performance issues where related to OAQ or to the integration process queues that they used. Oracle may have some OAQ experts, but many of they old G-Log support team (like myself) aren't extremely familiar with it. If you have experience with it, I'd investigate further.

BPEL:
I'm personally a fan of BPEL - the biggest issue I've seen is a lack of management capabilities and tools for the existing BPEL servers (Oracle, Active Endpoints). Technology-wise, I believe BPEL is very capable, especially with the newer BPEL 2.0 spec. If you already have experience here or are moving in this direction, I'd say go for it. If you have a need to be conservative, from a business perspective, then I'd look at OAQ or standard HTTP.

Web Services:
I'm not aware of any time-lines here, but wouldn't expect support before OTM 6.0. I expect OAS to catch up to WebLogic, in terms of performance and features, somewhere around OTM 6.5 or 7.0. There's a lot of work to be done, since OTM has been running on WebLogic for 8 years.

Hope this helps!

--Chris