ICEfaces
  1. ICEfaces
  2. ICE-1139

Seam: ValueChangeListener fired on unrendered SelectOneRadio

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.5.1
          • Fix Version/s: 1.6DR#2, 1.6
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            Operating System: Windows XP
            Platform: PC

            Description

            noted in the forum: http://www.icefaces.org/JForum/posts/list/3291.page

            and verified not to occur in non-Seam ICEfaces + Facelets

            If you have an unrendered SelectOneRadio with a valueChangeListener that's
            contained in an unselected parent panelStack item, the valueChangeListener is
            fired on other valueChanges, and a null "new value" is passed through the
            ValueChangeEvent

              Issue Links

              blocks

              New Feature - A new feature of the product, which has yet to be developed. ICE-1810 Support Integration with JBoss Seam

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                Philip Breau added a comment -

                Created an attachment (id=129)
                non-Seam test case

                Show
                Philip Breau added a comment - Created an attachment (id=129) non-Seam test case
                Hide
                Permalink
                Ken Fyten added a comment -

                This issue needs to be analyzed along with other Seam related issues and distilled to root causes.

                Show
                Ken Fyten added a comment - This issue needs to be analyzed along with other Seam related issues and distilled to root causes.
                Hide
                Permalink
                Greg Dick added a comment -

                I'm not seeing this on either 1.5.3, nor 1.6. One part of the forum post indicates an exception

                07:01:12,656 ERROR [D2DFaceletViewHandler] Problem in renderResponse: empty expr
                java.lang.IllegalArgumentException: empty expr
                at javax.faces.component.UIComponentBase.findComponent(UIComponentBase.java:388)
                at com.icesoft.faces.component.panelstack.PanelStackRenderer.encodeChildren(PanelStackRenderer.java:94)
                at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:524)

                I did encounter this when the PanelStackRenderer tried to render the current panel (obtained from the componet) and the property hadn't been initialized. Giving the current panel properties a value in the constructor will avoid this. I wouldn't expect the properties to have an initial value before the setter is called, without explicitly giving it one though.

                Status: waiting for the reporter to try an example I had reverse engineered to test the app. Also waiting to see what versions he was using, as that might have an effect.

                At this point, this doesn't look like a Seam integration problem. No Seam tags are used, the panel components are strictly ICEfaces, and the technology is partial submit, which has no Seam interaction. Maybe something will show up in the source code.

                Show
                Greg Dick added a comment - I'm not seeing this on either 1.5.3, nor 1.6. One part of the forum post indicates an exception 07:01:12,656 ERROR [D2DFaceletViewHandler] Problem in renderResponse: empty expr java.lang.IllegalArgumentException: empty expr at javax.faces.component.UIComponentBase.findComponent(UIComponentBase.java:388) at com.icesoft.faces.component.panelstack.PanelStackRenderer.encodeChildren(PanelStackRenderer.java:94) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:524) I did encounter this when the PanelStackRenderer tried to render the current panel (obtained from the componet) and the property hadn't been initialized. Giving the current panel properties a value in the constructor will avoid this. I wouldn't expect the properties to have an initial value before the setter is called, without explicitly giving it one though. Status: waiting for the reporter to try an example I had reverse engineered to test the app. Also waiting to see what versions he was using, as that might have an effect. At this point, this doesn't look like a Seam integration problem. No Seam tags are used, the panel components are strictly ICEfaces, and the technology is partial submit, which has no Seam interaction. Maybe something will show up in the source code.
                Hide
                Permalink
                Greg Dick added a comment -

                Example applications are larger than 10M and can't be attached to this case. The test application has been posted on the forum.

                Show
                Greg Dick added a comment - Example applications are larger than 10M and can't be attached to this case. The test application has been posted on the forum.

                  People

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

                    Dates

                    • Created:
                      Updated:
                      Resolved: