<div dir="ltr"><div>Hi James,</div><div>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.</div><div>
</div><div>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.</div>
<div> </div><div>Regards,</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 10, 2014 at 3:37 AM, James R. Perkins <span dir="ltr"><<a href="mailto:jperkins@redhat.com" target="_blank">jperkins@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">For the wildfly-maven-plugin I've written a simple class to launch a<br>
process that starts WildFly. It also has a thin wrapper around the<br>
deployment builder to ease the deployment process.<br>
<br>
I've heard we've been asked a few times about possibly creating a Gradle<br>
plugin. As I understand it you can't use a maven plugin with Gradle. I'm<br>
considering creating a separate bootstrap(ish) type of project to simple<br>
launch WildFly from Java. Would anyone else find this useful? Or does<br>
anyone have any objections to this?<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
James R. Perkins<br>
JBoss by Red Hat<br>
<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</font></span></blockquote></div><br></div>