Community
Participate
Working Groups
Build Identifier: Platform 3.6 Run on Server (RoS) a webpage on a server. See it open in the embdeeded browser. Change the JSP and do a RoS. A new browser window opens but the content is old. Need to reload the page to see the changes. Reproducible: Always Steps to Reproduce: Create a DWP Create a HTML or JSP. Type in a string. Do a RoS on any server. It open a new (internal) browser and displays the string. Change the string in the HTML/JSP and save it. Do another RoS on the same server. It opens a new browser window and displays the old string! Reload the page and you can see the changed string. Change the browser to external IE or FF and this problem is not seen.
What version of Eclipse were you running - did you have WTP installed?
Eclipse Platform Version: 3.6.1.r361_v20100909-9gF78GrkFqw7GrsZnvz0JWNTeb6fue6896L Build id: M20100909-0800 Eclipse RCP Version: 3.6.1.r361_v20100827-9OArFLdFjY-ThSQXmKvKz0_T Build id: M20100909-0800 Eclipse Java Development Tools Version: 3.6.1.r361_v20100714-0800-7z8XFUSFLFlmgLc5z-Bvrt8-HVkH Build id: M20100909-0800 Eclipse Web Developer Tools Version: 3.2.2.v201008100100-7O7CFbKEMf84nUlEJyX7-SPQjhYZ Build id: 20100415162438
This looks similar to Bug 300174 which was fixed in Eclipse 3.6. Maybe there is something different about this case which I am not noticing. Can you try the steps in Bug 300174 to see if that problem can be reproduced on your system?
The steps in this defect is exactly similar to the steps reported in Bug 300174.
I can reproduce the problem using I20101005-0800. I'm not sure why this is happening because I can see the lines of code from the patch are in the source and using a debugger I can see that these lines are being executed. It's possible that the regression is due to changes in IE8 since when Bug 300174 was fixed. In any case I think may need to reopen that bug.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
