ICEfaces
  1. ICEfaces
  2. ICE-7545

ace:dataExporter does not work witin a composite component

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 3.0.RC1
          • Fix Version/s: 3.0.RC2, 3.0
          • Component/s: ICE-Components
          • Labels:
            None
          • Environment:
            -
          • Assignee Priority:
            P2

            Description

            The following issue has been reported:

            The ace:dataExporter component searches from the UIViewRoot for the dataTable so it can't be used from within a composite component. It should do a findComponent() from itself so that it would find the datatable in its closest NamingContainer. Another improvement would be to also set the table component in a setter method so that it could used from a binding.

            Test case attached.

              Activity

              Ascending order - Click to sort in descending order
              Tyler Johnson created issue -
              Tyler Johnson made changes -
              Field Original Value New Value
              Attachment sf-10757.war [ 13848 ]
              Tyler Johnson made changes -
              Salesforce Case [5007000000JOP3V]
              Description The following issue has been reported:

              The ace:dataExporter component searches from the UIViewRoot for the dataTable so it can't be used from within a composite component. It should do a findComponent() from itself so that it would find the datatable in its closest NamingContainer. Another improvement would be to also set the table component in a setter method so that it could used from a binding.
              		 The following issue has been reported:

              The ace:dataExporter component searches from the UIViewRoot for the dataTable so it can't be used from within a composite component. It should do a findComponent() from itself so that it would find the datatable in its closest NamingContainer. Another improvement would be to also set the table component in a setter method so that it could used from a binding.

              Test case attached.
              Ken Fyten made changes -
              Fix Version/s 3.0 [ 10241 ]
              Assignee Priority P2
              Assignee Arturo Zambrano [ artzambrano ]
              Arturo Zambrano made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Resolution Fixed [ 1 ]
              Ken Fyten made changes -
              Fix Version/s 3.0.RC2 [ 10313 ]
              Ken Fyten made changes -
              Status Resolved [ 5 ] Closed [ 6 ]

                People

                • Assignee:
                  Arturo Zambrano
                  Reporter:
                  Tyler Johnson
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: