Proposed resolution to issue BINDINGS-45

Folks,

Here's my proposed resolution to issue
BINDINGS-45 (Update binding.jca spec for wireFormat/operationSelection
elements)

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

Applies to binding-jca-1.1-spec-cd02:

Delete section 2:
"Operation Selection and Data Binding".

Section 3: JCA Binding

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

Add descriptions of these elements to the list below the pseudo-schema:

/binding.jca/wireFormat –
identifies the wire format used by requests and responses sent or received
by this binding as defined in the SCA Assembly Specification [SCA-Assembly].

/binding.jca/operationSelector
– identifies the operation selector used when receiving requests for a
service as defined in the SCA Assembly Specification [SCA-Assembly].

Add Section 4 "Operation Selectors
and Wire Formats"  (Heavily based on what
is in the JMS binding spec):

In general JCA resource adapters deal with
records.  There is not usually a built-in concept of “operation”
that corresponds to that defined in a WSDL portType [WSDL].  Records
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 Resource Adapter-specific information is required in
order for an SCA runtime to know how to identify the operation and understand
the format of records. 

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 [SCA-Assembly] 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.  

This specification does not define default
behavior for the operation selection or wire format of a JCA binding. This
choice had been made because the implementations of generic Record interfaces
that define the data exchanged between JCA adapter and its client are specific
to a particular adapter and, unlike JMS, cannot be used in a generic manner.

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

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

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 - 

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