5

This question is spawned from Mac: JSF: why are development stage JSF web apps not always catching composite component changes?. If I can answer the question here, I will have a brute-force strategy for getting around that other reported problem, but this question here has a standalone purpose.

Q: How can I programmatically force clearing of the Facelets in-memory cache in a running web app (so that I can create a listener that is invoked from a [Clear Facelets Cache] button) ?

I am using NetBeans8.1beta and Glassfish4.1, with deployment over the NetBeans project's /build/web.

Community
  • 1
  • 1
Webel IT Australia - upvoter
  • 1,756
  • 1
  • 21
  • 34
  • Have you been able to find a solution for this by now? – Roben Jul 15 '16 at 11:26
  • @Roben No solution yet, and still very interested in finding one. Webel – Webel IT Australia - upvoter Jul 19 '16 at 05:10
  • Maybe this will be possible using a custom facelet cache factory. See the answer from Ballusc on http://stackoverflow.com/questions/31984924/custom-faceletfactory-in-jsf-2-2-alternatives-for-virtual-host-facelets. Thanks to seam, I am still stuck with JSF 2.1 though, so I am currently not able to test this. – Roben Jul 20 '16 at 10:30

0 Answers0