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

[Jason T. Greene]

On 4/26/11 10:49 AM, ssilvert at redhat.com wrote:
> Quoting Remy Maucherat<rmaucher at redhat.com>:
>
>> On Tue, 2011-04-26 at 09:46 -0500, David M. Lloyd wrote:
>>> It shouldn't be a global setting at all.  It should be per-deployment
>>> and it should default to "on" when there is exploded content and "off"
>>> otherwise.  In other words: the user should never even need to know
>>> about it.
>>
>> Ok, since I strongly disagree, I'll let you make that change.
>
> I also disagree, but for different reasons.  Whether or not you run in
> development mode should not depend on exploded/unexploded.  Some tools
> used in development would deploy unexploded.  Development mode is used
> for more than just hot deploy of JSP and Facelets.  It also determines
> what kind of error messages you see in the browser.  So even if a
> developer isn't interested in JSP/Facelets hot deploy he would
> certainly want to see the error detail that development mode provides
> in the browser.

It sounds like this setting does too much. I mean it would be really 
really silly to have a non-exploded deployment looking for jsp changes...

-- 
Jason T. Greene
JBoss, a division of Red Hat