Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » Difference between autopublish and autoload?
Difference between autopublish and autoload? [message #757118] Wed, 16 November 2011 10:04 Go to next message
Breako Missing name is currently offline Breako Missing name
Messages: 13
Registered: November 2011
Junior Member
Hi,
In the Servers Overview Tab there are options to:

1. Automatically publish when resources change.
2. Automatically publish after a build event.

In the Servers Modules Tab there is options to auto reload.

What is the difference between auto-load and auto-publishing?

Thanks
Re: Difference between autopublish and autoload? [message #757132 is a reply to message #757118] Wed, 16 November 2011 11:52 Go to previous messageGo to next message
Breako Missing name is currently offline Breako Missing name
Messages: 13
Registered: November 2011
Junior Member
I have half the answer!

This is exactly what auto - load does.

If auto - load for a specific module is true, the corresponding value for reloadable in the corresponding context (for the module) is the server.xml is true. Similarly for false.

If reloadable is set to true, it causes Tomcat to check for class changes in the WEB-INF/classes/ and WEB-INF/lib directories. If these classes have changed, the application owning these classes will automatically be reloaded. This feature should only be used during development. This setting will cause severe performance degradation, and therefore should be set to false when in a production environment.


Re: Difference between autopublish and autoload? [message #757139 is a reply to message #757132] Wed, 16 November 2011 12:25 Go to previous message
Breako Missing name is currently offline Breako Missing name
Messages: 13
Registered: November 2011
Junior Member
Ok - changing anything to do with auto publishing will change configuration values in the server.xml. Not the tomcat server.xml, but the other server.xml in .metadata\.plugins\org.eclipse.wst.server.core.

This means your changing WTP behaviour as opposed to Tomcat behaviour.

So the question really is how to these properties relate to WTP behaviour. I might put this in a separate thread.

Re: Difference between autopublish and autoload? [message #757915 is a reply to message #757118] Wed, 16 November 2011 10:58 Go to previous message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1303
Registered: July 2009
Senior Member
On 11/16/2011 10:04 AM, Breako wrote:
> Hi,
> In the Servers Overview Tab there are options to:
>
> 1. Automatically publish when resources change.
> 2. Automatically publish after a build event.
>
> In the Servers Modules Tab there is options to auto reload.
>
> What is the difference between auto-load and auto-publishing?
>
> Thanks
>

The "auto-publishing" refers to the WTP behavior of automatically
publishing changes to your project to the Tomcat server. If the server
is running, the impact on the server will vary depending on what is
changing.

The "auto-reload" refers to the Tomcat feature of being able to detect
changed resources in the served webapp and reloading the webapp so those
changes can become "visible". For example, a change to a servlet class
or the web.xml will trigger such a reload so the changes take effect.

Note that such a change will typically cause the Servers view to show
that the Tomcat server needs to "Restart". If the "reload" works, you
may be able to ignore the "Restart". Unfortunately, explaining what
works and doesn't work with respect to "reloading" isn't practical to
describe. If the "Restart" takes too long, you just have to experiment
with your use cases to determine what kinds of changes allow you to skip it.

Cheers,
Larry
Previous Topic:What exactly does "update context paths" mean?
Next Topic:"Hot overlay" in m2e
Goto Forum:
  


Current Time: Wed Jul 30 23:24:14 EDT 2014

Powered by FUDForum. Page generated in 0.06500 seconds