RichFaces
  1. RichFaces
  2. RF-1006

Xml filter throw exception for a non JSF-view generated resources.

    Details

    • Type: Bug Bug
    • Status: Closed Closed (View Workflow)
    • Priority: Critical Critical
    • Resolution: Done
    • Affects Version/s: 3.1.0
    • Fix Version/s: 3.1.4, 3.2.0
    • Component/s: None
    • Security Level: Public (Everyone can see)
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      Set filter parameter
      <init-param>
      <param-name>forceparser</param-name>
      <param-value>true</param-value>
      </init-param>
      Cause nullPointerException from non-jsf pages responses.

        Activity

        Hide
        Ilya Shaikovsky
        added a comment -

        Should be assigned to me after fix without resolving. We'll commit them to 3.1.1 if will be fixed before release.

        Show
        Ilya Shaikovsky
        added a comment - Should be assigned to me after fix without resolving. We'll commit them to 3.1.1 if will be fixed before release.
        Hide
        Franck MARTIN
        added a comment -

        can we change the fix version to 3.1.1?
        This bug prevents having both file download and ajax hibernate validation running in seam applications which is really annoying.
        It should be easy to detect that the content type of the response is not text/html and then do NOT filter the response at all. If it's binary like application/pdf the filter should let it go through.

        What do you think?

        Show
        Franck MARTIN
        added a comment - can we change the fix version to 3.1.1? This bug prevents having both file download and ajax hibernate validation running in seam applications which is really annoying. It should be easy to detect that the content type of the response is not text/html and then do NOT filter the response at all. If it's binary like application/pdf the filter should let it go through. What do you think?
        Hide
        Luiz Gustavo
        added a comment -

        We changed to version 3.1.0 to solve some problems, and now we have this problem related to the response content type.
        PDF reports/downloads are essential nowadays!
        Please, could we have this fix on version 3.1.1?

        thanks!

        Show
        Luiz Gustavo
        added a comment - We changed to version 3.1.0 to solve some problems, and now we have this problem related to the response content type. PDF reports/downloads are essential nowadays! Please, could we have this fix on version 3.1.1? thanks!
        Hide
        Eduardo Santos
        added a comment -

        We also noticed the difficulty in the generations of reports in HTML for the difficulty in patterns, of browser and applications.
        It would like that in version 3.1.1 to solve this problem,
        thankful

        Show
        Eduardo Santos
        added a comment - We also noticed the difficulty in the generations of reports in HTML for the difficulty in patterns, of browser and applications. It would like that in version 3.1.1 to solve this problem, thankful
        Hide
        Nick Belaevski
        added a comment -

        resolved

        Show
        Nick Belaevski
        added a comment - resolved
        Hide
        Ilya Shaikovsky
        added a comment -

        Alex, commit this to 3.1.x please.. and resolve to both versions this issue.

        Show
        Ilya Shaikovsky
        added a comment - Alex, commit this to 3.1.x please.. and resolve to both versions this issue.
        Hide
        Alan Feng
        added a comment -

        Looks like this is not included in the 3.1.3 release.

        I noticed, when I trace into the problem, that the same problem will also occur if the view ID does not have a corresponding physical .xhtml file. In which case, it is trying match the null xhtml template name against the predefined pattern to see if a pages should be parsed by the particular parser, and hence the NPE.

        Show
        Alan Feng
        added a comment - Looks like this is not included in the 3.1.3 release. I noticed, when I trace into the problem, that the same problem will also occur if the view ID does not have a corresponding physical .xhtml file. In which case, it is trying match the null xhtml template name against the predefined pattern to see if a pages should be parsed by the particular parser, and hence the NPE.

          People

          • Assignee:
            Viktor Volkov
            Reporter:
            Alexander Smirnov
          • Votes:
            5 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: