On 15/02/2010 14:42, Konstantin Kolinko wrote:
Thanks for the feedback. All my comments below are preliminary ideas I
have had whilst trying to figure out how best to clean this up. Nothing
is absolute at this stage but whichever way I thought of things adding
Lifecycle to Container always seemed
+1 works for me
On 02/15/2010 03:23 AM, Mark Thomas wrote:
Currently, Lifecycle is an optional interface for components. I'd like
to make it mandatory for Server, Service and Container.
My reasons for this are:
1. Much of the current implementation depends on Lifecycle (e.g. JNDI,
configuration
2010/2/15 Mark Thomas :
> Currently, Lifecycle is an optional interface for components. I'd like
> to make it mandatory for Server, Service and Container.
+1, Let's make it mandatory.
I agree with 1.,2.,3. of your reasons.
Cannot comment on 4. as I do not know that subject. Is there any
outline
Currently, Lifecycle is an optional interface for components. I'd like
to make it mandatory for Server, Service and Container.
My reasons for this are:
1. Much of the current implementation depends on Lifecycle (e.g. JNDI,
configuration) and breaks if the component doesn't implement Lifecycle
2.
