Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.2-RC1
-
Fix Version/s: 1.2
-
Component/s: PicoContainer (Java)
-
Labels:None
-
Number of attachments :
Description
The new lifecycleInvocationFailed event of the ComponentMonitor should also be supported by the ReflectionLCS in gems.
Activity

Field | Original Value | New Value |
---|---|---|
Summary | ReflectionLC does not support new lifecycleFailure event | ReflectionLCS does not support new lifecycleInvocationFailed event |
Description | The new lifecycleFailure event of the ComponentMonitor should also be supported by the ReflectionLC in gems. | The new lifecycleInvocationFailed event of the ComponentMonitor should also be supported by the ReflectionLCS in gems. |

Assignee | Mauro Talevi [ maurotalevi ] | Paul Hammant [ paul ] |

Assignee | Paul Hammant [ paul ] | Mauro Talevi [ maurotalevi ] |

Status | Open [ 1 ] | Closed [ 6 ] |
Resolution | Fixed [ 1 ] |
Cannot invoke CM#lifecycleInvocationFailed() for IllegalAccessException and InvocationTargetException as they
are checked exceptions and method expects RuntimeException as a param.
Two options:
1. change method signature to accept Exception
2. wrap checked exception as RuntimeException
I find 1. is preferrable and consistent with rest of CM method signatures.