2 Replies Latest reply on Aug 10, 2007 1:05 AM by Monkey Den

    Empty pages using Facelets

    Monkey Den Master

      Has anyone run into an issue where the backing is, by all accounts, doing it's work correctly but Facelets/JSF renders the page without any data? I can't reproduce this manually but can do it consistently using JMeter. I have tried to following, to ensure that everything is working correctly:

      1. Log an error if the object is null. Message is never printed, so the backing bean is good
      2. Switch from outjection of the data object to accessor on the backing bean.
      @Out Employee employee; is replaced by getEmployee(), using #{bean.employee} in the view
      3. Used facelets with and without <ui:param>

      I'm pretty sure this is a Facelets issue but wondered about anyone else's experiences.

      Thanks

        • 1. Re: Empty pages using Facelets
          Monkey Den Master

          As it turns out, the pages relied on page actions. Somehow these weren't being called before value binding methods when tested under a heavy load. Is there a guarantee that they will be called right after @Create?

          Also, is there any functional difference between:

          <page view-id="/searchResults.xhtml" action="#{nemAppManager.initAction}">
           <!-- some navigation rules -->
          </page>


          and

          <page view-id="/searchResults.xhtml">
           <action execute="#{appManager.initAction}" />
           <!-- some navigation rules -->
          </page>


          • 2. Re: Empty pages using Facelets
            Monkey Den Master

            Sorry, bad example. One uses an action attribute, the other a child tag.

            <page view-id="/searchResults.xhtml" action="#{appManager.initAction}">
             <!-- some navigation rules -->
            </page>
            

            <page view-id="/searchResults.xhtml">
             <action execute="#{appManager.initAction}" />
             <!-- some navigation rules -->
            </page>