ICEfaces
  1. ICEfaces
  2. ICE-9960

New general purpose ace:proxy component for ACE containers

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Won't Fix
          • Affects Version/s: None
          • Fix Version/s: 4.2
          • Component/s: ACE-Components
          • Labels:
            None
          • Environment:
            ICEfaces 4.x

            Description

            A new ace:proxy component should be created that would provide support for specifying which form any submit triggered by a container component (that itself is not located inside a form) should occur in.

            This functionality exists already in the case of the ace:tabSet and ace:tabSetProxy component, but should be further generalized to work with all ACE (and possibly MOBI) containers, such as:

            - ace:accordion
            - ace:dialog
            - ace:notificationPanel
            - ace:panel
            - ace:resizable
            - ace:tooltip/ace:delegate (?)
            - ace:tabSet (deprecate ace:tabSetProxy)

              Issue Links

              blocks

              Bug - A problem which impairs or prevents the functions of the product. ICE-9567 ace:dialog JS error on IE7/8 when widgetVar referenced from outside the containing form

              • Major - Major loss of function.
              • Open

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                Ken Fyten added a comment -

                FYI, description of the current ace:tabSetProxy:

                The ace:tabSetProxy component works in conjunction with its associated server side ace:tabSet, so that the ace:tabSet need not be inside a form, but can still communicate with the server, when it changes its current tab. The purpose of this is so that ace:tabPane components may have forms within them, and since forms can not be nested, ace:tabSet needed to be freed from the requirement to be inside a form itself. As well, since ace:tabSet's immediate and cancelOnInvalid properties control the interaction of the changing of current tab selection, with the validation of input components in the submitted form, ace:tabSetProxy is the means for specifying which form, anywhere on the page, should host the submission of the tab change. So, when the current tab changes, it is the form that the ace:tabSetProxy is in, which is submitted.

                Show
                Ken Fyten added a comment - FYI, description of the current ace:tabSetProxy: The ace:tabSetProxy component works in conjunction with its associated server side ace:tabSet, so that the ace:tabSet need not be inside a form, but can still communicate with the server, when it changes its current tab. The purpose of this is so that ace:tabPane components may have forms within them, and since forms can not be nested, ace:tabSet needed to be freed from the requirement to be inside a form itself. As well, since ace:tabSet's immediate and cancelOnInvalid properties control the interaction of the changing of current tab selection, with the validation of input components in the submitted form, ace:tabSetProxy is the means for specifying which form, anywhere on the page, should host the submission of the tab change. So, when the current tab changes, it is the form that the ace:tabSetProxy is in, which is submitted.
                Hide
                Permalink
                Mircea Toma added a comment - - edited

                As alternatives to the ace:proxy component we could have:

                • A form attribute on the component that can contain the ID of the form that should be used by the component to submit its data.
                • Automatically use a default (built-in) form that will submit just the data of the component that triggered the submit.
                Show
                Mircea Toma added a comment - - edited As alternatives to the ace:proxy component we could have: A form attribute on the component that can contain the ID of the form that should be used by the component to submit its data. Automatically use a default (built-in) form that will submit just the data of the component that triggered the submit.
                Hide
                Permalink
                Ken Fyten added a comment -

                Closing as won't fix as this general approach is not required/desired.

                Show
                Ken Fyten added a comment - Closing as won't fix as this general approach is not required/desired.

                  People

                  • Assignee:
                    Ken Fyten
                    Reporter:
                    Ken Fyten
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    3 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: