JIRA

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Use Agile By Default
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile Access more options (Alt+g)
  • Create Issue
  • Mule
  • MULE-4813

Consider managing full lifecycle for the spring registry

  • Agile Board
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: Product Backlog
  • Fix Version/s: None
  • Component/s: Core: Lifecycle
  • Labels:
    None
  • User impact:
    Low
  • Migration Impact:
    none
  • Similar Issues:
    None

Description

Right now the spring container manages initailise and dispose of Mule objects, this means there is slightly different phasing depending on whether a connector is in the Spring Registry and the Transient Registry. We cope with it, ubt it might be cleaner to manage all lifecycle transitions from Mule.

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Transitions
  • Commits
  • Source
  • Builds
There are no comments yet on this issue.

People

  • Assignee:
    Unassigned
    Reporter:
    Ross Mason
Vote (0)
Watch (0)

Dates

  • Created:
    25/Mar/10 09:21 AM
    Updated:
    18/Oct/10 02:27 PM

Agile

  • View on Board
  • Atlassian JIRA (v5.0.7#734-sha1:8ad78a6)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.