Proposed updates for issues 96 and 110 within JMS spec doc

As discussed on yesterday's call, here
is an updated version of the JMS binding spec with the proposed resolutions
of issues BINDINGS-96 and BINDINGS-110 included (I've done both in one
documents as there is no overlap).

For BINDINGS-110, the purpose is to
remove all mention of any use of a binding element in a definitions file,
so there should be no mention of any such behaviour remaining.

For BINDINGS-96, the purpose is to show
the updates in context, in order to see if there is any simplification
possible.  The refactoring suggested is to move the bidirectional
cases from section 6.4.1 and merge them into sections 6.1 and 6.2, and
make those sections apply to both undirectional and bidirectional interfaces.
 The main justification for this is that for request/response operations,
all the statements for setting JMSReplyTo are identical for invocations
on the forward and callback interfaces.  For each case of request/response
and oneway there would then be a single additional statement that says
the scaCallbackDestination or JMSReplyTo is set to the callback destination
respectively.

Regards, Simon

Simon Holdsworth

STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC Chair,
AT&T and Boeing Lab Advocate

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

sca-jmsbinding-1.1-spec-cd03-issues96and110.doc