[jboss-jira] [JBoss JIRA] Resolved: (JBAS-5453) Make DeleteWorkDirOnContextDestroy=true the default setting

[Remy Maucherat (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Remy Maucherat resolved JBAS-5453.
----------------------------------

    Fix Version/s: JBossAS-5.0.0.CR2
       Resolution: Rejected


JBAS-3358 specifically advocates the opposite default is better (configurability was added so that the work dir would not get deleted). However, I found out during testing that DeleteWorkDirOnContextDestroy was not doing anything in the current build, so I fixed it and things are now back to leaving the work dir alone by default, and being configurable.

Please have the new default signed off by Scott if you are going to reopen this JIRA. Thanks.

> Make DeleteWorkDirOnContextDestroy=true the default setting
> -----------------------------------------------------------
>
>                 Key: JBAS-5453
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5453
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-5.0.0.Beta4
>            Reporter: Mike Millson
>            Assignee: Remy Maucherat
>             Fix For: JBossAS-5.0.0.CR2
>
>
> JBAS-3358 added the DeleteWorkDirOnContextDestroy property to handle use cases that require the work directory not be deleted on context destroy. This includes cases where it is desired to persist session data between restarts/redeploys and cases where customers do not precompile JSPs and no not want previously compiled JSPs to be recompiled after a restart/redeploy.
> However, this default setting is causing issues with enterprise users deploying applications that have gone through long quality assurance and user acceptance testing cycles. JSP files will at times necessarily be created earlier than the compilation time of JSPs from older versions of the application that are running in production. Also, sometimes it is necessary to roll back an older version of an application in an emergency. The current default setting causes stale JSPs to be served. 
> Also, enterprise uders often run a clustered configuration, where the concept of saving the session locally in the work directory likely does not apply.
> Precompiling JSPs is ultimately the best solution; however, many users are still not doing this. My guess is there are more users relying on stale JSPs not being served than session persistence across restarts.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira