|Re: reloading issues [message #206330 is a reply to message #206163]
||Wed, 02 January 2008 17:22
| Larry Isaacs
Registered: July 2009
Kent Tong wrote:|
> I am using Eclipse Europa JEE edition configured to use Tomcat 6.0. Several
> 1) The menu commands such as Start, Stop or Restart on my webapp are all
> grayed out in the Servers window. Any idea why? I've tried setting auto
> reload to false for the webapp but those commands are still disabled.
This is normal. The "server framework" in WTP supports starting,
stopping, and restarting servers, but not individual projects added to
the server. You will need to select a server to enable these commands,
assuming I'm correct that you have an added project selected in the
> 2) What is the best way to show a jsp page in a web browser window in
> without restarting Tomcat? Choosing "Run on server" seems to force
> Tomcat to restart. I currently use "Open With | Others | Web Browser" but
> it is quite far away.
It also isn't practical for WTP to track Tomcat's internal webapp
reloads, so WTP will assume a restart is needed if a class or jar
changes. If Tomcat is configured to reload the webapp after the publish
operation has copied the changes, you can ignore the Tomcat restart. It
should be noted that it is easy for old webapps to leak after reloads,
so depending on how much heap you have configured, you may be forced to
restart after some number of reloads eats up the memory. If you only
change a JSP, it shouldn't say a restart is needed.
> 3) If I have a jsp page currently open in a web browser window in Eclipse,
> how to refresh it using GET instead of POST? Clicking on the URL bar and
> pressing enter seems to always cause a POST.
A simple test verified I see GET used by default. However, if you are
using the internal browser, the last time I checked (on Windows), it
appeared to create a single browser session. This means that when you
first display the internal browser, it creates a new browser session.
When you close the Browser view, it merely hides the window, but doesn't
close the session. I've observed this when using Basic authentication.
After authenticating, closing, and then reopening the browser window,
it will continue to send the headers for the original authentication,
indicating the original session is still in effect. The only way I've
found to start a new session with the internal browser is to start a new
Eclipse session. My guess is that the URL has somehow been cached as a
POST, perhaps for the duration of your Eclipse session.
> 4) Sometimes changes to the attribute of a JSF tag in a jsp page fails to
> take effect, even after restarting Tomcat. I have to clean the module
> work directory. Any idea why?
Might be related to session persistence. Stopping Tomcat, deleting the
*.ser file from the work directory, and restarting would confirm this.
Powered by FUDForum
. Page generated in 0.01591 seconds