You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by si...@avalon.apache.org on 2004/03/17 19:10:37 UTC

[Apache Avalon Wiki] New: AvalonStandards

   Date: 2004-03-17T10:09:52
   Editor: AaronFarr <fa...@apache.org>
   Wiki: Apache Avalon Wiki
   Page: AvalonStandards
   URL: http://wiki.apache.org/avalon/AvalonStandards

   Avalon Standards Considation Effort (ASCE)   :-)   -farra

New Page:

#pragma section-numbers off
= Avalon Standards =

The Avalon community recently voted to have a single platform.  The core Avalon framework has traditionally offered quite a bit of leniency to container developers by ''not'' specifying certain standards.  That has lead to various individual container standards which makes component reuse difficult if not impossible.  This document serves to assist the Avalon community in
  * Identifying the existing standards and usages in current containers (ECM, Fortress, Phoenix, Merlin)
  * Build consensus on a set of standards which will be held by all Avalon containers (ie- a TCK)
This is not an attempt to build from scratch new standards.  It is an attempt to identify existing approaches and develop a responsible way to both support our existing users (via backwards compatibility or migration tools) and to offer a consistent platform for the future of Avalon.

== Standardization Areas ==

''Niclas, you had a list at one point...''
  * Meta-Info
    * Component contract -- how users specify meta-info
    * Container contract -- how container developers or extension writers retrieve meta-info
  * Context Entries (see AvalonContextSurvey)
  * [add more here]

= Meta-Info =

''put existing meta-info approaches here, ideas for improvement...''

= Context Entries =

'' same thing...''  See AvalonContextSurvey

= More to come =

'' just setting up the basic structure here ''

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org