<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 25, 2015 at 7:55 AM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">+1 I am fully supporting that - I actually think it is a mistake that we did not have that done in the past (mainly due to the full profile usage - I can't figure out if that actually made sense...)</div></blockquote><div><br>Well there is a LOT of bias against full profile Java EE containers because they were big slow lumbering jacktards of projects for a very long time. Wildfly's name change REALLY did a good job in distancing itself from that perception. I've even heard people use the term "lightweight" to describe it.<br><br></div><div>So it was probably just not wanting to assume the emotional baggage of being on a Java EE Profile because that was "heavyweight" in out minds.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div class="gmail_quote"><div><div class="h5">On Wed, Mar 25, 2015 at 11:25 AM, Lukáš Fryč <span dir="ltr"><<a href="mailto:lukas.fryc@gmail.com" target="_blank">lukas.fryc@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hey guys,<div><br></div><div>we are working on a prototype of UPS that is leveraging JMS to send notifications to Push Networks.</div><div><br></div><div>The requirement of JMS means we need to switch runtime requirement from WildFly web profile to WildFly full profile.</div><div><br></div><div>i.e.: wildfly> ./bin/standalone.sh -c standalone-full.xml</div><div><br></div><div><br></div><div><br></div><div><a href="https://issues.jboss.org/browse/AGPUSH-1321" target="_blank">https://issues.jboss.org/browse/AGPUSH-1321</a> - Enable JMS for notification sending<br></div><div><br></div><div><br></div><div>Essentially JMS should allow us to</div><div>* send notifications with higher confidence (per-message transaction guarantees)</div><div>* allow configuration of throughput and timeout (we get it for free)</div><div>* potentially it may even allow sending notifications in parallel in more threads or in a cluster of application servers (not an initial goal)</div><div><br></div><div>All of these benefits could be hardly achieved without messaging.</div><div><br></div><div>The feature request is elevated by AGPUSH-1320.</div><div><br></div><div>If you have any concerns, let us know!</div><div><br></div><div><br></div><div>Cheers,</div><div><br></div><div>~ Lukas</div><div><br></div></div>
<br></div></div>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><span class="HOEnZb"><font color="#888888"><br></font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div>
</font></span></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div></div>