Hi Erik,

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:

-------------------------------------------------------------------------------------------

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:

bean-validation
ee
io
jaxrs
logging
naming
request-controller
security
transactions
undertow
weld

-----------------------------------------------------------------------------------------

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.

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.

Cheers
Raimund

2015-04-29 13:44 GMT+01:00 Erik Jan de Wit <edewit@redhat.com>:
Maybe use wildfly swarm [1] and 'just' manage the process?

[1] https://github.com/wildfly-swarm/wildfly-swarm

On Wed, Apr 29, 2015 at 12:05 PM, Raimund Klein <chessray77@gmail.com> wrote:
> Hi everyone,
>
> We are considering the use of the AeroGear Unified Push Server in our
> current project, but I'm afraid there will be quite some resistance against
> using the WildFly or JBoss EAP servers in our environments (and no, we don't
> have Docker yet, either - I'm trying to push for that on another line, but
> there are even more stakeholders involved...). So far, our infrastructure
> team supports only another application server.
>
> How deep are the links between the application and the server? I briefly
> talked to Matze after this JAX talk last week and he mentioned that there
> are direct uses of HornetQ. Is that the only restriction, and how heavily is
> this used? Are there plans to make this tie-in optional?
>
> Please excuse all these questions, but they're only some of the problems I'm
> facing in pushing this forward. I would really like to use it in order to
> reduce the headaches I had over the past months, but in a bigger
> organisation you have more people asking this kind of thing. ;-)
>
> Cheers
> Raimund
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>



--
Cheers,
       Erik Jan
_______________________________________________
Aerogear-users mailing list
Aerogear-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-users