[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [sca-bindings] ISSUE 4: JMS binding can be used as pub/sub workarounding reference multiplicity
Hi Michael, I was little bit worried that by having "broadcast" bindings, the whole concept of reference multiplicity becomes very vague and such binding usage may interfere with any pub/sub concepts that the assembly TC may come up with (in-scope of their project charter) So I was hoping to ban "pub/sub" usage of bindings, but I am also ok with not opening of that specific issue. Peter -----Original Message----- From: Michael Rowley [mailto:mrowley@bea.com] Sent: Monday, 8. October 2007 18:18 To: sca-bindings@lists.oasis-open.org Subject: RE: [sca-bindings] ISSUE 4: JMS binding can be used as pub/sub workarounding reference multiplicity I do not believe that this should be opened as an issue, since it is a description of what is already possible. Michael -----Original Message----- From: Eric Johnson [mailto:eric@tibco.com] Sent: Friday, October 05, 2007 12:30 PM To: sca-bindings@lists.oasis-open.org Subject: [sca-bindings] ISSUE 4: JMS binding can be used as pub/sub workarounding reference multiplicity Logged as http://www.osoa.org/jira/browse/BINDINGS-4 -Eric. Peshev, Peter wrote: > 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]