ICEfaces
  1. ICEfaces
  2. ICE-3527

handle outcomes of Spring Web Flow 2 flows

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.7.1
    • Fix Version/s: 1.8.1
    • Component/s: None
    • Labels:
      None
    • Environment:
      ICEfaces, Spring Web Flow

      Description


      The result of Spring Web Flow flows was not implemented. In the case of the swf-booking-icefaces demo, this caused the booking confirmation to fail.

        Activity

        Hide
        Greg Dick added a comment -

        I believe this is fixed in 1.8.1. As a part of fixing ICE-4186, I fixed a large number of navigation outcome paths in SwfLifecycleExecutor.java. There were several issues with this class including the improper use of response.sendRedirect(location) (which does not work with the ICEFaces bridge) as well as simply commented out sections of code to handle various cases.

        At this time the swf-booking-faces sample application works identically to the Spring booking-faces application (assuming the always-redirect settings are the same)

        Show
        Greg Dick added a comment - I believe this is fixed in 1.8.1. As a part of fixing ICE-4186 , I fixed a large number of navigation outcome paths in SwfLifecycleExecutor.java. There were several issues with this class including the improper use of response.sendRedirect(location) (which does not work with the ICEFaces bridge) as well as simply commented out sections of code to handle various cases. At this time the swf-booking-faces sample application works identically to the Spring booking-faces application (assuming the always-redirect settings are the same)

          People

          • Assignee:
            Unassigned
            Reporter:
            Ted Goddard
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: