JMS Binding does not conform to the specification when selecting the opeartion to invoke

Currently, the way that the JMS Binding selects a method to invoke is not compliant with the SCA JMS Binding specification. Currently it always uses the scaOperationName parameter to find the operation This is option 2 in the specifications (lines 205 & 206 - see below)

The JMS Binding specification says:

197 1.5 Default Operation Selection and Data Binding behavior

198 This section describes the default behavior for operation selection and data binding for a JMS
199 binding.

200 1.5.1 Default Operation Selection
201 When receiving a request at a service, or a callback at a reference, the native operation name is
202 determined as follows:

203 • If there is only one operation on the service's interface, then that operation is assumed as
204 the native operation name.

205 • Otherwise, if the JMS user property "scaOperationName" is present, then its value is used as
206 the native operation name.

207 • Otherwise, the native operation name is assumed to be "onMessage".