ICEfaces
  1. ICEfaces
  2. ICE-6667

Portlets: CoreComponentUtils findComponent not absolutely finding components

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Won't Fix
          • Affects Version/s: 2.0.0
          • Fix Version/s: 2.0.1
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            Portlets, ICEfaces 2

            Description

            As found in ICE-6659, when using an absolute search for a component, CoreComponentUtils.findComponent(-) is not finding the component. There seems to be some issue with the clientIds including the portlet namespace in a way that the algorithm doesn't support.

            This might also be part of the issue with portlet environment components not finding each other with their for property.

              Issue Links

              blocks

              Bug - A problem which impairs or prevents the functions of the product. ICE-6398 CoreComponentUtils.findComponent(UIComponent, String) is bailing out too early, not recursing through the component tree enough to find a matching clientId

              • Major - Major loss of function.
              • Closed

              Bug - A problem which impairs or prevents the functions of the product. ICE-6659 ice:inputText required validation not happening properly inside portlet

              • Major - Major loss of function.
              • Closed

                Activity

                There are no subversion log entries for this issue yet.

                  People

                  • Assignee:
                    Deryk Sinotte
                    Reporter:
                    Mark Collette
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: