26

I had some problems with hot-reloading XHTML files using JRebel, Spring, JSF Mojarra 2.0.3 and WebLogic 10.3.

JRebel reloads regular Java classes and js/css files under /WebContent successfully, but not JSF's .xhtml files. A full republish was necessary to get xhtml files updated on the server.

By trial and error I finally got it to work by adding some facelets parameters to web.xml and creating a custom ResourceResolver as described in this blog post.

However, I wonder WHY this works, and more specifically:

  • Why is a custom ResourceResolver needed?
  • Isn't JRebel supposed to handle this by monitoring /WebContent where the xhtml files reside?
  • I'm guessing it has something to do with Facelets/JSF compiling xhtml to servlets(?) via FacesServlet which JRebel is unable to detect?
Mads Mobæk
  • 34,762
  • 20
  • 71
  • 78

2 Answers2

48

JRebel handles /WebContent folder changes.

The problem is that Facelets do caching and do not reread changed files. To force reread specify the following parameters in web.xml.

JSF 2 (Facelets 2.x):

<!-- Time in seconds that facelets should be checked for changes since last request. A value of -1 disables refresh checking. -->
<context-param>
    <param-name>javax.faces.FACELETS_REFRESH_PERIOD</param-name>
    <param-value>0</param-value>
</context-param>

<!-- Set the project stage to "Development", "UnitTest", "SystemTest", or "Production". -->
<!-- An optional parameter that makes troubleshooting errors much easier. -->
<!-- You should remove this context parameter before deploying to production! -->
<context-param>
    <param-name>javax.faces.PROJECT_STAGE</param-name>
    <param-value>Development</param-value>
</context-param>

For JSF 1.2 (Facelets 1.x) parameters are:

<context-param>
    <param-name>facelets.REFRESH_PERIOD</param-name>
    <param-value>0</param-value>
</context-param>
<context-param>
    <param-name>facelets.DEVELOPMENT</param-name>
    <param-value>true</param-value>
</context-param>

More on JSF context params: http://docs.jboss.org/jbossas/6/JSF_Guide/en-US/html/jsf.reference.html#standard.config.params

That custom resource resolver is not needed in your case. That resource resolver is just a tricky way to get xhtml files from custom file system folder. In your case JRebel does that (and even more).

Tiny
  • 27,221
  • 105
  • 339
  • 599
Andrey
  • 6,526
  • 3
  • 39
  • 58
  • I believe that JRebel already implicitly does that. At least, here it does. Note that your context params are Facelets 1.x specific and that OP is using Facelets 2.x. – BalusC Sep 22 '11 at 14:01
  • @Balusc Thanks for reply, answer updated to be Facelets 2.x specific. – Andrey Sep 22 '11 at 14:31
  • Setting `javax.faces.FACELETS_REFRESH_PERIOD` to `0` and `javax.faces.PROJECT_STAGE` to `Development` does not seem to trigger updated templates with JRebel on JSF 2.0.4 and WebLogic 10.3. – uggedal Sep 27 '11 at 11:06
  • @uggedal OP has noted that 'finally got it to work by adding some facelets parameters to web.xml and creating a custom ResourceResolver '. I don't know whether it works for him without custom resource resolver. – Andrey Sep 27 '11 at 12:13
  • 1
    Gotta love stack overflow. `javax.faces.FACELETS_REFRESH_PERIOD` worked perfectly for me. JBoss 4, JSF2. – Magnilex Apr 19 '13 at 06:56
  • Our team uses Glassfish 3/IceFaces and we had FACELETS_REFRESH_PERIOD set to -1 for quite a while. Setting it to 0 enabled hot-reloading XHTML. – dseibert Jul 12 '13 at 19:52
  • this change is a must in order to use jsf with jrebel – mokarakaya Jun 25 '15 at 12:44
1

Here's how I fixed this for me:

  1. Verify that facelets plugin is enabled in your JRebel settings &
  2. Verify that you're using Project Stage Development in your web.xml
Rajat Gupta
  • 25,853
  • 63
  • 179
  • 294