NEW ISSUE: JMS bindingType and atLeastOne intent

TARGET:
JMS Binding Specification Version 1.1, Working Draft  25 September 2007


DESCRIPTION:

The current bindingType of the jms is defined as :

<bindingType type="binding.jms" alwaysProvides="jms"
mayProvide="atLeastOnce atMostOnce ordered conversation"/>

Not being at all policy expert and under the assumption that
"mayProvide" is supposed to indicate - ("in some scenarios when the
binding is used, this may be  provided, the assembler by supplying
intents can influence the runtime behavior of the binding"), here is the
question :

The semantics of atLeastOnce is actually having persistent messages over
a queue, and persistent messages + durable subscriptions over topic. 
If that can be configured by intents by the assembler, doesn't it
overlap with the setting of JMSDeliveryMode in the schema of the JMS
binding ? Which one wins in case of conflict ?


PROPOSED SOLUTION
 Drop JMSDeliveryMode from the schema