ajax4jsf
  1. ajax4jsf
  2. AJAX4JSF-26

Filter. reformatting page breaks jsf-comp

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: current
    • Fix Version/s: milestone 1
    • Component/s: www
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      26

      Description

      I'm using MyFaces (1.1.4), Facelets, jsf-comp and ajax4jsf. Adding the latter
      changed the behaviour of jsf-comp.

      jsf-comp clientvalidators can display in-page error messages as well as popups.
      It takes the value for the popup message from the innerHTML from an in-page
      error div element. However, this is broken by using ajax4jsf.

      The following config section in my web.xml

      <filter>
      <display-name>Ajax4jsf Filter</display-name>
      <filter-name>ajax4jsf</filter-name>
      <filter-class>org.ajax4jsf.Filter</filter-class>
      </filter>
      <filter-mapping>
      <filter-name>ajax4jsf</filter-name>
      <servlet-name>Faces Servlet</servlet-name>
      <dispatcher>REQUEST</dispatcher>
      <dispatcher>FORWARD</dispatcher>
      <dispatcher>INCLUDE</dispatcher>
      </filter-mapping>

      caused this HTML (when page is loaded without the above config section):

      <FONT class="defaultValidationMsgClass"><div id="loginForm:_id12"
      class="dynamicDivClass">Username is required</div></FONT>

      to be changed into this (when page is loaded with the above config section):

      <div id="loginForm:_id12" class="dynamicDivClass"><font
      class="defaultValidationMsgClass">Username is required</font></div>

      I don't know why ajax4jsf does this, or even if it should.

        Activity

        Hide
        welshofdave added a comment -

        Updating the subject since it seems there are a couple of other issues with the
        filter.

        Show
        welshofdave added a comment - Updating the subject since it seems there are a couple of other issues with the filter.
        Hide
        welshofdave added a comment -

        Found that putting this into the filter makes the problem go away.

        <init-param>
        <param-name>forceparser</param-name>
        <param-value>false</param-value>
        </init-param>

        Show
        welshofdave added a comment - Found that putting this into the filter makes the problem go away. <init-param> <param-name>forceparser</param-name> <param-value>false</param-value> </init-param>

          People

          • Assignee:
            ajax4jsf-issues
            Reporter:
            welshofdave
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: