[pandutalli]

Hi,

When i deploy in Exploded mode and the server is running, I am unable to redeploy after adding a new method, I am forced to stop the server and do the redeploy, I observed struts.jar is locked. However, when i deploy in Packaged mode i am able to undeploy, deploy or redeploy without stopping the server and the changes (new methods that are added) are reflected, i am kind of confused which Mode i should use? it seems if i use Packaged mode i can modify the code (add new methods) and doesn’t have to stop the server. With this observation I think Packaged benefits than Exploded? Am I correct?

[Riyad Kalla]

This is sometimes confusing. Actually you usually want to use exploded. What happens is as soon as you save the file, it is synchronized to the server. In the case of a class file IF the change is within the acceptable bounds of the hot-sync spec, it is actually injected into the running VM and you can see your changes *instantly*. Otherwise you can optionally setup Tomcat to reload the web context when a file changes (I think it’s on by default) and with JSP pages, since the changes are copied out on save, just switch over to the browser and hit refresh and you’ll see your changes.

[pandutalli]

Hi Riyad,

With Exploded i can’t redeploy if i add a new method to the code and this new method is not visible without doing a redeploy, however with Packaged i can redeploy and the method is visible.

Rao

[Riyad Kalla]

Rao,
I know. I guess I didn’t explain this well, you need to set Tomcat’s context to reloadable and you do *not* need to keep redeploying when using an exploded deployment, it’s done for you automatically.

[pandutalli]

Hi Riyad,

I am sorry, where do i set Tomcat’s context to reloadable?

Rao

[Riyad Kalla]

If you drill down into the Tomcat directory, under conf/localhost, then find the context XML file, and for the root <context> tag, there is a parameter called reloadable that you want to set to true:

reloadable="true"

[Author]

Posts