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

[Pete Muir]

I know this thread, but I think it's worth correcting a misconception here.

On 26 Apr 2011, at 08:17, Remy Maucherat wrote:

> On Tue, 2011-04-26 at 13:49 +0200, Max Rydahl Andersen wrote:
>> You would rather have the server out of the box be TCK compliant
>> than usable for development ? I thought we were pass the mistakes
>> made in latest AS and EAP being targeted purely for production ?
> 
> The dev scenario I described using a marker (or the equivalent API call
> to trigger a redeploy) seems far more sustainable, even if it takes a
> bit more time (framework init, etc).

Application developers do not care about sustainability. They care about turnaround and development time.

Operations guys care about sustainability.

This update-without-redeploy stuff is really important, and I've seen this misunderstanding before with concerns like "well the update will not always succeed" - in development this does not matter one bit. If it the update fails, you simply restart the AS and it starts working again.