Mule
  1. Mule
  2. MULE-6127

Default mule application mule context is private

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.2.1
    • Fix Version/s: 3.3 M3
    • Component/s: Core: API
    • Labels:
      None
    • User impact:
      Very Low
    • Similar Issues:
      MULE-1456Exception in thread "main" org.mule.MuleRuntimeException: Failed to reinitialise Mule after the Application Context was refreshed
      MULE-6060Do not always serialize Mule session security context
      MULE-2751SpringConfigurationBuilder does not preserve container contexts from a mule configuration
      MULE-5666mule application properties should be available in mule registry
      MULE-6811Mule is unable to deploy applications
      MULE-2803Improve access to application context in MuleXmlConfigrationBuilder
      MULE-666MuleEventMulticaster - cannot reinitialise after context reload
      MULE-6247Custom transformers are not registered on mule context
      MULE-6289Mule Context missing when receiving a message on TCP inbound endpoint
      MULE-7008Private flow sends duplicate message when replyTo property is set

      Activity

        People

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

          Dates

          • Created:
            Updated:
            Resolved:

            Development