Those steps are correct if you want to start with a clean deployment.
Hot deployment is easy - simply copy the EAR file to the deploy directory. The app server will undeploy the old app and deploy the new one. There are various situations under which this will fail, mostly having to do with how your application attempts to maintain state and the fact that the new app will have a different class loader than the old app.
My rule-of-thumb. If hot deployment works, great. If not, do the steps you outlined (usually you do not need steps 3 and 4).
Thanks a lot for the reply. Hot deployment did not work in most of the cases. (Even though we are more interested in getting this work)
Until & unless step 3 & 4 are done, we still have issues once the new ear is deployed.
Do you know where else it extracts the war file when JBoss starts. I am facing another issue now. I removed all the tmp file & redeployed the new war. For some reason, it still picks the old release.
I removed the files from /tmp & /work
The WAR is extracted to tmp, the JSPs are compiled into work. There are no other locations.
You could try setting the -verbose:class option on the Java command line, this should let you know the location of the jar files for each class loaded, look at where your servlets are being loaded from. That might give you some clue as to why the old app is showing up.
Also, what kind of changes did you make? Sometime changes such as CSS or images don't get noticed because the browser caches them.