[TUSCANY-3783] Various improvments to the OASIS async programming model support we provide

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: Java-SCA-2.0-Beta1
• Fix Version/s: Java-SCA-2.x
• Environment: All
• Assignee: Unassigned
• Reporter: Simon Laws
• Created: 17/Nov/10 09:37
• Updated: 04/May/11 07:37

Description

Looking at the async programming model support we currently have in the runtime there are several areas we need to improve. For example,

• support void return types
• remove the need for the forward call to use exceptions to unwind the call stack
• provide clear separate between the Java specific bits and the infrastructure bits

I'll raise sub tasks here as I come across areas I'd like to see improved.

Sub-Tasks

• The Java callback pattern of the aynch programming model is not implemented correctly: Open
• Consider what reliable async would look like: Open
• MessageId field on Message object no longer used. Async uses MESSAGE_ID but as a header. Can we remove the field?: Open
• Enable core async handling code to supply correct information for all binding types: Open
• Enable the JMS binding to deal with Async service invocations: Open
• Enable binding.sca to deal with Async service invocations: Open
• Enable binding.ws (Axis2) to deal with Async service invocations: Open