Problems after redeployment of SmartGWT App for IE8

[family.labrador@outlook.com]

Hi,

I have a general question. We are evaluating the framework and I need to convince the team so I did a few updates of the app during the development. The app is deployed on websphere and the Browser is IE8.

I got some strange things on some clients, suddenly some gui components like ToolStripButtons in table header disappeared on some clients. I tried browser restart and it seems to work. Is this normal? And is it because of redeployment? Or do I need to do anything the client will update the cache automatically on IE8?

It is important for an evaluation that the framework shows Reliability and I want to know if I did something wrong or the framework is unstable. Maybe it is an IE8 problem because on development environment with chrome I never had this problem.

Thx

[Blama]

Hi family.labrador,

generally speaking you should make sure that your main html and - more important - your projectname.nocache.js is not cached.
Also, the load_skin.js and skin_styles.css of your skin as well as the SmartGWT js files can and will change.
Of course you must ensure that the deployed version is also used in your clients' browsers.
There are many ways to ensure this:

• Clear cache (good, but manual step)
• Disable cache in browser (bad idea)
• Disable caching tags in webserver (bad idea)
• Change paths (good, some effort from your side)
• Configure caching to your needs (best idea, but effort from your side)

For the last point (using Apache httpd + Tomcat) see this thread.

Generally speaking, this is more a Webserver topic than a SmartGWT topic.

Best regards,
Blama

[family.labrador@outlook.com]

Problems after redeployment of SmartGWT App for IE8

Hi Blama,

Thx for your info. I cant change anything on the client configuration. What about your last point, configuring caching. Can you give some idea what you mean?

I did a ServletFilter which add meta like

final HttpServletResponse httpResponse = (HttpServletResponse) servletResponse;
        if (requestUri.contains(".nocache.")) {
            httpResponse.addHeader("Cache-Control", "no-cache, no-store, must-revalidate");
        }
        filterChain.doFilter(servletRequest, servletResponse);

I dont know if this is the best idea and not sure if this will solve the client issue.

Regards

Hi family.labrador,

generally speaking you should make sure that your main html and - more important - your projectname.nocache.js is not cached.
Also, the load_skin.js and skin_styles.css of your skin as well as the SmartGWT js files can and will change.
Of course you must ensure that the deployed version is also used in your clients' browsers.
There are many ways to ensure this:

• Clear cache (good, but manual step)
• Disable cache in browser (bad idea)
• Disable caching tags in webserver (bad idea)
• Change paths (good, some effort from your side)
• Configure caching to your needs (best idea, but effort from your side)

For the last point (using Apache httpd + Tomcat) see this thread.

Generally speaking, this is more a Webserver topic than a SmartGWT topic.

Best regards,
Blama

[Blama]

Hi family.labrador,

I can't really help here as I use apache httpd in front of tomcat in prod and an unconfigured tomcat in dev. In dev I'm facing the same issues you are.

Regarding your change: Open the network tab in FF F12 Tools and see whether your *.nocache.js-file (and main *.html-file) is always HTTP 200 and not a caching status. Also look at the response headers.

Best regards,
Blama