Mule
  1. Mule
  2. MULE-5747

Sub-flows (and processors defined in them) don't get muleContext injected or lifecycle when used via flow-ref

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 3.1.2, 3.2-RC1
    • Fix Version/s: 3.1.3 (EE only), 3.2.0
    • Component/s: Core: Lifecycle
    • Labels:
      None
    • User impact:
      High
    • Similar Issues:
      MULE-5752Components cannot be used in globally defined sub-flows or processor-chains
      MULE-5837Error at startup when a sub-flow is invoked twice via flow-ref
      MULE-5941sub-flow name is not displayed nor required in the schema but you get an error when trying to run an app with a sub-flow without a name
      MULE-7773Dynamic reference to sub flow produces lifecycle errors
      MULE-7464Runtime Message Processor Injection
      MULE-6401Lifecycle is not invoked for the MPs in a sub-flow when it is being references with expressions
      MULE-6348Support recursive flows/sub-flows
      MULE-5900As a user I want invocation properties I set in a flow to be available everywhere in the same flow and and other flows referenced by flow-ref
      MULE-6146Filters in sub-flows do not filter as expect and should (rather only act as sub-flow 'return')
      MULE-5847Sub-flow doesn't admit doc name causing errors when creating them in Mule Studio

      Issue Links

        Activity

        Hide
        Daniel Feist added a comment -

        3.1.x: r22729
        3.x: r22730

        Show
        Daniel Feist added a comment - 3.1.x: r22729 3.x: r22730

          People

          • Assignee:
            Daniel Feist
            Reporter:
            Daniel Feist
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development