← Prev in month ← Prev in thread
Next in thread → Next in month →

NEW ISSUE: JMS message selector should not be specific to pub/sub

From
Simon Holdsworth <>
Date
2009-01-27T15:03:59+00:00
ID
Thread
NEW ISSUE: JMS message selector should not be specific to pub/sub
TARGET: SCA JMS Binding Specification
CD-01 rev 4 

DESCRIPTION: 

Issue BINDINGS-12 introduced support
for message selectors.  The original issue statement did not say this
was necessarily specific to use with JMS Topics, however the resolution
wording is quite specific to Topics, without actually enforcing that -
no conformance statement about whether subscriptionHeaders can be used
when the destination type is Queue.

An update to the element name and wording
would clarify that this is can be applied to both queues and topics.

PROPOSAL:

Rename subscriptionHeaders element to
messageSelection

Update the description of this element:

/binding.jms/messageSelection
- this element allows JMS message selection options to be set. These values
apply to a service receiving messages from the request destination or for
a reference receiving messages from the callback or reply-to destination.The
description of the JMSSelector element remains unchanged.

Regards, Simon

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
← Prev in month ← Prev in thread
Next in thread → Next in month →