ICEfaces
  1. ICEfaces
  2. ICE-1461

OutputConnectionStatus doesn't work with more than one portlet

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.6DR#3
          • Fix Version/s: 1.7DR#3, 1.7
          • Component/s: ICE-Components
          • Labels:
            None
          • Environment:
            any

            Description

            Contribution from Dan Leahu:

            OutputConnectionStatus doesn't work with more than one portlet because the "connection-status" is hard-coded in icefaces-d2d.js class hence it doesn't accept more than one OutputConnectionStatus on the same master page(the portal's page).

              Activity

              Descending order - Click to sort in ascending order
              Hide
              Permalink
              Mircea Toma added a comment -

              Refactor how status component is setup.

              Show
              Mircea Toma added a comment - Refactor how status component is setup.
              Hide
              Permalink
              Ken Fyten added a comment -

              We could make it so multiple instances of the outputConnectionStatus component on a single page would all be updated by the bridge, thus, making them work as expected in portals.

              Show
              Ken Fyten added a comment - We could make it so multiple instances of the outputConnectionStatus component on a single page would all be updated by the bridge, thus, making them work as expected in portals.

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: