Carsten Ziegeler wrote:
Sylvain Wallez wrote:
A few questions that quickly popped up:
- is it implemented as a BeanPostProcessor that implements the Avalon
lifecycle interfaces?
Yupp, it's a DestructionAwareBeanPostProcessor to support Dispose and
Startable#stop.
- how is defined the configuration of a Configurable?
Configurable is still used by the Avalon components of course and this
used the same old xconf - so if you define Avalon components, use the
xconf, if you define "real" beans use the application context
definition. Both are merged into one big configuration file for spring.
You mean these are separate files each using their own format that are
merged in a single DOM for the ApplicationContext?
- how can a POJO access the Context: does it still have to implement
Contexualizable, or is the context available as a regular bean?
It's available as a bean, like the service manager or the logger are as
well.
Great.
- what is the format of the configuration file?
Two options: either old xconf/roles style (where old means 2.2 version
with included) and default spring xml configuration.
- what about ServiceSelectors?
Are simply wrappers around the bean factory which forward the lookup. So
looking up a "GeneratorSelector" and then select component "file" is the
same as looking up "Generator/file" from the bean factory or the
provided service manager. The service manager is a wrapper around the
bean factory as well.
Ah yes. I forgot that we already had flattened selectors in ECM++ :-)
Sounds good!
Sylvain
--
Sylvain Wallez Anyware Technologies
http://bluxte.net http://www.anyware-tech.com
Apache Software Foundation Member Research & Technology Director
