Howard M. Lewis Ship wrote:
I also saw a lot to like in Avalon, but was driven away by the need for an explicit assembly stage to identify all components and express the relationships between them.
Howard:
I had similar concerns that basically filtered down to a requirement for a couple of sub-systems within a containment API:
* auto-discovery of component types and services * auto-assembly using runtime context and deployment heuristics
What this means is that you can easily use deployment descriptions that are really compact. This is achieved by maintaining a registry of component type information pulled in from structural units (jar files), maintaining associations between type definitions and published services, and when the need arises, dynamically constructing deployment solutions based on packaged deployment profiles and type-level defaults.
Cheers, Stephen.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
