[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: NEW ISSUE: JMS binding can be used as pub/sub workarounding reference multiplicity
TARGET: JMS Binding Specification Version 1.1, Working Draft 25 September 2007 DESCRIPTION: Suppose that a component A has reference with multiplicity 1 and is wired to a component B via binding.jms over a jms topic, and there is a component C that is wired to a component D via jms binding OVER THE SAME TOPIC. That will mean that by the semantics of the JMS that whenever the reference from the component A is being invoked, the message will be sent to component B AND AT THE SAME TIME it will be sent as well to the component D. (Here the JMS binding specifies that operations should be oneway if topic is used, so technically there are no problems with such scenario) In other words if there is a reference with the following definition <reference name="MyReference"> <interface.java interface="myInterface"/> <binding.jms> <destination name="MyTopic" type="topic" /> </binding.jms> </service> Than there will be a pub/sub to all components who have exposed services : <service name="MyService"> <interface.java interface="myInterface"/> <binding.jms> <destination name="MyTopic" type="topic"/> </binding.jms> </service> In that way the assembler via a creative usage of JMS binding can form a pub/sub (one invocation from A is broadcasted) eventhough the component developer has put multiplicity "1" on the reference in "A". Is this an issue that needs solving ? PROPOSED SOLUTION None
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]