ICEfaces
  1. ICEfaces
  2. ICE-5323

Regression: ICE-3147 not working as expected

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Invalid
    • Affects Version/s: 2.0-Alpha2
    • Fix Version/s: 2.0-Beta1
    • Component/s: ICE-Components
    • Labels:
      None
    • Environment:
      N/A
    • Assignee Priority:
      P2

      Description

      The application has two command links one with no children the other with child em tag.
      Toggle happens only after first click. The toggle value does not change on any subsequent clicks.
      Note: same application works on ICEfaces1.8.2

        Issue Links

          Activity

          Hide
          Mandeep Hayher added a comment -

          Problem still exists on
          Glimmer revision# 21634
          Server: Tomcat6
          Browser: FF3.6, Opera10.10 & IE8

          Note:Works fine on icefaces trunk.

          Show
          Mandeep Hayher added a comment - Problem still exists on Glimmer revision# 21634 Server: Tomcat6 Browser: FF3.6, Opera10.10 & IE8 Note:Works fine on icefaces trunk.
          Hide
          Mircea Toma added a comment -

          I cannot find the test case for ICE-3147. Where can I find it?

          Show
          Mircea Toma added a comment - I cannot find the test case for ICE-3147 . Where can I find it?
          Hide
          Mandeep Hayher added a comment -

          Testcase is available at C:\repo\qa\trunk\Regression-Icefaces2\Nightly\ICE-3147.

          Show
          Mandeep Hayher added a comment - Testcase is available at C:\repo\qa\trunk\Regression-Icefaces2\Nightly\ ICE-3147 .
          Hide
          Mircea Toma added a comment - - edited

          The test case uses a bean in request scope, every-time the state is toggled a new bean instance is created thus the state will never be propagated to the next request.
          Running this test in 1.8 works because the default request scope is non-standard, the bean instances are not recreated for postback requests.

          Changing the scope of the bean to any other kind of scope beside 'request' will fix the test case.

          Show
          Mircea Toma added a comment - - edited The test case uses a bean in request scope, every-time the state is toggled a new bean instance is created thus the state will never be propagated to the next request. Running this test in 1.8 works because the default request scope is non-standard, the bean instances are not recreated for postback requests. Changing the scope of the bean to any other kind of scope beside 'request' will fix the test case.
          Hide
          Mandeep Hayher added a comment -

          Tested successfully on Glimmer revision# 21752, Tomcat6 & FF3.6

          Show
          Mandeep Hayher added a comment - Tested successfully on Glimmer revision# 21752, Tomcat6 & FF3.6

            People

            • Assignee:
              Mircea Toma
              Reporter:
              Mandeep Hayher
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: