On Tue, Jul 09, 2002 at 10:33:08AM -0400, Berin Loritsch wrote:
> > From: Leo Simons [mailto:[EMAIL PROTECTED]]
> >
> > What I'm not so sure about is whether it satisfies all use
> > cases. You've defined 4 stages in the component lifetime
> > where one can register an extension. But what if you want two
> > extensions in the same stage, in a specific order?
> >
>
> <SNIP/>
>
> If you want to mix and match extension types, there is something
> wrong in your design. One Extension helper class can support
> multiple stages in any order you want. Or at least it should be.
Yes, this is correct, an extension class can run a component through
as many lifecycle extensions as the developer has implemented.
At the moment the LifecycleExtensionManager class also exposes each
List that contains the extensions via getAccessExtensions()/etc
methods so it's currently possible to insert new extensions sets
before those already registered.
(I'm debating about this exposure though because IIRC 'Refactoring'
says this breaks encapsulation, perhaps I should just implement a
subset of the List operations instead).
Cheers,
Marcus
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: ManageSoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&'
&&&&.
&&&&&&&:
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
