My two cents,
As we do today, I am thinking you need to have configs out of the box that can be
started.
Production
Development
Maybe even JMS
or WS
or....
I think prepackaged tested configs are a good idea as one size will not fit all. We have
done this for a long time and am wondering out loud why that notion would be removed?
Jim Tyrrell
Senior JBoss Solutions Architect
Did you see RHT on CNBC's Mad Money?
http://www.cnbc.com/id/39401056
On Apr 26, 2011, at 7:39 AM, ssilvert(a)redhat.com wrote:
Quoting Jaikiran Pai <jpai(a)redhat.com>:
> Thinking a bit more about this, I don't see any use of supporting
> exploded deployments (out of the box) if we don't support dynamic
> changes to .jsps (out of the box). What else can be changed dynamically
> in an exploded deployment?
xhtml (Facelets) pages can behave the same as JSP's as long as you are
in development mode.
>
> -Jaikiran
> On Tuesday 26 April 2011 04:52 PM, Remy Maucherat wrote:
>> On Tue, 2011-04-26 at 16:40 +0530, Jaikiran Pai wrote:
>>>> The better default will now be used: development will remain as
"false".
>>> IMO, before going to production with the server, any developer/team
>>> would go through a development phase in which he would definitely like
>>> this feature. So having this turned on by default (atleast in standalone
>>> mode), IMO, makes sense.
>>>
>>> P.S: I created
https://issues.jboss.org/browse/AS7-659 and was about to
>>> send out a pull request with a patch, before I saw this reply. If
>>> there's any objection to this change, then I'll wait for a resolution
on
>>> this discussion.
>>
>> I have rejected the jira.
>>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev