Users guide
Architecture
Demo applications
Plugins
Porting Guide
Development Roles
Introduction
Administrator
Deployer
Assembler
Block Developer
Project Info
License
Mailing lists
IRC
Source repositories
Issue tracking
Blog entries
Team
 |
|
Blogs
Loom RC3 Released!
The Loom development team is proud to announce RC3 of the Loom application server.
RC3 represents the last release prior to 1.0. If no show stopper bugs are reported, 1.0 will be released in two weeks time.
Loom is fully backwards compatible with applications from Phoenix 4.0.
Downloading
Souce and Binary distributions can be downloaded here.
About Loom
Loom is a micro-kernel designed and implemented on top of the DNA framework and supports components developed using the Avalon.
Loom provides a number of facilities to manage the environment of Server Applications. Such facilities include log management, classloading, thread management and security. In the future it will conditionally support extra facilities such as central server management, server pools, and other facilities aimed at reducing the time to market.
The API defines a standard method of piecing together server components and creating a server.
Posted at Feb 15, 2005 by
peter royal |
0 comments
Loom RC1 Released!
The Loom development team is proud to announce RC1 of the Loom application server.
RC1 represents the (hopefully) last release prior to 1.0. This marks the first public release of a container based upon the un-released Apache Avalon Phoenix 4.1 development branch.
Loom is fully backwards compatible with applications from Phoenix 4.0.
Downloading
Souce and Binary distributions can be downloaded here.
About Loom
Loom is a micro-kernel designed and implemented on top of the DNA framework and supports components developed using the Avalon. In the future Loom will support DNA and Pico components.
Loom provides a number of facilities to manage the environment of Server Applications. Such facilities include log management, classloading, thread management and security. In the future it will conditionally support extra facilities such as central server management, server pools, and other facilities aimed at reducing the time to market.
The API defines a standard method of piecing together server components and creating a server.
Posted at May 17, 2004 by
peter royal |
0 comments
Copyright 2003-2006 - The Codehaus. All rights reserved unless otherwise noted.
Powered by Atlassian Confluence
[ edit ]