If that is true, can event based programming be done in merlin?
Ineed more context to give you an answer. There is a terribly easy *yes* because anything can be done in Merlin - but to give you a real answer I need a bunch more information about what you want to do and the relationship concerning container/component contract.
Of course it can, but there is one little exception I don't catch. In a Fortress/ExcalibutEvent environment, you write components which are discovered by the DefaultStageManager configuration and put into the pipeline. This is automatically achieved in Fortress because every component as visible to each other. But in Merlin, you'll have to declare every dependency inside the DefaultStageManager using meta tag (or overwrite the .xinfo file). This means overwriting the event code, having something like /org/apache/excalibur/event/seda/DefaultStageManager.xinfo in you own code... and this doesn't seem right, even if more IoC friendly because the manager should register the components it uses.
I have been scratching my head many times to solve this usecase, so please, contradict me!
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
