| Tomcat publishing problems with WTP / Eclipse 3.2/Callisto [message #175429] |
Wed, 26 July 2006 02:50  |
Eclipse User |
|
|
|
Originally posted by: gregp777.gmail.com
Hi Everyone,
I am using various versions of Eclipse w/ WTP (WTP 1.0 and Eclipse3.1 and
3.2) on 3 different computers. In all machines I am using tomcat 5.5
embedded in eclipse with "Run all modules directly from the workspace"
checked. I view my local tomcat server using firefox. On the computer in
which I have the newest version of eclipse (callisto 3.2 w/WTP) my JSPs
and my stylesheets aren't immediately refreshable in my web browser upon
save/modification. I have to wait for the "INFO: Reloading this Context
has started" message to show up, and then my JSP and stylesheet changes
are live in my tomcat instance. This is a very fast computer (dual amd
4200+) and yet this redeployment/publishing can take more than 10 seconds,
and so it can be quite a nuisance. Is there some configuration setting I
am missing or that is new in the WTP1.5 that forces a reload on .jsp
changes? In my older versions of eclipse, I am able to save the jsp and
refresh instantly. JSP saving also does not trigger context reloading. Any
insight here would be much appreciated.
Thank you,
Greg
|
|
|
| Re: Tomcat publishing problems with WTP / Eclipse 3.2/Callisto [message #175457 is a reply to message #175429] |
Wed, 26 July 2006 09:34  |
| Eclipse User |
|
|
|
Originally posted by: w.f.voogd.planet.nl
I've experienced the same problem (see my thread: bypass publishing to
tomcat?), I don't know whether it was better in WTP1.0 since i haven't
used that version, but it seems that the publish mechanism walks through
the entire tree in order to see if anything changed. That means the time
to publish is getting greater if your project is getting bigger. I
believe this is worked on for WTP 2.0 In the meantime, i use the Sysdeo
tomcat plugin which lets you configure your context file for tomcat
point directly to your webapp, so there is no publish delay. You can
still use all of WTP editors using sysdeo, in fact my project is a WTP
and a Sysdeo Tomcat project simultaneously, so whenever the publishing
delay is fixed, i can switch right back. The only problem i'm having now
is that i cant debug the jsp files, but i can debug the generated
*_jsp.java files...
I hope this helps you some,
cheers,
Willem
Truth schreef:
> Hi Everyone,
>
> I am using various versions of Eclipse w/ WTP (WTP 1.0 and Eclipse3.1
> and 3.2) on 3 different computers. In all machines I am using tomcat 5.5
> embedded in eclipse with "Run all modules directly from the workspace"
> checked. I view my local tomcat server using firefox. On the computer in
> which I have the newest version of eclipse (callisto 3.2 w/WTP) my JSPs
> and my stylesheets aren't immediately refreshable in my web browser upon
> save/modification. I have to wait for the "INFO: Reloading this Context
> has started" message to show up, and then my JSP and stylesheet changes
> are live in my tomcat instance. This is a very fast computer (dual amd
> 4200+) and yet this redeployment/publishing can take more than 10
> seconds, and so it can be quite a nuisance. Is there some configuration
> setting I am missing or that is new in the WTP1.5 that forces a reload
> on .jsp changes? In my older versions of eclipse, I am able to save the
> jsp and refresh instantly. JSP saving also does not trigger context
> reloading. Any insight here would be much appreciated.
>
> Thank you,
> Greg
>
>
|
|
|
| Re: Tomcat publishing problems with WTP / Eclipse 3.2/Callisto [message #175623 is a reply to message #175457] |
Thu, 27 July 2006 18:56 |
| Eclipse User |
|
|
|
Originally posted by: tgalati.nospam-naic.org
I don't know if this will help but maybe a -VMArgs adjustment within your
server configuration?
for example double click your server inside eclipse click "open launch
configuration".
Click on the arguements tab and enter the following code.
Under VM args at the bottom enter the following code
-vmargs -Xmx256m
Or change 256 to what you want. 256 is the number of megs of ram to
allocate to the javaw.exe
It might help, might not... give it a try.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03494 seconds
] 
Search
Help
Register
Login
Home
