Issue Details (XML | Word | Printable)

Key: MULE-3102
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Dirk Olmes
Reporter: Dirk Olmes
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Mule

Remove retry logic from DefaultLifecyclePhase

Created: 10/Mar/08 05:40 AM   Updated: 31/Mar/08 04:36 PM
Component/s: Core: Lifecycle
Affects Version/s: 2.0.0-RC3
Fix Version/s: 2.0.0

Time Tracking:
Not Specified

Issue Links:
Block
 
Related

Labels:
User impact: Low


 Description  « Hide
DefaultLifecyclePhase has logic for retrying the current lifecycle phase. This all was added only to work around problems in agent startup (JmxAgent needs RmiRegistryAgent) but clutters the whole codebase. (See MULE-3002 why this doesn't work)

Remove the retry logic and implement some kind of ordering for the Agents. This can be something simple as putting a Comparator in the registry and use that to order the objects for the current lifecycle phase before actually sending the right lifecycle methods to them.



 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
Daniel Feist added a comment - 14/Mar/08 09:44 PM
Shouldn't we get rid of the retry mechanism now even if it needs a hack in JMXAgent so that we don't have to change API significantly by updating all life-cycle method signatures?

Dirk Olmes added a comment - 17/Mar/08 04:01 AM
Dan, you're absolutely right. I'm not sure whether it's worthwhile to hold back RC3 for this. Let's target the removal for 2.0.0 then.