[lmonaco]

Hi
I have been using MyEclipse for a few months now and as of today am having the following problem:
Changes made to a file are not being pushed to the server.

What has happened is this:
View a jsp page on my server
I made a change to a Java file,
stopped the server,
re-deployed
started the server
Viewed the same jsp page on my server – no changes are evident!!
this has happened with a couple of files now, eventhough i have made thousands of saves, redeployments etc to jsp’s java files, etc.

Can anyone tell me what I might havce done to the file or my settup to cause this problem??

My Setup :
MyEclipse running on Windows XP with
Apache Tomcat server , Mysql DB
— thanks in advance – lmonaco

[rmcvay]

Since you only mention a JSP page, this could be caused by browser caching, which we’ve found to be rampant in the built in browser. Pull up the seemingly unchanged page and to a shift-refresh to see if it changes.

[lmonaco]

hi rmcvay
thanks for replying so fast. actually it has occurred with both .jsp files and .java files.
i have refreshed, cleared cache, and even tried browsers which have not viewed the page before.
also i checked in the Apache roots deployment directory and the file seems to be updated there…
any ideas?
might it be an apache server cache issue?

@rmcvay wrote:

Since you only mention a JSP page, this could be caused by browser caching, which we’ve found to be rampant in the built in browser. Pull up the seemingly unchanged page and to a shift-refresh to see if it changes.

[rmcvay]

I guess it could actually be a Tomcat issue. I’ve seen times when WebSphere wouldn’t recognize a JSP was newer than its class file so I think that’s kind of a general web container hiccup. Now in the case of WAS we would just leave it running and push the changes out. There was also a reload time interval involved. I’d definitely look into Tomcat configuration items related to servlet caching, though.

[lmonaco]

thanks – will do.
ive looked throgh the server configuration within the IDE and not seen anything related to that. should i be able to change the servlet configuratio there? or somewhere else?
thanks again

@rmcvay wrote:

I guess it could actually be a Tomcat issue. I’ve seen times when WebSphere wouldn’t recognize a JSP was newer than its class file so I think that’s kind of a general web container hiccup. Now in the case of WAS we would just leave it running and push the changes out. There was also a reload time interval involved. I’d definitely look into Tomcat configuration items related to servlet caching, though.

[rmcvay]

I’m not sure of the built in Tomcat. I think I’ve seen the ME guys here say it’s sort of stripped down. Even the full up release doesn’t have the admin app bundled. The built in Tomcat should work as you expect IMHO.

[Author]

Posts