Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

HttpUnit seems to be caching responses...grrr

 
Sheriff
Posts: 15815
264
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm using JDeveloper 9.0.3 and the embedded OC4J to run a Struts-based application.
HttpUnit 1.5 doesn't seem to be getting the changes that I make to my JSP. View source in IE reflects any changes in the JSP but in my HttpUnit test class, resp.getText() still shows the old JSP!
I've tried combinations of the following but nothing seems to help:
1. Terminate and restart OC4J
2. Run Struts app on one instance of JDeveloper and the HttpUnit test on another.
3. Delete generated jsps classes to make sure that they are recompiled next time they are requested.
4. Exit and restart JDeveloper
The only thing that helps is if I reboot my machine but I can't be rebooting every 5 minutes! That defeats the whole purpose of using the testing framework
Seems to me that somehow the original WebResponse object is not going away since IE can see the changes.
I would really appreciate any help or suggestions. Thanks!
 
Junilu Lacar
Sheriff
Posts: 15815
264
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Some of the best ideas come to you on the can... :roll:
It finally dawned on me that the problem was proxy server-related. Sure enough, when I changed the URL from using the dot notation IP address supplied by JDeveloper and used "localhost" instead, thus bypassing the proxy server, things work as expected.
    Bookmark Topic Watch Topic
  • New Topic