Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Hot deployment of js/jspx not working after upgrade to JSF2.1

SA-7543

Summary



On running the application with server setting "Run server with resources on server", hot deploying the jspx, after making some changes, does not reflect the changes on browser (even after deleting the cookies and temporary internet files). There are no error messages or logs generated. Changes are not reflecting on view source/debugger tool of the browser.

Error Messages



Not Applicable

Steps to Reproduce

  1. Open any jspx page.
  2. Make some changes in it.
  3. Hot deploy the files in the server profile.
  4. Open the browser and see if the changes are displayed on screen.

Root Cause



The root cause of this problem is that the MyFaces caches aggresively. Even with HotDeployment it refers to cached version of jspx / jsf page.


Resolution



This behavior can be addressed by adding PROJECT_STAGE entry in deployment descriptor as below:

<context-param>
    <param-name>javax.faces.PROJECT_STAGE</param-name>
    <param-value>Development</param-value>
</context-param>


With this context parameter, MyFaces will relax the Facelet caching strategy, causing it to recompile the Facelet file almost instantly.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us