Peter Johnson wrote:1) Have you turned off the hot deployer? Or changed the hot deployer settings in any way?
We have not turned off the hot deployer and we have not changes any settings
2) Are you certain that the timestamp on the updated WAR is more recent than the timestamp that was on the previous WAR?
Yes..But the customized files contains in a jar file and not in war file..So the deploy directory has 1 war file and 1 jar file
3) Are you certain that you placed the new WAR in the correct location? That is, in the deploy directory of the running configuration?
Yes
4) Have you added any external deploy directories?
No
5) What version of JBoss AS? (I know you are going to ask questions about my questions, like "what file is xxx in?", and if I know the version of JBoss AS I can give specific answers.)
Mark E Hansen wrote:If you deploy your application as a .war file to the server's deploy directory, you shouldn't have to do anything other than just copy a new version of the .war file to the server's deploy directory. The entire application should get re-deployed at that time (within a few seconds, anyway).
If this isn't happening, that's a problem. Perhaps you can describe what's actually going wrong with your application?
Peter Johnson wrote:You need to provide a very detailed description of how the customizations are defined in the JAR file and how they are picked up by the WAR file. I can think of several reasons why this will not work, but then all of those reasons are based on assumptions of the customization mechanism. A concrete example of one of the customizations, both how declared in the JAR and how accessed in the WAR, would be helpful.
Peter Johnson wrote:A concrete example of one of the customizations, both how declared in the JAR and how accessed in the WAR, would be helpful.
Consider Paul's rocket mass heater. |