Logged as: http://www.osoa.org/jira/browse/BINDINGS-158
-Eric.
On 4/11/11 8:16 AM, Simon Holdsworth wrote:
OF335FDEE3.E583A66F-ON8025786F.0053A637-8025786F.0053DFE1@uk.ibm.com"
type="cite">Target:
sca-jmsbinding-1.1-csd05.pdf
Description:
The JMS binding specification
includes
statement BJM60016 with a SHOULD keyword:
For an SCA service with a JMS binding,
when
a callback request message is sent and no callback destination
can be identified
then the SCA runtime SHOULD raise an error, and MUST throw an
exception
to the caller of the callback operation [BJM60016]
We need to clarify whether this
is an
optional part of the JMS binding spec.
Proposal:
Strengthen the statement by
removing
the SHOULD as follows:
For an SCA service with a JMS binding,
when
a callback request message is sent and no callback destination
can be identified
then the SCA runtime MUST raise an error and throw an exception
to the
caller of the callback operation [BJM60016]
Having done that I don't think
there's
any change to the testcase as its not possible to detect the
fact that
the SCA runtime has raised an error. The existing testcase
already
checks that an exception is thrown to the caller.
---------------------------------
Simon Holdsworth
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
|