OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-bindings message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Proposed resolution to issue BINDINGS-44



This proposed resolution applies to JMS binding spec cd01

Notes on this proposal:

---------------------------------------------------------------

Move Section 2 down to section 5 and reword as shown below.

Section 4:

Add the <wireFormat> and <operationSelector> elements to the pseudo-schema within the <binding.jms> element.
Add a <wireFormat> element within the <response> element

Add descriptions of these elements to the list below the pseudo-schema: Rename the nativeOperation attribute to selectedOperation: Update description of the property element: Section 5: rename to "Operation Selectors and Wire Formats"

Insert before section 5.1 (text based on what was in Section 2):

In general messaging providers deal with message formats and destinations.  There is not usually a built-in concept of “operation” that corresponds to that defined in a WSDL portType [WSDL].  Messages have a format which corresponds in some way to the schema of an input or output message of an operation in the interface of a service or reference, however additional information is required in order for an SCA runtime to know how to identify the operation and understand the format of messages.

The process of identifying the operation to be invoked is operation selection; the information that describes the contents of messages is a wire format.  The binding element as described in the SCA Assembly specification [ref needed] provides the means to identify specific operation selection via the operationSelector element and the format of messages received and to be sent using the wireFormat element. The JMS binding defines a default operation selector and wire format and the corresponding operationSelector and wireFormat elements ; SCA providers may provide additional such elements.

No standard means is provided for linking the wireFormat or operationSelector elements with the runtime components that implement their behaviour.

Section 5.1 "Default Operation Selector", add the following paragraph:  "The use of this operation selector can be explicitly specified in a binding.jms using the <operationSelector.jmsdefault> element; if no operationSelector element is specified then SCA runtimes MUST use this as the default."

Update the last paragraph: "An SCA runtime SHOULD provide the means for identifying alternative operation selectors via additional <operationSelector> elements."

Replace "native operation name" with "selected operation value" throughout this section.

Section 5.2 "Default Data Binding", rename to "Default Wire Format" and reword to that effect throughout; add the following paragraph:

The use of this wire format can be explicitly specified in a binding.jms using the <wireFormat.jmsdefault> element; if no wireFormat element is specified then SCA runtimes MUST use this as the default.

Update the last paragraph: "An SCA runtime SHOULD provide the means for identifying alternative wire formats to support any other type of JMS message via additional <wireFormat> elements."

---------------------------------------------------------------

Simon Holdsworth
STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC Chair
MP 211, IBM UK Labs, Hursley Park, Winchester SO21 2JN, UK
Tel +44-1962-815059 (Internal 245059) Fax +44-1962-816898
Internet - Simon_Holdsworth@uk.ibm.com





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU








[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]