[TUSCANY-2987] Sort out jms operation selector mapping to service operations

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Java-SCA-1.4
• Fix Version/s: Java-SCA-1.x
• Component/s: Java SCA JMS Binding Extension
• Environment: All
• Assignee: Unassigned
• Reporter: Simon Laws
• Created: 24/Apr/09 17:45
• Updated: 19/Sep/10 11:31
• Resolved: 26/Apr/09 12:08

Description

There are two parts to this

First, the code for nativeOperation handling is in the wrong place. It's in the reference side rather than the service side. I.e. the HeaderReferenceInterceptor shouldn't be trying to do anything with it.

What I believe should happen is that in the service side operation selector we should...

generate an operation name as defined in the default operation selector algorithm in the spec
use this operation name to locate an operation properties using the operationProperties/@name attirbute
use this operationProperties/@nativeOperation attribute to find the real operation to call.

It seems useful to show how to generate a new, non-default operation selector, to allow the user to specific which propery in the message the operation name will be pulled. This is not defined in the specification. But is does motivate us to put the native operation processing in a separate interceptor so that regardless of which operation selector is used to choose the operation name the same nativeOperation processing can be applied