This content has been marked as final. Show 7 replies
kalyan Pasupuleti wrote:But clean cache and tmp is not required for every time deployment.
But clean cache and tmp is not required for every time deployment.
if you think then avoid stage deployment and use nostate deployment that will help you.
The issue is when I do the deployment, the weblogic not change the file that I modified. Usually the file .watr contains file diferent than in the stage area (or tmp folder). Do you know what I mean?
What do you mean with "nostate deployment"?
I can't change the weblogic.xml because I must leave the weblogic.xml equal in all environments.
I will try explain with another words.
Every deploy I do, I must delete the directory /<FOLDERS>/tmp/_WL_user/<APP_DIR> and do again a deploy, if I not delete the <APP_DIR> the jsp files aren't updated.
Edited by: userOfJavaOracle on 06/11/2012 17:44
You can consider adding any of these parameters pageCheckSeconds of jsp-descriptor element and/or servet-reload-check-secs, resource-reload-check-secs of container-descriptor in your weblogic.xml file
The <resource-reload-check-secs> element is used to perform metadata caching for cached resources that are found in the resource path in the Web application scope. This parameter identifies how often WebLogic Server checks whether a resource has been modified and if so, it reloads it.
The value -1 means never reload. This is the default value in a production environment.
The value 0 means always reload.
The value 1 means reload every second. This is the default value in a development environment.
Values specified for this parameter using the Admin Console are given precedence.
Check more about it from the below link