I'm new to the avalon framework. Please bear with me.

I'm thinking of using merlin2 to build an application
with the following
services/components:
0. application
1. model
2. controller
3. view

An application container is also created to manage
these components. For a
standalone application, these components all reside in
the container. In other
scenarios, the view part will be split from the
model/controller part, ie, they
will stay in separate containers. This means another
component, eventsysem,
will be used by the controller and the view to
communicate with each other.

I do expect various implementations of these
components are used for different
scenarios.

This is the skeleton of the startup.xml file:
<kernel>
...
  <component name="es" class="DefaultEventSystem"
activation="startup">
  </component>
  <container name="ac" class="ApplicationContainer">
    <component name="controller" 
           class="DefaultController" 
           enabled="true" 
           activation="true">
    </component>
    <component name="model" 
           class="DefaultModel" 
           enabled="true" 
           activation="true">
    </component>
    <component name="view" 
           class="DefaultView" 
           enabled="true" 
           activation="true">
    </component>
  </container>
...
</kernel>

Here are some of my questions.
1. It appears that I need to first start the
eventsystem in the root container,
   ie, outside of the application container. Am I on
the right track?
2. How do I pass the eventsystem to the application,
as a context,
   configuration, or parameter? Or should the
eventsystem be a dependency of
   the application?
3. How do I configure a non-default component,
preferrably outside the
   startup.xml file?

Thanks for your help.

Cheers,
Albert

=====
Regards,
Albert

__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to