Ferguson, Doug wrote:
There are several differences:My collegues & I have built an avalon application but we do so prior to any suitable container being aviable.
We are currently considering the possibility of dropping in Merlin.
It seems like a suitable fit, however I am trying to get a good understanding of all the features of Merlin. I am hung up on one particular thing....
What is the difference between Contextualization Stage Handlers and Lifecycle Extentions?
* there is only one contextualization stage handler wheras there can be multiple lifecycle extensions
* the contextualization handler includes classic context entries (i.e. the contract is more specific)
* lifecycle extensions are a more general notion and more portable
* contextualization customization is merlin specific
The only difference I can see is the interface that is used by the handler. I guess I am not understanding the usage patterns.
Right now, our "homebrew container" creates a dynamic configuration based on
the configuration file and the contents of a db.
I am thinking that a speciallized context could easily perform this
function, but I would have to refactor the code to not use configuration.
Is there a way to have custom configuration handlers?
No currently - basically the custom contextualization handler is a successfull experiment in how to deal with specific lifecycle stage handling. The next step is to (a) generalize the other handlers (e.g. configuration) is the same way, leading to (b) redefinition of a lifecycle as an order series of stages. But that's probably a while away (too many other things to be done in the meantime).
Stephen.
d./
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
