Niclas Hedhman wrote:
Paul wrote
1) We strive for a lowest common denominator (LCD) approach with embracing of multiple value-added implementation, which may end up divergent without that being considered a failure. Thus A-F's Java interfaces are our point of unification. There is no single container. There is no unified assembly or configuration meta info specification at the application level. XML and other.
2) We drop a unified component-level meta info dependancy and
configuration design. XML and other.
The A/F is the LCD, but can slowly evolve to include such things as the dependency, configuration, assmebly and other issues. The direction of such evolution should be the result from the feedback from Merlin, Fortress, Phoenix, et al...
+1
Leveraging synergy and opportunity as and when it presents itself.
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
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
