Hi Isuru, Thanks for the reply.
STRATOS-616 was really an enabler for making deb/rpm packages easier. However, if my investigation into providing docker images for Stratos is successful [1], AMQP won't be so important for me. Dinesh may benefit from AMQP when writing the python based agent (unless he uses ActiveMQ STOMP). Cheers, Chris --- [1] http://mail-archives.apache.org/mod_mbox/incubator-stratos-dev/201407.mbox/%3CCAGWifGL%3DzL%3DvYCqQ-baXx5Fu1eh6h-HXtG%3DZ0b6o%2B_i79aiTuw%40mail.gmail.com%3E On Sat, Jul 5, 2014 at 12:27 AM, Isuru Perera <isu...@wso2.com> wrote: > Stratos uses JMS APIs. We have never used AMQP specific APIs in Java. > > Yes, implementing STRATOS-616 will not be easy. > > This is just a quick reply. Let's see how we can solve this. > > > On Fri, Jul 4, 2014 at 1:38 PM, chris snow <chsnow...@gmail.com> wrote: >> >> I was under the impression that Stratos uses AMQP, but looking >> through the classes for in the org.apache.stratos.messaging.broker >> package I see lots of javax.jmx.* imports. >> >> Has Stratos ever used AMQP, or has it always used JMS? >> >> If it has always used JMS, I'm expecting that it will make the JIRA >> STRATOS-616 [1] much harder to implement. >> >> Many thanks, >> >> Chris >> >> --- >> [1] https://issues.apache.org/jira/browse/STRATOS-616 > > > > > -- > Isuru Perera > Senior Software Engineer | WSO2, Inc. | http://wso2.com/ > Lean . Enterprise . Middleware > > about.me/chrishantha
