[jboss-as7-dev] Changes to .jsp in an exploded deployment no longer picked up?

Tue Apr 26 10:46:11 EDT 2011

From: "Jim Tyrrell" <jtyrrell at redhat.com> 
To: "jboss-as7-dev at lists.jboss.org Development" <jboss-as7-dev at lists.jboss.org> 
Sent: Tuesday, April 26, 2011 7:56:11 AM 
Subject: Re: [jboss-as7-dev] Changes to .jsp in an exploded deployment no longer picked up? 

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? There is a requirement in the PRD to have a development configuration and a production configuration, but that is specific to EAP. Traditionally, we have made the AS distribution more "development" focused out-of-the-box. 

I'm not sure, in this specific case what is the best option, but EAP will have a production and development configuration (perhaps a script that sets things up for either using the management API). 

Andy 

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 at redhat.com wrote: 

Quoting Jaikiran Pai < jpai at 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 at lists.jboss.org 

https://lists.jboss.org/mailman/listinfo/jboss-as7-dev 

_______________________________________________ 
jboss-as7-dev mailing list 
jboss-as7-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev 

_______________________________________________ 
jboss-as7-dev mailing list 
jboss-as7-dev at lists.jboss.org 
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20110426/a7ea04a9/attachment.html 