[wildfly-dev] WildFly Bootstrap(ish)

[Peter Cai]

Hi James,
I believe that's where the core distribution of Wildfly comes in  ---  to
allow interested users to boot/extend wildfly as any type of server, not
merely EE container.

I do find this useful. In my previous project, we build a software to
distrbute fax to email. This software is running in different IDC across
Australia, where faxes are terminated from telcom network, and instances of
this software need to be managed and synchronized provision data from
central node.  If this piece of software has been equipped with Domain
Management features like Wildfly provides, it would have make our lives
much easier.

Regards,


On Tue, Jun 10, 2014 at 3:37 AM, James R. Perkins <jperkins at redhat.com>
wrote:

> For the wildfly-maven-plugin I've written a simple class to launch a
> process that starts WildFly. It also has a thin wrapper around the
> deployment builder to ease the deployment process.
>
> I've heard we've been asked a few times about possibly creating a Gradle
> plugin. As I understand it you can't use a maven plugin with Gradle. I'm
> considering creating a separate bootstrap(ish) type of project to simple
> launch WildFly from Java. Would anyone else find this useful? Or does
> anyone have any objections to this?
>
> --
> James R. Perkins
> JBoss by Red Hat
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20140610/eea0ca82/attachment.html