You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scm@excalibur.apache.org by le...@apache.org on 2004/06/18 04:12:11 UTC
svn commit: rev 21399 - excalibur/trunk/site/xdocs
Author: leif
Date: Thu Jun 17 19:12:10 2004
New Revision: 21399
Modified:
excalibur/trunk/site/xdocs/index.xml
Log:
Reformat the XML. No other changes.
Modified: excalibur/trunk/site/xdocs/index.xml
==============================================================================
--- excalibur/trunk/site/xdocs/index.xml (original)
+++ excalibur/trunk/site/xdocs/index.xml Thu Jun 17 19:12:10 2004
@@ -1,182 +1,182 @@
<?xml version="1.0"?>
<document>
-
+
<properties>
<author email="dev@avalon.apache.org">Avalon Documentation Team</author>
<title>Excalibur i18n</title>
</properties>
-
+
<body>
-
+
<section name="Excalibur">
-
+
<subsection name="Overview">
- <p>
- The Excalibur Project contains a set of utilitiy projects
- used in the development of container facilities and as
- underlying system for cause-grain components such as the
- Cornerstone suite.
- </p>
+ <p>
+ The Excalibur Project contains a set of utilitiy projects
+ used in the development of container facilities and as
+ underlying system for cause-grain components such as the
+ Cornerstone suite.
+ </p>
</subsection>
<subsection name="Index">
- <table>
- <tr><th>Package</th><th>Description</th></tr>
- <tr><td><a href="configuration/index.html">Configuration</a></td><td>
- <p>
-The Configuration package contains extensions to the Avalon Framework
-supporting configuration management.
- </p></td></tr>
- <tr><td>Datasource</td><td>
- <p>
- Avalon Excalibur's DataSource package in
- <code>org.apache.avalon.excalibur.datasource</code> allows you
- to manage pooled connections in one of two ways. You can have
- the package handle it for you, or you can use a J2EE server's
- DataSource management. It provides the same kind of access
- regardless of which method you choose--since they are obtained
- through Avalon's Component Manager infrastructure.
- </p>
- </td></tr>
- <tr><td>Event</td><td>
- <p>
- This is the Excalibur Event package which includes event queues,
- asynchronous command processing, and the interfaces to support
- event based programming. Event is heavily influenced by Matt
- Welsh's work with the
- <fork href="http://www.cs.berkeley.edu/~mdw/proj/seda/">SEDA architecture</fork>.
- We forked the portion of his SandStorm server that had to do with
- event processing. From there we cleaned up the API and made it as
- generic as we could.
- </p>
- </td></tr>
- <tr><td><a href="i18n/index.html">i18n</a></td><td>
- <p>
- Excalibur's Internationalization package is found in
- <code>org.apache.avalon.excalibur.i18n</code>. Avalon
- Excalibur includes a method of managing resources, and
- an interface for specifying the resource. Support for
- XML resource bundles are still under development.
- </p></td></tr>
- <tr><td>Instrumentation</td><td>
- <p>
- Excalibur Instrument is an instrumentation utility that allows you
- to attach a separate JVM to your running application to determine its
- health. Instrumentation is the process of exposing the internal state
- in a way that is easy for an administrator or help desk personell to
- digest. Excalibur Instrumentation is such a package that you can use
- for your Avalon based projects.
- </p>
- </td></tr>
- <tr><td>Lifecycle</td><td>
- <p>The Lifecycle package contains a set of interfaces and classes supporting portable lifecycle extensions.</p>
-
- <p>Contributions to this project are based on co-development actives by container projects aiming towards cross-container component portability and consistent service management.</p>
- </td></tr>
- <tr><td>Logger</td><td>
- <p>
- Find Avalon Excalibur's Log Management System in the
- <code>org.apache.avalon.excalibur.logger</code> package.
- Excalibur-Logger integrates neatly into the Avalon ECM
- and Fortress. The main goal is to
- be able to define the log categories on a component basis by
- specifying a 'logger' attribute which denotes the log category
- to use for a particular component (given the
- component is <code>LogEnabled</code> or <code>Loggable</code>).
- </p>
- </td></tr>
- <tr><td>Monitor</td><td>
- <p>
- Avalon Excalibur's resource management code allows you to
- be notified when a resource has changed. There are two
- methods of resource management: active and passive. Passive
- resource management acts as a holder for resources, and after
- the resource has been modified through it's normal API,
- notification goes to all listeners. Active resource management
- does the same, but it also polls the resources periodically
- to see if the resource was modified through an external method.
- Active resource management is perfect for monitoring files
- because they can be modified by external programs, and your
- program will be notified when the change occurs instead of
- constantly polling it.
- </p>
- </td></tr>
- <tr><td>Pool</td><td>
- <p>
- Find Avalon Excalibur's Pool implementations in the
- <code>org.apache.avalon.excalibur.pool</code> package.
- There are many implementations that are ThreadSafe, and
- one that is not. You have the option of not limiting
- used resources at all, or limiting the used resources
- based on specific rules.
- </p>
- </td></tr>
- <tr><td><a href="sourceresolve-index.html">Sourceresolver</a></td><td>
- <p>
- A very common problem is resolving a source, which means
- finding a source using a URI.
- </p>
- <p>
- The source resolver of Avalon Excalibur is a component
- helping you in this task. 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.
- </p>
- </td></tr>
- <tr><td><a href="store-index.html">Store</a></td><td>
- <p>
- The Store Package provides a way to store named objects without
- taking care about where and how they are stored.
- You can choose between different implementations that store
- the data e.g. in memory or on the file system etc.
- </p>
- </td></tr>
- <tr><td>Thread</td><td>PENDING</td></tr>
- <tr><td>XMLUtil</td><td>
- <p>
- Excalibur's XML Utilities provide simplified wrappers
- for XML parsers, transformers and XPath evaluators. It
- also provides interfaces and classes useful for
- constructing a pipeline of XML components by defining interfaces
- for consuming and producing XML in either SAX or DOM formats.
- </p>
- </td></tr>
- </table>
+ <table>
+ <tr><th>Package</th><th>Description</th></tr>
+ <tr><td><a href="configuration/index.html">Configuration</a></td><td>
+ <p>
+ The Configuration package contains extensions to the Avalon Framework
+ supporting configuration management.
+ </p></td></tr>
+ <tr><td>Datasource</td><td>
+ <p>
+ Avalon Excalibur's DataSource package in
+ <code>org.apache.avalon.excalibur.datasource</code> allows you
+ to manage pooled connections in one of two ways. You can have
+ the package handle it for you, or you can use a J2EE server's
+ DataSource management. It provides the same kind of access
+ regardless of which method you choose--since they are obtained
+ through Avalon's Component Manager infrastructure.
+ </p>
+ </td></tr>
+ <tr><td>Event</td><td>
+ <p>
+ This is the Excalibur Event package which includes event queues,
+ asynchronous command processing, and the interfaces to support
+ event based programming. Event is heavily influenced by Matt
+ Welsh's work with the
+ <fork href="http://www.cs.berkeley.edu/~mdw/proj/seda/">SEDA architecture</fork>.
+ We forked the portion of his SandStorm server that had to do with
+ event processing. From there we cleaned up the API and made it as
+ generic as we could.
+ </p>
+ </td></tr>
+ <tr><td><a href="i18n/index.html">i18n</a></td><td>
+ <p>
+ Excalibur's Internationalization package is found in
+ <code>org.apache.avalon.excalibur.i18n</code>. Avalon
+ Excalibur includes a method of managing resources, and
+ an interface for specifying the resource. Support for
+ XML resource bundles are still under development.
+ </p></td></tr>
+ <tr><td>Instrumentation</td><td>
+ <p>
+ Excalibur Instrument is an instrumentation utility that allows you
+ to attach a separate JVM to your running application to determine its
+ health. Instrumentation is the process of exposing the internal state
+ in a way that is easy for an administrator or help desk personell to
+ digest. Excalibur Instrumentation is such a package that you can use
+ for your Avalon based projects.
+ </p>
+ </td></tr>
+ <tr><td>Lifecycle</td><td>
+ <p>The Lifecycle package contains a set of interfaces and classes supporting portable lifecycle extensions.</p>
+
+ <p>Contributions to this project are based on co-development actives by container projects aiming towards cross-container component portability and consistent service management.</p>
+ </td></tr>
+ <tr><td>Logger</td><td>
+ <p>
+ Find Avalon Excalibur's Log Management System in the
+ <code>org.apache.avalon.excalibur.logger</code> package.
+ Excalibur-Logger integrates neatly into the Avalon ECM
+ and Fortress. The main goal is to
+ be able to define the log categories on a component basis by
+ specifying a 'logger' attribute which denotes the log category
+ to use for a particular component (given the
+ component is <code>LogEnabled</code> or <code>Loggable</code>).
+ </p>
+ </td></tr>
+ <tr><td>Monitor</td><td>
+ <p>
+ Avalon Excalibur's resource management code allows you to
+ be notified when a resource has changed. There are two
+ methods of resource management: active and passive. Passive
+ resource management acts as a holder for resources, and after
+ the resource has been modified through it's normal API,
+ notification goes to all listeners. Active resource management
+ does the same, but it also polls the resources periodically
+ to see if the resource was modified through an external method.
+ Active resource management is perfect for monitoring files
+ because they can be modified by external programs, and your
+ program will be notified when the change occurs instead of
+ constantly polling it.
+ </p>
+ </td></tr>
+ <tr><td>Pool</td><td>
+ <p>
+ Find Avalon Excalibur's Pool implementations in the
+ <code>org.apache.avalon.excalibur.pool</code> package.
+ There are many implementations that are ThreadSafe, and
+ one that is not. You have the option of not limiting
+ used resources at all, or limiting the used resources
+ based on specific rules.
+ </p>
+ </td></tr>
+ <tr><td><a href="sourceresolve-index.html">Sourceresolver</a></td><td>
+ <p>
+ A very common problem is resolving a source, which means
+ finding a source using a URI.
+ </p>
+ <p>
+ The source resolver of Avalon Excalibur is a component
+ helping you in this task. 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.
+ </p>
+ </td></tr>
+ <tr><td><a href="store-index.html">Store</a></td><td>
+ <p>
+ The Store Package provides a way to store named objects without
+ taking care about where and how they are stored.
+ You can choose between different implementations that store
+ the data e.g. in memory or on the file system etc.
+ </p>
+ </td></tr>
+ <tr><td>Thread</td><td>PENDING</td></tr>
+ <tr><td>XMLUtil</td><td>
+ <p>
+ Excalibur's XML Utilities provide simplified wrappers
+ for XML parsers, transformers and XPath evaluators. It
+ also provides interfaces and classes useful for
+ constructing a pipeline of XML components by defining interfaces
+ for consuming and producing XML in either SAX or DOM formats.
+ </p>
+ </td></tr>
+ </table>
</subsection>
<subsection name="Depricated">
- <table>
- <tr><th>Package</th><th>Description</th></tr>
- <tr><td>Compatability</td>
- <td>
- <p>
-Avalon is minimizing the number of projects and utilities it maintains
-because we need to focus on our charter. However, we do have users
-who have used some of the projects that were previously released. We
-can't just ignore their needs. The compatibility project is the
-graveyard for projects we are no longer supporting. It exists simply
-to let our users (and in some cases, our users' users) continue to
-use their legacy components until they migrate to better supported
-libraries.
- </p>
- </td>
- </tr>
- <tr><td><a href="component.html">Component</a></td><td>
- <p>
- Due to a number of issues in ECM, not the least of which is a
- simplistic and convoluted design, it has been deprecated in
- favor of Fortress or Merlin. Fortress has been designed with
- ECM users in mind, so it provides a number of goodies to make
- it easier to migrate forward. This project will be maintained
- for bug fixes only.
- </p>
- </td></tr>
- </table>
- </subsection>
+ <table>
+ <tr><th>Package</th><th>Description</th></tr>
+ <tr><td>Compatability</td>
+ <td>
+ <p>
+ Avalon is minimizing the number of projects and utilities it maintains
+ because we need to focus on our charter. However, we do have users
+ who have used some of the projects that were previously released. We
+ can't just ignore their needs. The compatibility project is the
+ graveyard for projects we are no longer supporting. It exists simply
+ to let our users (and in some cases, our users' users) continue to
+ use their legacy components until they migrate to better supported
+ libraries.
+ </p>
+ </td>
+ </tr>
+ <tr><td><a href="component.html">Component</a></td><td>
+ <p>
+ Due to a number of issues in ECM, not the least of which is a
+ simplistic and convoluted design, it has been deprecated in
+ favor of Fortress or Merlin. Fortress has been designed with
+ ECM users in mind, so it provides a number of goodies to make
+ it easier to migrate forward. This project will be maintained
+ for bug fixes only.
+ </p>
+ </td></tr>
+ </table>
+ </subsection>
</section>
-
+
</body>
-
+
</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: scm-unsubscribe@excalibur.apache.org
For additional commands, e-mail: scm-help@excalibur.apache.org