javaserverfaces
  1. javaserverfaces
  2. JAVASERVERFACES-1877

FacesMessage not displayed on page in subdirectory

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Duplicate
    • Affects Version/s: 2.0.2
    • Fix Version/s: None
    • Component/s: facelets
    • Labels:
      None
    • Environment:

      Operating System: Linux
      Platform: GlassFish 3.0.1

    • Issuezilla Id:
      1,877
    • Status Whiteboard:
      Hide

      size_medium importance_large

      Show
      size_medium importance_large

      Description

      FacesMessage is not displayed when I navigate (via a redirect navigation rule)
      to a page in a subdirectory.

      I have these navigation rules in faces-config.xml: http://pastebin.com/c30a2etj
      . That page: http://pastebin.com/XrYyifDx uses this:
      http://pastebin.com/7rFhFQbL backing bean to add a message and navigate to
      another page, either in the same or in a subdirectory of the current. those both
      pages are exactly the same, one displays the message, the other does not.

      Strange thing: Upon the very,very first deployment, the message would be
      displayed at the subdirectory-page correctly. After that, it doesn't. Neither
      undeploying, nor shift-reload in browser, nor stopping and starting GlassFish
      makes it reappear. So I guess it's an issue about the flash thing?

      Appeared on a fresh NetBeans 6.9.1 environment, using the shipped GlassFish
      3.0.1 and its Mojarra 2.0.2 . No other libraries used, flash.setKeepMessages is
      set to true in both cases.

      The NetBeans project I created for this is available at
      http://rapidshare.com/files/432087157/FacesMessages.tar.gz

        Issue Links

          Activity

          Hide
          Ed Burns added a comment -

          Exclude these as impractical for GlassFish 3.1

          Show
          Ed Burns added a comment - Exclude these as impractical for GlassFish 3.1
          Hide
          Ed Burns added a comment -

          Exclude these issues from GlassFish 3.1. Reasons include:

          not important enough
          too risky

          Show
          Ed Burns added a comment - Exclude these issues from GlassFish 3.1. Reasons include: not important enough too risky
          Hide
          Jens Buthmann added a comment -

          I just ran into this issue again with this when I tried to store a Object in flash scope, navigate to a page in another directory and try to restore the Object.

          Since this renders Flash in most cases unusable, I disagree with Your comment "not important enough". I hope I do not offend You by this,

          Or am I getting something wrong, did I do a mistake?

          Show
          Jens Buthmann added a comment - I just ran into this issue again with this when I tried to store a Object in flash scope, navigate to a page in another directory and try to restore the Object. Since this renders Flash in most cases unusable, I disagree with Your comment "not important enough". I hope I do not offend You by this, Or am I getting something wrong, did I do a mistake?
          Hide
          Ed Burns added a comment -

          No offense, I was only stating that it does not meet the criteria for holding the release of GlassFish 3.1.

          Show
          Ed Burns added a comment - No offense, I was only stating that it does not meet the criteria for holding the release of GlassFish 3.1.
          Hide
          luisalves00 added a comment - - edited

          replaced JsfUtil.flashScope().setKeepMessages(true); for the solution describe here: http://blogs.sourceallies.com/2010/03/rendering-global-tmessages-after-redirect/ as an workaround for the bug.

          Show
          luisalves00 added a comment - - edited replaced JsfUtil.flashScope().setKeepMessages(true); for the solution describe here: http://blogs.sourceallies.com/2010/03/rendering-global-tmessages-after-redirect/ as an workaround for the bug.
          Hide
          Ed Burns added a comment -

          Because a workaround exists, setting Priority to Minor.

          Show
          Ed Burns added a comment - Because a workaround exists, setting Priority to Minor.
          Hide
          arjan tijms added a comment -

          The workaround doesn't really addresses the Flash issue itself. It's the JSF 1.x method of saving faces messages into the session and then restoring them at any next page.

          This issue does seem to be the exact same one as JAVASERVERFACES-1956 and JAVASERVERFACES-2136, while JAVASERVERFACES-1635 is related (it also mentions path related problems, but in combination with the back button).

          Show
          arjan tijms added a comment - The workaround doesn't really addresses the Flash issue itself. It's the JSF 1.x method of saving faces messages into the session and then restoring them at any next page. This issue does seem to be the exact same one as JAVASERVERFACES-1956 and JAVASERVERFACES-2136 , while JAVASERVERFACES-1635 is related (it also mentions path related problems, but in combination with the back button).

            People

            • Assignee:
              Unassigned
              Reporter:
              Jens Buthmann
            • Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: