<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 29, 2016 at 11:31 AM, Lukas Fryc <span dir="ltr"><<a href="mailto:lfryc@redhat.com" target="_blank">lfryc@redhat.com</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">Hi guys,<div><br></div><div>in order to support WildFly 10+, that replaced HornetQ with ActiveMQ Artemis,</div><div><br></div><div>we will have to change:</div><div><br></div><div><ul><li>WEB-INF/hornetq-jms.xml (primarily schema change, file rename would be nice too, though it is not needed: *-jms.xml)<br></li><li>jms-setup-wildfly.cli (again, subsystem addresses reflect hornetq->activemq project rename, but stays compatible otherwise)<br></li></ul></div><div><br clear="all"><div>But that also means either:</div><div><br></div><div><ul><li>we will have to package WAR specific to WildFly 10+,</li><li>or rather we should refrain from using *-jms.xml (bundled in WAR) and use the pre-configured message queues instead (i.e. add bunch of "jms-queue" add commands to jms-setup-wildfly.cli file)</li><ul><li>since we will make user to use that CLI batch file anyway (starting with 1.2), I don't see a reason why not to include queues in CLI config instead of WAR</li></ul></ul></div></div></div></blockquote><div>+1 Let's not ship yet another WAR flavor </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>WDYT?</div></div><div><br></div><div><br></div><div>Cheers!</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>~ Lukas</div>
</font></span></div></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" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div></div>