<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">The thing needs distribution tooling to
      setup different configurations.<br>
      <br>
      As for support, we'll support combinations that are actual
      products.<br>
      <br>
      Carlo<br>
      <br>
      On 02/24/2014 03:10 AM, Stuart Douglas wrote:<br>
    </div>
    <blockquote
cite="mid:CAAoo=c7rWYObqRGQN2g34PR0bdP6YLeFCaoi3E5f7PuMQkav7Q@mail.gmail.com"
      type="cite">
      <div dir="ltr">No, because that means we essentially have to
        support and test every possible combination that someone might
        select.
        <div><br>
        </div>
        <div>Stuart</div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">
          On Mon, Feb 24, 2014 at 7:13 AM, Misty Stanley-Jones <span
            dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:misty@redhat.com" target="_blank">misty@redhat.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            I know you guys aren&#8217;t there yet, but can we think about
            wrapping a GUI around this, so that the developer only needs
            to tick the boxes for what he does/doesn&#8217;t want, with
            dependencies sorted out automatically? Maybe some default
            profiles that select a group of things, but the ability to
            go in and add or remove individual subsystems as needed?
            Maybe this could be part of the installer but could
            optionally be run post-install as well.<br>
            <div>
              <div class="h5"><br>
                On Feb 22, 2014, at 2:01 AM, Brian Stansberry &lt;<a
                  moz-do-not-send="true"
                  href="mailto:brian.stansberry@redhat.com">brian.stansberry@redhat.com</a>&gt;
                wrote:<br>
                <br>
                &gt; When I said "Web" I meant the thing described on
                that wiki page Tomaz<br>
                &gt; linked:<br>
                &gt;<br>
                &gt; "Web<br>
                &gt;<br>
                &gt; Undertow subsystem, and all related dependencies,
                including a small<br>
                &gt; subset of EE and JNDI. This is basically just a
                Servlet container, and<br>
                &gt; will provide a platform for people that want to
                create web based<br>
                &gt; appliances or applications, and don't need all the
                additional<br>
                &gt; functionality that Wildfly provides. We should end
                up with something as<br>
                &gt; lightweight as Tomcat or Jetty, but with all our
                advanced management<br>
                &gt; functionality."<br>
                &gt;<br>
                &gt; On 2/21/14, 9:40 AM, Bill Burke wrote:<br>
                &gt;&gt; Its also "Web" minus some stuff. &nbsp;For my
                project I want just Servlet,<br>
                &gt;&gt; JAX-RS, JPA, and datasources. &nbsp; Its very very
                hard to figure out how to<br>
                &gt;&gt; remove a subsystem and all its associated
                modules.<br>
                &gt;&gt;<br>
                &gt;&gt; BTW, I think my maven artifact thing got into
                JBoss Modules. So it<br>
                &gt;&gt; would be possible to load jars on demand, or at
                least use it as a way to<br>
                &gt;&gt; figure out which modules aren't being used ;).<br>
                &gt;&gt;<br>
                &gt;&gt;<br>
                &gt;&gt; On 2/21/2014 10:22 AM, Brian Stansberry wrote:<br>
                &gt;&gt;&gt; This will move things in the right
                direction, but not all the way there<br>
                &gt;&gt;&gt; yet. Note the set of capabilities Bill
                mention: web, CDI, JAX-RS, JPA.<br>
                &gt;&gt;&gt; That sounds like our "Web" variant, plus
                some stuff. It's the easy "plus<br>
                &gt;&gt;&gt; some stuff" part that needs sorting at some
                point.<br>
                &gt;&gt;&gt;<br>
                &gt;&gt;&gt; On 2/21/14, 9:08 AM, Toma&#382; Cerar wrote:<br>
                &gt;&gt;&gt;&gt; Bill,<br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt; that is exactly idea we have in mind of
                9.<br>
                &gt;&gt;&gt;&gt; We already started with producing
                WildFly core distribution in that is<br>
                &gt;&gt;&gt;&gt; WildFly with no subsystems, upon which
                you can build you own wildfly.<br>
                &gt;&gt;&gt;&gt; It is only 15mb and contains whole mgmt
                capabilites (CLI, standalone,<br>
                &gt;&gt;&gt;&gt; domain,...) you can grab it at:<br>
                &gt;&gt;&gt;&gt; <a moz-do-not-send="true"
href="http://download.jboss.org/wildfly/8.0.0.Final/core/wildfly-core-8.0.0.Final.zip"
                  target="_blank">http://download.jboss.org/wildfly/8.0.0.Final/core/wildfly-core-8.0.0.Final.zip</a><br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt; For 9 we have plans to move things bit
                further and have decided that we<br>
                &gt;&gt;&gt;&gt; will also do split codebase for core,
                ee, web, .. and other distributions.<br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt; Current idea on code split up is here<br>
                &gt;&gt;&gt;&gt; <a moz-do-not-send="true"
                  href="https://community.jboss.org/wiki/SplittingUpTheWildflyCodeBase"
                  target="_blank">https://community.jboss.org/wiki/SplittingUpTheWildflyCodeBase</a><br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt; --<br>
                &gt;&gt;&gt;&gt; tomaz<br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt; On Fri, Feb 21, 2014 at 3:00 PM, Bill
                Burke &lt;<a moz-do-not-send="true"
                  href="mailto:bburke@redhat.com">bburke@redhat.com</a><br>
                &gt;&gt;&gt;&gt; &lt;mailto:<a moz-do-not-send="true"
                  href="mailto:bburke@redhat.com">bburke@redhat.com</a>&gt;&gt;
                wrote:<br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;On Resteasy list I have a few
                people "rolling their own app server"<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;using Netty, Weld, Resteasy and
                JPA. &nbsp;I asked one of them "I don't<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;understand why you are rolling
                your own app server" response:<br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;"It's actually a lot more
                lightweight. &nbsp;The minimum I can run the<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;equivalent on AS7 on is ~ 180 mb
                in binaries, but throwing this<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;together is about 32 mb (and
                compresses further when its packaged).<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;I'm able to start the JVM on the
                bare minimum (~100mb on my linux VM)<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;but AS7 with all I need is about
                756mb. &nbsp;When rolling out in the<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;cloud, where all of my REST APIs
                are stateless, running with this<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;configuration helps us get a lot
                more per node."<br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;I'm not complaining :), just
                something to think about. It might be<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;really valuable to focus a bit in
                Wildfly 9 to make it easier to create<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;custom profiles or even different
                packaging options for the app server<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;instead of the exploded style we
                currently have.<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;--<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;Bill Burke<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;JBoss, a division of Red Hat<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;<a moz-do-not-send="true"
                  href="http://bill.burkecentral.com" target="_blank">http://bill.burkecentral.com</a><br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp;
                &nbsp;_______________________________________________<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;wildfly-dev mailing list<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;<a moz-do-not-send="true"
                  href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
                &lt;mailto:<a moz-do-not-send="true"
                  href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>&gt;<br>
                &gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp;<a moz-do-not-send="true"
                  href="https://lists.jboss.org/mailman/listinfo/wildfly-dev"
                  target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt;
                _______________________________________________<br>
                &gt;&gt;&gt;&gt; wildfly-dev mailing list<br>
                &gt;&gt;&gt;&gt; <a moz-do-not-send="true"
                  href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
                &gt;&gt;&gt;&gt; <a moz-do-not-send="true"
                  href="https://lists.jboss.org/mailman/listinfo/wildfly-dev"
                  target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;<br>
                &gt;&gt;&gt;<br>
                &gt;&gt;<br>
                &gt;<br>
                &gt;<br>
                &gt; --<br>
                &gt; Brian Stansberry<br>
                &gt; Senior Principal Software Engineer<br>
                &gt; JBoss by Red Hat<br>
                &gt; _______________________________________________<br>
                &gt; wildfly-dev mailing list<br>
                &gt; <a moz-do-not-send="true"
                  href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
                &gt; <a moz-do-not-send="true"
                  href="https://lists.jboss.org/mailman/listinfo/wildfly-dev"
                  target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
                <br>
              </div>
            </div>
            Misty Stanley-Jones, RHCE<br>
            Manager, Content Services (Middleware)<br>
            Direct: <a moz-do-not-send="true"
              href="tel:%2B%2061%207%203514%208105" value="+61735148105">+
              61 7 3514 8105</a> / Mobile: <a moz-do-not-send="true"
              href="tel:%2B61%20429%20595%20932" value="+61429595932">+61
              429 595 932</a> &nbsp;(TZ: GMT+10)<br>
            IRC: misty (Freenode / RH)<br>
            <div class="HOEnZb">
              <div class="h5"><br>
                <br>
                _______________________________________________<br>
                wildfly-dev mailing list<br>
                <a moz-do-not-send="true"
                  href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
                <a moz-do-not-send="true"
                  href="https://lists.jboss.org/mailman/listinfo/wildfly-dev"
                  target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
wildfly-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></pre>
    </blockquote>
    <br>
  </body>
</html>