The PushStream is a streaming api. It focuses on defining a pipeline, but the implementation is not related to any distribution mechanism.
If you want to send messages across VMs on your network, you really should focus on ActiveMQ. There's no real OSGi specific facade I know of, so my best bet would be Camel too, as others have said. You can just show the minimum of camel, just what is needed to actually consume the JMS message from a pojo or to send messages from a pojo. You don't have to look at everything Camel can do. 2017-04-06 7:48 GMT+02:00 Dominik Przybysz <[email protected]>: > Hmm, > it is difficult to understand for me... > Could you explain how it will be works, for example, with ActiveMQ? > > 2017-04-06 5:31 GMT+02:00 Raymond Auge <[email protected]>: > > > OSGi R6 provides the Asynchronous Services specification which Aries > > implements [1]. > > > > Aries Async also directly implements R6 Promises which can be used to > great > > effect (same url). > > > > Finally, R7 updates RSA [2] (see chapter 100, Section 3.2.1) to support > the > > following async return types on service methods: > > > > org.osgi.util.promise.Promise > > java.util.concurrent.Future > > java.util.concurrent.CompletionStage > > java.util.concurrent.CompletableFuture > > > > [1] http://aries.apache.org/modules/async-svcs.html > > [2] https://osgi.org/download/osgi.enterprise-7.0.0-early- > > draft-2017-03.pdf > > > > - Ray > > > > > > > > On Wed, Apr 5, 2017 at 5:37 PM, Christian Schneider < > > [email protected] > > > wrote: > > > > > I am also very interested in some good async communication mechanism > for > > > OSGi. It would be great to have something like in RSA where you can > plug > > in > > > transports. > > > > > > Christian > > > > > > 2017-04-05 21:50 GMT+02:00 Raymond Auge <[email protected]>: > > > > > > > On Wed, Apr 5, 2017 at 2:32 PM, Dominik Przybysz < > [email protected] > > > > > > > wrote: > > > > > > > > > RFC looks great, especially `The solution MUST allow the sending of > > > > > asynchronous messages to remote recipients.` > > > > > > > > > > But I do not see anything connected with sending events between VMs > > in > > > > > Specification Draft or in aries repo > > > > > https://github.com/apache/aries/tree/trunk/pushstream ... Does it > > work > > > > > only > > > > > on one VM? > > > > > > > > > > > > > Hmm... This is where Tim Ward would be better qualified to answer. I > > > can't > > > > remember if in his demos he paired it with Async/RSA or some other > > > > remoting... > > > > > > > > @Tim? > > > > > > > > - Ray > > > > > > > > > > > > > > > > > > 2017-04-05 20:10 GMT+02:00 Raymond Auge <[email protected] > >: > > > > > > > > > > > Oh, and the Push Stream Spec - Chapter 706 is included in the > > public > > > > > review > > > > > > draft [1] > > > > > > > > > > > > [1] https://osgi.org/download/osgi.enterprise-7.0.0-early- > > > > > > draft-2017-03.pdf > > > > > > > > > > > > On Wed, Apr 5, 2017 at 2:06 PM, Raymond Auge < > > > [email protected] > > > > > > > > > > > wrote: > > > > > > > > > > > > > FYI, the state of Push Stream Spec is 95% complete and stable. > > The > > > > OSGi > > > > > > CT > > > > > > > is effectively complete, and the RI (Apache Aries Push Stream) > is > > > > also > > > > > > > effectively done, stable, and passes the CT. > > > > > > > > > > > > > > The spec is only waiting for the release of OSGi R7 Compendium, > > so > > > > what > > > > > > > you see there now should be stable and what comes out at > release. > > > > > > > > > > > > > > - Ray > > > > > > > > > > > > > > On Wed, Apr 5, 2017 at 2:02 PM, Dominik Przybysz < > > > > [email protected] > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > >> @Raymond It look promising. I will check it. > > > > > > >> > > > > > > >> I was looking for something like that > > > > > > >> https://github.com/ops4j/org.ops4j.pax.jms but the last > commit > > > was > > > > in > > > > > > >> 2013 > > > > > > >> and it was never released... > > > > > > >> > > > > > > >> 2017-04-05 19:54 GMT+02:00 Dominik Przybysz < > > [email protected] > > > >: > > > > > > >> > > > > > > >> > Yeah, > > > > > > >> > I know camel, but I need something more easier to use and > show > > > to > > > > > new > > > > > > >> ones. > > > > > > >> > > > > > > > >> > 2017-04-05 19:45 GMT+02:00 Karabo Molema < > [email protected] > > >: > > > > > > >> > > > > > > > >> >> Hi, > > > > > > >> >> > > > > > > >> >> You could look into using Apache camel, it integrates well > > with > > > > JMS > > > > > > and > > > > > > >> >> AMQP > > > > > > >> >> > > > > > > >> >> On Wednesday, April 5, 2017, Dominik Przybysz < > > > > > [email protected]> > > > > > > >> >> wrote: > > > > > > >> >> > Hi, > > > > > > >> >> > Messaging is `must have` in microservices world, so... > > > > > > >> >> > Is there any framework for using JMS (or AMQP) with OSGi? > > > > > > >> >> > Do you think we should create something like > jms-whiteboard > > > in > > > > > > aries? > > > > > > >> >> > > > > > > > >> >> > -- > > > > > > >> >> > Pozdrawiam / Regards, > > > > > > >> >> > Dominik Przybysz > > > > > > >> >> > > > > > > > >> >> > > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > > > >> > -- > > > > > > >> > Pozdrawiam / Regards, > > > > > > >> > Dominik Przybysz > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> -- > > > > > > >> Pozdrawiam / Regards, > > > > > > >> Dominik Przybysz > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > *Raymond Augé* <http://www.liferay.com/web/ra > ymond.auge/profile> > > > > > > > (@rotty3000) > > > > > > > Senior Software Architect *Liferay, Inc.* < > > http://www.liferay.com> > > > > > > > (@Liferay) > > > > > > > Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> > > > > > > > (@OSGiAlliance) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > > > > > > (@rotty3000) > > > > > > Senior Software Architect *Liferay, Inc.* < > http://www.liferay.com> > > > > > > (@Liferay) > > > > > > Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> > > > > > > (@OSGiAlliance) > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Pozdrawiam / Regards, > > > > > Dominik Przybysz > > > > > > > > > > > > > > > > > > > > > -- > > > > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > > > > (@rotty3000) > > > > Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> > > > > (@Liferay) > > > > Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> > > > > (@OSGiAlliance) > > > > > > > > > > > > > > > > -- > > > -- > > > Christian Schneider > > > http://www.liquid-reality.de > > > <https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba5 > > > 2bd062c5a7e46&URL=http%3a%2f%2fwww.liquid-reality.de> > > > > > > Open Source Architect > > > http://www.talend.com > > > <https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba5 > > > 2bd062c5a7e46&URL=http%3a%2f%2fwww.talend.com> > > > > > > > > > > > -- > > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > > (@rotty3000) > > Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> > > (@Liferay) > > Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> > > (@OSGiAlliance) > > > > > > -- > Pozdrawiam / Regards, > Dominik Przybysz > -- ------------------------ Guillaume Nodet
