From: "denstar" <valliantster(a)gmail.com&gt; To: "JBoss AS7 Development" <jboss-as7-dev(a)lists.jboss.org&gt; Sent: Tuesday, April 26, 2011 1:29:53 PM Subject: [jboss-as7-dev] default configurations (was: Re: Changes to .jsp in an exploded deployment no longer picked up?) Is AS7 targeting developers or admins?

Developers and admins have a slew of different, and many times opposing, concerns. Take exploded vs. unexploded. As a dev, "explode away!". As an admin, "wrap that sucker up into one file, por favor". If we're going to choose one to target, "out of the box", which is it going to be? I'd rather not choose, and instead offer options... but what are options without defaults? "A lot of work." ba dum dum. Why not offer well documented, pre-baked configurations? Something a bit more fine grained than "nothing" and "everything" and "web"?. Eh. I dunno. Guess JBoss tuning is sorta a profession in itself, neh... Do we really want to change that? ;) I guess making standalone the "development" config is o.k., but somehow it sorta bugs me too. Something about polluting the difference between standalone and domain, which I don't think is so much about internal deployment options, as it is about external deployment stuff, if that makes sense. I'm a total newb to AS7, so, take it with a grain of salt. :Den -- The world is a perpetual caricature of itself; at every moment it is the mockery and the contradiction of what it is pretending to be. George Santayana _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev