NEW ISSUE 7: JMS bindingType and ordered intent

[Eric Johnson <eric@tibco.com>]

Logged as: http://www.osoa.org/jira/browse/BINDINGS-7

-Eric.

Peshev, Peter wrote:
> 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"/>
>
> A guidance for the implementation could be made for the ordered intent
> and what does it mean in the JMS case. 
>
> If it is provided by the assembler, it is especially interesting what
> happens if there are several instances of service consumers sending JMS
> messages in concurrent. Does the intent means that the messages are
> "ordered" within the instance that produced them - i.e. each service
> consumer instance is having a separate JMS session and in that case the
> ordering is guaranteed by the semantics of the JMS session.
>
> Or there is a global ordering within all the concurrent service
> consumers ? I.e. there is a global synchronization in the JVM for the
> whole wire, and there is a single JMS session behind it.
>
> Of course if there is no such "ordered" intent, the binding is free to
> do whatever it wants - a pool of JMS sessions, each time opening new
> one, etc.
>
> PROPOSED SOLUTION
>  Include clarification in the spec
>
>
>
>
>