I already sent in a news article for Excalibur release. Please submit followups so that they can post it soon! Use the following text: ------------------------------------------------------- <h1>Avalon Excalibur 4.0 Released</h1> <p> The Avalon team is proud to announce the 4.0 final release of the Avalon Excalibur. </p> <h2>About Avalon</h2> <p> The Avalon project is Apache's Java Server Framework. It is separated into five sub projects: Framework, Excalibur, LogKit, Cornerstone, and Phoenix. Its purpose is to simplify server side programming for Java based projects. It formalizes serveral best of breed practices and patterns for server side programming. </p> <p> For more information about Avalon, please go to <a href="http://jakarta.apache.org/avalon/";>http://jakarta.apache.org/avalon</a> </p> <h2>About Avalon Excalibur 4.0</h2> <p> Avalon Excalibur contains several premade Avalon Components and utilities to make your server side programming easier. There are several pool implementations, Component management implementations, and database management implementations. </p> <p> For more information about Avalon Excalibur 4.0, please go to <a href="http://jakarta.apache.org/avalon/excalibur/";>http://jakarta.apache.org/avalon/excalibur</a> </p> <p> ChangeLog for Avalon Excalibur 4.0 <ul> <li>Update user docs. [BL]</li> <li>Remove dead code in scratchpad. [PD]</li> <li>Rework thread pooling package to a new design. This provides a mechanism to run a cleanup thread when the JVM is killed. [PD]</li> <li>Add classloader extension framework into the extension package. [PD]</li> <li>Add Container mechanism from Avalon Phoenix. [PD]</li> <li>Add support for recursive property resolution. Added appropriate unit test to accompany feature. (Property utils). [PD]</li> <li>Problem Fixed: I've encountered a problem with the SingleThreadedPool in that it alternatley returns valid and null pooled objects until you've got the "initial" constructor argument + 1 and then it starts returning (Poolable)m_factory.newInstance(). Submitted by: "Corey O'Donovan". [PD]</li> <li>Fix some bugs found by Pool Profiling tests. [BL]</li> <li>Add new resource monitoring facility. This allows you to actively monitor resources and be notified if they are changed by outside forces. [BL]</li> <li>Set hierarchy via constructor to allow LogKit to work in sub classloaders. Submitted By: Sylvain Wallez. [DP]</li> <li>Update FileUtils with methods to count size of a directory, input argument check, fix javadoc, and method to convert an array of Files into URLs. [DP]</li> <li>ClassLoaderObjectInputStream moves from Cornerstone to Excalibur. [PH]</li> <li>Promote the i18n ResourceManager code to Excalibur production. [DP]</li> <li>Updated log messages for JdbcConnection--as well as added runtime detection if no connections could be created. This provides better reporting if the connection has configuration errors or other mitigating errors. [BL]</li> <li>Add direct support for Informix connection pooling. Requires the most recent JDBC drivers from Informix to use this feature. [BL]</li> <li>Deprecated the oradb attribute in JdbcDataSourceComponent, and added a keepalive element.This way we can test the line with valid SQL statements no matter what the DB is. Informix had trouble with the "select 1" and I am sure there are others. [BL]</li> <li>Fix bugs found by ReadWriteLock Test Case in the concurrent package. [BL]</li> <li>Update component package with support for Paremeterizable components (patch from Mircea Toma) [DP]</li> <li>Add support to display if an option is required. Patch was from Tom Jordahl (from xml-axis project). [BL]</li> <li>Fixed bug "CLArgsParser loops infinitely on OPTIONAL options" like "-Fa -B" where F optionally has an argument. Added unit tests to verify that it has been fixed. [PD]</li> <li>Update javadocs with '@since' tags so that we know when components have been introduced. [JT]</li> <li>Update JDBC datasource component so that you can specify your keep-alive query. This is for databases that don't like "SELECT 1;" as a query. [BL]</li> <li>Add new JUnit TestCase for automatically setting up Avalon Components and running tests. [GP]</li> <li>Fix a number of tests, and provided a couple new tests. [BL]</li> <li>Fix build process for tests and fix some of the tests. [PD]</li> <li>Add new LogKit Management framework to allow each component to have unique logger implementations and provide fine grained control over logging. [GP]</li> <li>Add new JNDI package to Excalibur with Memmory and RMI providers. [PD]</li> <li>Updated Announcement.xml to not refer to Testlet anymore. [BL]</li> </ul> </p> <p> Downloads for Avalon Excalibur 4.0 available at <a href="http://jakarta.apache.org/builds/jakarta-avalon/release/excalibur/latest";>http://jakarta.apache.org/builds/jakarta-avalon/release/excalibur/latest</a> </p> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
