caching - Different behaviour for local and productive WeblogicServer -
O people,
I have a strange behavior and I am wondering why this happens :
My managed van has three values (selected plant, selected year and selected months). When opening the required page, the code of the plant is started and started by selecting Now my problem is: My local weblogic server (Integrated Web server - standard configuration) works as expected, I open the page, view my current data, switch to editing mode, edit & Amp; Help. is that all. works like a charm. The productive weblogic server (I have been configured by a colleague) I think that does some kind of cache. I open the page, see my current data, change the values of the year last year and see the updated values. When clicking on the "Edit" button, the old values are displayed instead of the updated values. It happens until I change the plant. My current solution looks like this: Open the page, switch to the plant and then switch the year. Works as expected after changing plant, I can not understand why the productive machine works differently from the local machine. Each updated methods setPlant (), setYear () and setMonth () call RefreshVille () and similar JSF Definitions are required. So I do not know if this is a caching problem or maybe a Weblogic configuration problem. You know more information or need some piece of code. I put them out as it has a lot of code Thanks, Stefi Enable http header debug from browser and in every environment Monitor the difference. Also monitor access.log on each domain server. @PostConstruct method and according to pre-defined plant, year and month. None of these three options should be updated and updated via AJAX request while changing data. To switch to editing mode, I can right click on my button to change a value that indicates whether the page should be visible in view or edited mode.
Comments
Post a Comment