Matthias,

Currently the changes required to make WildFly work in this way are part of WildFly Core and WildFly 9.

It might be possible to backport those changes to WildFly 8/EAP, but it's not something we've currently investigated

Ken

On Wed, Apr 29, 2015 at 6:19 AM, Ken Finnigan <ken@kenfinnigan.me> wrote:
Bob and I would welcome any additional ways to improve WildFly Swarm!

Bob's been working on the datasource connector only this week, and I think we're also looking at defaulting to H2 setup if an application doesn't provide details of a datasource.

There isn't currently a mailing list for the project, but by all means open github issues to discuss items.

Ken

On Wed, Apr 29, 2015 at 3:39 AM, Lukáš Fryč <lukas.fryc@gmail.com> wrote:
That's right, but we can always set it up in Main method by using client API and database connector.

Or improve Swarm to provide this functionality/hooks.

st 29. 4. 2015 v 9:21 odesílatel Erik Jan de Wit <edewit@redhat.com> napsal:

That would build a executable jar file containing everything, but we
would still need to setup a database right?

On Wed, Apr 29, 2015 at 8:48 AM, Lukáš Fryč <lukas.fryc@gmail.com> wrote:
> Morning guys,
>
> I came across WildFly-Swarm, seems it could be a simplification how to build
> appliance distribution from UPS war, isn't it?
>
> https://github.com/wildfly-swarm/wildfly-swarm
>
> Cheers,
>
> ~ Lukas
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Cheers,
       Erik Jan

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev