Logged as: http://www.osoa.org/jira/browse/BINDINGS-60
-Eric.
Simon Holdsworth wrote:
TARGET: SCA JMS Binding
Specification
cd01
DESCRIPTION:
The default wire format and
operation
selector defined in the JMS binding spec are provided as minimum
functionality,
primarily to ensure that messages sent by a reference with a JMS
binding
can be received and correctly processed by a service with a JMS binding
without any additional vendor-specific configuration.
However these elements require a
specific
wire representation, where in general JMS applications will tend to use
a variety of other wire formats requiring different operation
selectors.
Without any additional wireFormat and operationSelector elements
defined as standard, integration with these applications will require
vendor-specific
extensions which will limit portability.
PROPOSAL:
We need to consider whether there
are
any additional wireFormats or operationSelectors we should include in
the
JMS binding spec (or assembly spec if applicable).
Some possible examples (half-baked,
not intended to be a formal proposal, just to provoke discussion):
wireFormat.xml - has the
behaviour defined for the default binding, specifically when the
message
is the XML serialization of the interface (not JMS-specific)
wireFormat.jmsMessage - when the
interface has JMS message as the parameter
wireFormat.bytes - when
there is a single byte[] parameter (not JMS-specific)
wireFormat.text - when there
is a single string parameter (not JMS-specific)
wireFormat.fixedWidth - message
consists of values of fixed widths with a defined mapping to the
parameters
in the interface (not JMS-specific)
wireFormat.separated - message
consists of values with a given separator with a defined mapping to the
parameters in the interface (not JMS-specific)
wireFormat.dfdl - message
structure is defined via WSDL annotations as described by Data Format
Description
Language (not JMS-specific)
wireFormat.xslt - message
structure is defined via XSLT (not JMS-specific)
operationSelector.jmsUser -
selected
operation name is passed in the specified JMS user property
operationSelector.jmsType -
selected
operation name is the type of the JMS message
operationSelector.fixed
- selected operation name is the specified value (not JMS-specific)
operationSelector.singleOperation -
when the interface has a single operation (not JMS-specific)
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
|