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

[Dimitris Andreadis]

Has anyone measured what is the true overhead of enabling it by default, anyway?

On 27/05/2011 15:27, David M. Lloyd wrote:
> On 05/27/2011 06:39 AM, Remy Maucherat wrote:
>> On Fri, 2011-05-27 at 16:59 +0530, Jaikiran Pai wrote:
>>> Just to reiterate, I don't mind disabling this flag by default, if
>>> there's a real valid reason for that. So far, I haven't seen any.
>>
>> Bad performance + different behavior = it won't get in.
>>
>> Now, I would have some sympathy if JSP was not being singled out among
>> the equivalent technologies, which are all running in production mode,
>> because you happen to use that for you hack testing. So change the
>> configuration, move on with your work, and stop wasting both of our
>> time. Thanks.
>>
>> I'm ok if someone proposes a "master" development flag BTW.
>
> I may be wrong, but I believe that JSP is singled out because every
> other resource type (other than classes of course) already behaves this
> way when you have an exploded deployment.