App Product Table

Content-Type: multipart/mixed; boundary="------------070408080807020700030305" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --------------070408080807020700030305 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Leo Simons wrote: > > +100! I also kind-of had the idea to do a bit more integration of the > excalibur and cornerstone website, perhaps do a common catalogue. > Quickly threw up http://avalon.apache.org/components/index.html for that. > > Be sure to harvest > http://www.osm.net/technical/avalon/docs/avalon.html (Steve, can you > provide the sourcefiles to those?) :D > Sure - attached. Steve. -- Stephen J. McConnell mailto:mcconnell@apache.org http://www.osm.net --------------070408080807020700030305 Content-Type: text/xml; name="apps.xml" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="apps.xml" App Product Table

Product	Version	Status	Notes
Corbaloc	1.0	BETA	Component supporting the management of corbaloc urls. Dependencies: apps orb 2.0; assembly 1.0
INS	2.0	BETA	Interoperable Naming Service Dependencies: apps orb 2.0; assembly 1.0
ORB	2.0	BETA	Componet based implementation of a CORBA 2.4 ORB. Dependencies: framework 4.1; assembly 1.0
PSS	2.0	BETA	Persistent state service (PSS). Dependencies: framework 4.1; assembly 1.0
Time	2.0	BETA	Component based implementation of the CORBA Time Service. Dependencies: excalibur datasource 1.0; excalibur pool 1.2
FTP Server	1.0	ALPHA	FTP server implementation. Dependencies: ????
HSQL	1.0	ALPHA	??? Dependencies: ????
Overlord	1.0	ALPHA	??? Dependencies: ????
Phyre	1.0	ALPHA	??? Dependencies: ????
Servac	1.0	ALPHA	??? Dependencies: ????
XCommander	1.0	ALPHA	??? Dependencies: ????

--------------070408080807020700030305 Content-Type: text/xml; name="avalon.xml" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="avalon.xml" Avalon Product Table

Product	Version	Status	Notes
Framework	4.1.1	RELEASED	Avalon component model API (pre-Service package).
	4.1.2	WITHDRAWN	Basically 4.1.2 is a badly packaged release that should be ignored - it was intended to include the service package but the release was stuffed up somewhere along the line resulting in the release of 4.1.3 that fixed the problem.
	4.1.3	RELEASED	Includes the service package which replaces the component package (delivering a significantly more open solution and reduced framework dependency).

Product	Version	Status	Notes
Framework	5.0	ALPHA	Work in progress relating to the clean client component API based on the knowlege aquired through the V4 process.

--------------070408080807020700030305 Content-Type: text/xml; name="containers.xml" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="containers.xml" Phoenix Product Table

Product	Version	Status	Notes
Phoenix	4.0.3	RELEASED	App server that provides support for delopment of applications built using a Phoenix metainfo descriptor.
	CVS HEAD		Substantial changes exist in the CVS HEAD version including incorporation of a number of alpha products (Containerkit, Info, loader, etc.). This changes enable inital support for auto assembly, will provide improved meta info management, and enable configurable classloaders.

Product	Version	Status	Notes
Fortress	1.0	CANDIDATE	Fortress is a replacement for Excalibur's component package. It makes it easier to build your own scalable containers. It separates the Container logic from the component accessor logic.

Product

Version

Status

Notes

Merlin

2.1

ALPHA

A next generation container providing:

leverages and enhances the notion of meta based management from phoenix and the work on Merlin 1.0 and 2.0
provides support for dynamic component assembly and deployment
manages a set of "blocks" (where a block is a container hierachy that can contain components and other blocks - and is itself a component)
containers represent the runtime management environment for the set of contained components - it provides support for orderly component startup and shutdown
full support for different component lifestyles
suppport for pluggable lifecycle strategies
fully embeddable
existing support for Phoenix components

With planned support for:

ECM/Fortress components
block level asembly
remote service integration

--------------070408080807020700030305 Content-Type: text/xml; name="facilities.xml" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="facilities.xml" Avalon Product Table

Product	Version	Status	Notes
cli	1.0	RELEASED	The CLI component is a set of classes that allow you to parse command line arguments. It parses command line arguments that conform to the GNU "standard" for command line arguments. Dependencies: none
component	1.0	RELEASED	This project contains utilities for managing components. In particular, the ExcaliburComponentManager. Based on mailing list opinions, this package is not longer maintained and the objectives are to provide the Fortress package as a replacement. Dependencies: framework 4.1; logkit 1; event 1.1; collections 1.0; logger 1.0; pool 1.2; i18n 1.1
datasource	1.0	RELEASED	Used within the Cocoon and Cornerstone projects which is turn is used within the James project. Contains some alpha level jars. Dependencies: framework 4.1.3; logkit 1; pool 1.2
event	1.0.1	RELEASED	This is the Excalibur Event package which includes event queues, asynchronous command processing, and the interfaces to support event based programming. Fortress uses this project to manage the components and its pools outside of the direct thread of execution. Dependencies: framework 4.1.3; logkit 1; pool 1.2
i18n	1.0	RELEASED	The i18n component is a set of classes that allow you to manage internationalization in your projects. Dependencies: none
	CVS	CANDIDATE	Minor update to ResourceManager to enable explicit declaration of locale. Dependencies: none
logger	1.0	RELEASED	Logging utilities. Dependencies: framework 4.1.3; logkit 1
monitor	1.0	RELEASED	Monitor is a component that will actively notify you if a resource has changed. For example, if you are caching data in Files, Monitor will let you know when to update your cache with an event. It is designed to reduce the number of system calls in highly concurrent environments. Dependencies: framework 4.1; logkit 1.0; logger 1.0; sourceresolve 1.0
naming	1.0	RELEASED	Utilities suport simplified management of a JNDI context. Dependencies: none
pool	1.1	RELEASED	Support for object pools. Dependencies: framework 4.1; i18n 1.1
thread	1.0	RELEASED	Utilities supporting thread management. Dependencies: framework 4.1; threadcontext 1.0; pool 1.2; collections 1.0
	1.1	CANDIDATE	The 1.1 version includes changes to the thread pool constructor that ensures max pool usage policy is propergated.
threadcontext	1.0	RELEASED	The ThreadContext defines a set of data that is associated with a particular thread. In particular this is useful as a location to centralize management of ThreadLocal-type variables. As such the type of data contained in ThreadContext is usually data such as ContextClassLoader, Transaction ID, User ID/Subject, etc. Dependencies: none

Product	Version	Status	Notes
bzip2	1.0	DEPRICATED	Package has been moved to Jakarta Commons Sandbox under the package org.apache.commons.io.compress.bzip2.*
collections	1.0	DEPRICATED	This package has been copied in the Jakarta Commons Sandbox under the project collections. The new package name is org.apache.commons.collections.* No vote on migration has been taken at the Avalon level. The Avalon Collections API is in use with client projects.
io	1.1	DEPRICATED	This package has been copied in the Jakarta Commons Sandbox under the project io. The new package name is org.apache.commons.io.*
tar	1.0	DEPRICATED	This package has been copied in the Jakarta Commons Sandbox under the project io. The new package name is org.apache.commons.io.compress.tar.*
zip	1.0	DEPRICATED	This package has been copied in the Jakarta Commons Sandbox under the project io. The new package name is org.apache.commons.io.compress.zip.*

--------------070408080807020700030305 Content-Type: text/xml; name="development.xml" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="development.xml" Avalon Product Table

Product	Version	Status	Notes
Altrmi	0.8	ALPHA	Alternative remote method invocation.
baxter	1.0	ALPHA	Baxter is a set of base classes and utility classes that enable rapid creation of MBeans via delegation and inheritance. These were originally derived from the Phoenix project.
cache	1.0	ALPHA	The Cache component is a set of classes that allow you to cache objects to memory. It gives you a flexible and plugable API to allow you to specify the exact policies you want.
configuration	1.0	CANDIDATE	Utilities supporting the management of Avalon Configurations. Used within Merlin and Phoenix.
converter	1.0	ALPHA
csframework	1.0	ALPHA	C# implementation of the Avalon framework.
extension	1.0	ALPHA	Utility classes used to manage jar file depedencies. Used with Phoenix and Merlin.
instrument	1.0	ALPHA	Classes supporting instrumentation of a component. Currently has depedencies on AltRMI which can be removed. Is used by several projects.
jprocess	0.99	ALPHA
loader	1.0	ALPHA	Classloader utilities used with Phoenix.
sourceresolver	1.0	CANDIDATE	The source resolver of Avalon Excalibur is a component helping you in the task of finding a source using a URI. It resolves sources from a given URI. The URI can use all available protocols of the JRE. In addition own protocols can be plugged-in. So using the standard protocols like HTTP, FTP or file can be handled in the same way, like dealing with custom, self-build protocols such as myxmldatabase://root/documents/test.xml. The main advantage in comparisson to the mechanisms provided by the JRE is that the source resolver can be used without any problems with web application servers. Each web application can use it's own configured version of this component avoiding any possible conflicts between these applications. Dependencies: framework 4.1.3; pool 1.2
policy	1.0	ALPHA	Security policy management.
store	1.0	CANDIDATE	???
util	1.0	ALPHA	utilities that are either legacy, or new. Usually the utilities that have been hosted here have been moved to a new location that better fits their purpose. For example, SystemUtil has been moved to "Event". The Delegate stuff in there is new, and it is working, but it might be better to move into a larger context.
xfc		ALPHA	Project dealing with meta info conversion.
xmlutil	1.0	CANDIDATE	???

Product	Version	Status	Notes
Assembly	1.0	ALPHA	Generic container framework supporting meta driven component assembly, deployment, decommissioning and dissassembly. The assembly package is under active development and as such the API are changing. The API is used as the service and component management engine within the Merlin 2.1 container. Features include: Type meta-info repository Service meta-info repository Deployment template (profile) meta-data repository Deployment manager (appliance) system Unified context/service management model Preliminary model for pluggable lifecycle strategies Dynamic component assembly services
Datasource	1.0	ALPHA	The Sandbox version is meant to correct some of the issues with the older version (Excalibur Datasource): Interface assumes one to one relationship with DB and the rest of the system. In the new version we have a DatabaseManager that will allow you to get a connection by name. Easier integration with javax.sql.DataSource implementations by DB vendors. All the "big boys" have very well tested connection pooling code developed and tested. We should be able to use it directly--without having to go through JNDI. Easier compilation--no need to distinguish between JDBC 3.0 and JDBC 2.0 because we will use dynamic proxies or PooledConnection style objects (references the connection instead of extending it). Pooling of prepared statements. This is something that has not been done yet.
Meta	1.0	BETA	Meta information and meta data classes used by the assembly package. Features include: Type meta-info classes Service meta-info classes Legacy meta-model support Meta builders and validators
Tweety	1.0	BETA	Tutorial product the demonstrations a minimal container.

--------------070408080807020700030305 Content-Type: text/xml; name="utilities.xml" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="utilities.xml" Logkit Product Table

Product	Version	Status	Notes
Logkit	1.0	RELEASED	LogKit is an easy to use logging toolkit designed for secure performance oriented logging. It's design encourages integration into existing products with minimal impact.
	1.1	RELEASED	Additional logging targets added to package together with some bug fixes to the implementation of the file rotation strategy.

--------------070408080807020700030305 Content-Type: text/xml; name="cornerstone.xml" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="cornerstone.xml" Cornerstone Product Table

Product	Version	Status	Notes
Connection	1.0	CANDIDATE	Component supporting connection management. Dependencies: cornerstone threads 1.0
Store	1.0	CANDIDATE	Component that provides support for selection from a number of configured repositories. Dependencies: framework 4.1; excalibur io 1.0
Scheduler	1.0	CANDIDATE	A component that provides support for job scheduling. Dependencies: framework 4.1
Sockets	1.0	CANDIDATE	A component that provides support for socket management. Dependencies: framework 4.1
Datasources	1.0	CANDIDATE	A component that provides support for data source selection. Dependencies: excalibur datasource 1.0; excalibur pool 1.2
Threads	1.0	CANDIDATE	A component that provides support for thread management. Dependencies: excalibur threads 1.0; excalibur threadcontext 1.1

--------------070408080807020700030305 Content-Type: text/plain; charset=us-ascii --------------------------------------------------------------------- To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: avalon-dev-help@jakarta.apache.org --------------070408080807020700030305--