ICEfaces-EE
  1. ICEfaces-EE
  2. IPCK-365

FilterTable Composite Component loses reference to #{bean} variable after Filtering

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: EE-3.0.0.BETA
          • Fix Version/s: EE-3.0.0.GA
          • Component/s: None
          • Labels:
            None
          • Environment:
            n/a

            Description

            The FilterTable example renders the following ajax response after attempting to filter:

            <partial-response>
               <error>
                  <error-name>javax.faces.el.PropertyNotFoundException</error-name>
                  <error-message>
                  <![CDATA[org.apache.myfaces.view.facelets.el.ContextAwarePropertyNotFoundException: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null]]>
                   </error-message>
                </error>
            <changes><extension aceCallbackParam="validationFailed">{"validationFailed":false}</extension></changes></partial-response>

              Activity

              Descending order - Click to sort in ascending order
              Hide
              Permalink
              Philip Breau added a comment -

              fix serialization issues with MyFaces
              fix template scoping issues with MyFaces
              when used with MyFaces 2, users will have to use the 'bean' property on the <icecc:filterColumn> as shown in the example, as MyFaces will not pass this through from the parent. Users of Mojarra are unaffected. eg:

              <ice-cc:filterColumn title="First Name" value="#

              {row.firstName}

              "
              property="firstName" bean="#

              {filterTableExampleBean.filterTableBean}

              "/>

              30695 3/7/12 2:48 PM 4 philip.breau IPCK-365 fix MyFaces serialization issues fix template scoping issues

              Show
              Philip Breau added a comment - fix serialization issues with MyFaces fix template scoping issues with MyFaces when used with MyFaces 2, users will have to use the 'bean' property on the <icecc:filterColumn> as shown in the example, as MyFaces will not pass this through from the parent. Users of Mojarra are unaffected. eg: <ice-cc:filterColumn title="First Name" value="# {row.firstName} " property="firstName" bean="# {filterTableExampleBean.filterTableBean} "/> 30695 3/7/12 2:48 PM 4 philip.breau IPCK-365 fix MyFaces serialization issues fix template scoping issues
              Hide
              Permalink
              Philip Breau added a comment -

              bean is now resolving but this new exception is showing up:

              <partial-response>
              <error>
              <error-name>javax.faces.el.PropertyNotFoundException</error-name>
              <error-message><![CDATA[org.apache.myfaces.view.facelets.el.ContextAwarePropertyNotFoundException: javax.el.PropertyNotFoundException: Target Unreachable, 'columnFilterInput' returned null]]></error-message>
              </error>...

              Show
              Philip Breau added a comment - bean is now resolving but this new exception is showing up: <partial-response> <error> <error-name>javax.faces.el.PropertyNotFoundException</error-name> <error-message><![CDATA [org.apache.myfaces.view.facelets.el.ContextAwarePropertyNotFoundException: javax.el.PropertyNotFoundException: Target Unreachable, 'columnFilterInput' returned null] ]></error-message> </error>...

                People

                • Assignee:
                  Philip Breau
                  Reporter:
                  Philip Breau
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: