> We'll note your desire to no longer refer to JAMES as if it were *our*
> project.
Well, it is yours in-so-far as you want to participate in that community
(you are welcome to come back at any time). :-) And it does consume the
range of Avalon (the project) technologies. As for confusing casual
readers, I think that more than just casual readers are confused about
various aspects of something as "basic" to building applications using
Avalon technologies as Context and Compose.
As a part of moving towards Avalon 5, I'd like to see the core notions
revisited and clarified as an essential exercise towards defining the
architecture and design.
> .... please differentiate between 'Avalon' (a project which is a
> collection of tools), 'Avalon-Framework' (a set of very reusable
> component interfaces), and Avalon-Framework recognising containers (such
> as Phoenix).
Is this really a particularly useful distinction, except to indicate where
there are differences within the Avalon community?
Avalon is the Community Project, whose intent is to provide a
container-based model of application development. To do so the Community
develops and publishes a Framework and [current: set of containers / future:
scalable, profiled, container]. What is Java? The language, the library or
the JVM? Which profile? J2ME, J2SE and J2EE?
What is Avalon? IMO, it is the Community, the architecture, and the
technologies that implement it.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
