Mule
  1. Mule
  2. MULE-4586

Merge Session property-related changes forwards, backwards, and sideways

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Completed
    • Affects Version/s: 2.1.4 (EE only), ITR24, 3.0.0-M2
    • Fix Version/s: ITR27, 3.0.0-M2
    • Component/s: Core: Sessions
    • Labels:
      None
    • User impact:
      Medium
    • Similar Issues:
      MULE-2118Make RequestContext backwards compatible
      MULE-6099Merged session for an event group is not created in a deterministic way
      MULE-8713Merge mule 3.x on 4.x branch
      MULE-6954Merge 3.4.1 changes from ASR from Dynamic Round Robin
      MULE-8194Change DB conector resultsets to TYPE_FORWARD_ONLY to support additional databases
      MULE-8389Analyze merge method of DefaultMuleSession
      MULE-8830Review/Fix test broken on mule 4 after merge
      MULE-6001Ensure session scope properties merged correctly with outbound endpoints and async reply
      MULE-7575Aggregator result has invalid session variables values
      MULE-8325Review and merge MULE-7588

      Description

      Merge Session property-related changes for MULE-4567/EE-1705, MULE-4432, MULE-4431

      • back to 2.1.x
      • forward to 3.x

        Issue Links

          Activity

          Show
          Travis Carlson added a comment - 3.x: http://fisheye.codehaus.org/changelog/mule/?cs=16252
          Hide
          Travis Carlson added a comment -

          The merge to 3.x broke org.mule.transport.servlet.jetty.JettyContinuationsHttpFunctionalTestCase

          Show
          Travis Carlson added a comment - The merge to 3.x broke org.mule.transport.servlet.jetty.JettyContinuationsHttpFunctionalTestCase
          Hide
          Travis Carlson added a comment -

          DO:
          "If you look at the log output that the test generates in 2.2.x I doubt
          that it works there. The test failure is just better masked in 2.2.x

          I'm all for making it work in 2.2.x first and only then tackling the 3.x
          test failure."

          Show
          Travis Carlson added a comment - DO: "If you look at the log output that the test generates in 2.2.x I doubt that it works there. The test failure is just better masked in 2.2.x I'm all for making it work in 2.2.x first and only then tackling the 3.x test failure."

            People

            • Assignee:
              Travis Carlson
              Reporter:
              Travis Carlson
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development