<div dir="ltr">Hi Erik,<div><br></div><div>Thank you for the suggestion. Please excuse the stupid question, but I assume this means I'd have to pack my own artifact based on the released sources? In this case, I'm a bit concerned about this part of the swarm (which I haven't heard of before) documentation:</div><div><br></div><div>-------------------------------------------------------------------------------------------</div><div><br></div><div><div>In order to specify the portions of the Wildfly AS your application needs, your pom.xml should specify some of the following dependencies within the org.wildfly.swarm Maven group-id:</div><div><br></div><div>bean-validation</div><div>ee</div><div>io</div><div>jaxrs</div><div>logging</div><div>naming</div><div>request-controller</div><div>security</div><div>transactions</div><div>undertow</div><div>weld</div></div><div><br></div><div>-----------------------------------------------------------------------------------------</div><div><br></div><div>Since this would be my first contact with AeroGear, I have no idea which of these is required by the server. I'd probably just resort to including all of the above.</div><div><br></div><div>I'm not sure if I could "sell" this solution to the other project stakeholders, but unless someone has a better idea (or can give me a hint as to how much Wildfly there really is inside the Unified Push Server), I'll have to give it a try.</div><div><br></div><div>Cheers</div><div>Raimund</div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-04-29 13:44 GMT+01:00 Erik Jan de Wit <span dir="ltr"><<a href="mailto:edewit@redhat.com" target="_blank">edewit@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Maybe use wildfly swarm [1] and 'just' manage the process?<br>
<br>
[1] <a href="https://github.com/wildfly-swarm/wildfly-swarm" target="_blank">https://github.com/wildfly-swarm/wildfly-swarm</a><br>
<div><div class="h5"><br>
On Wed, Apr 29, 2015 at 12:05 PM, Raimund Klein <<a href="mailto:chessray77@gmail.com">chessray77@gmail.com</a>> wrote:<br>
> Hi everyone,<br>
><br>
> We are considering the use of the AeroGear Unified Push Server in our<br>
> current project, but I'm afraid there will be quite some resistance against<br>
> using the WildFly or JBoss EAP servers in our environments (and no, we don't<br>
> have Docker yet, either - I'm trying to push for that on another line, but<br>
> there are even more stakeholders involved...). So far, our infrastructure<br>
> team supports only another application server.<br>
><br>
> How deep are the links between the application and the server? I briefly<br>
> talked to Matze after this JAX talk last week and he mentioned that there<br>
> are direct uses of HornetQ. Is that the only restriction, and how heavily is<br>
> this used? Are there plans to make this tie-in optional?<br>
><br>
> Please excuse all these questions, but they're only some of the problems I'm<br>
> facing in pushing this forward. I would really like to use it in order to<br>
> reduce the headaches I had over the past months, but in a bigger<br>
> organisation you have more people asking this kind of thing. ;-)<br>
><br>
> Cheers<br>
> Raimund<br>
><br>
</div></div>> _______________________________________________<br>
> Aerogear-users mailing list<br>
> <a href="mailto:Aerogear-users@lists.jboss.org">Aerogear-users@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-users" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-users</a><br>
><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
Cheers,<br>
Erik Jan<br>
_______________________________________________<br>
Aerogear-users mailing list<br>
<a href="mailto:Aerogear-users@lists.jboss.org">Aerogear-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-users" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-users</a><br>
</font></span></blockquote></div><br></div>