Hi, for ticket "AEROGEAR-1222" ([1]) I looked a bit at JMS integration hooks. The JIRA has an updated description, and two SIMPLE "UML diagrams". Also, I created a branch that uses JMS for (GCM/APNs) based broadcast (more to follow later this week). Example: The HTTP enpoint for the "broadcast sender", publishes a JMS messages and immediately returns: https://github.com/matzew/pushee/blob/Messaging/src/main/java/org/aerogea... Yes, there is no guarantee at all, that the message really arrives the device (see Apple/GCM doc for details) Behind the sceneses, a "Consumer" is responsible to deliver the message to the network: https://github.com/matzew/pushee/blob/Messaging/src/main/java/org/aerogea... The code above performs all the "heavy" work ("blocking" JPA lookups and PushNEtwork Delivery).. We now should use the "standalone-full.xml" configuration, since that supports JMS. I double checked and the SimplePush/Netty Adapter are working fine here too.... also, for JMS (for now), we need to declare some JMS topics in the "standalone-full.xml" file More during the week, Matthias [1] http://jira.jboss.org/browse/AEROGEAR-1222 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf

On Mon, May 20, 2013 at 02:20:53PM +0200, Matthias Wessendorf wrote: > We now should use the "standalone-full.xml" configuration, since that > supports JMS. I double checked and the SimplePush/Netty Adapter are working > fine here too.... also, for JMS (for now), we need to declare some JMS > topics in the "standalone-full.xml" file The not-so-nice side effect of this is that now you need to carry a JMS server if you want to deploy this outside of a full-blown AS. Was this intended?

-- qmx _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev