avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berin Loritsch" <blorit...@apache.org>
Subject RE: [Commit] New Servlet and Creator tools in the component package
Date Wed, 21 Aug 2002 13:11:00 GMT
> From: Leif Mortenson [mailto:leif@tanukisoftware.com] 
> I went ahead and committed a couple of tools which I have 
> been using for 
> some time to ease the use of the ECM.
> 1)
> The first is the ExcaliburComponentManagerCreator class.  It 
> is used to 
> manage the entire lifecycle of the ECM, RoleManager, 
> LoggerManager and optionally the InstrumentManager.  And it 
> can all be done with the following code.  Much simpler than 
> having to everything manually each time it is used:
> Initialization:
> ---
> m_componentManagerCreator = new ExcaliburComponentManagerCreator(
>     null, // Optional Context
>     new File( "../conf/logkit.xml" ),
>     new File( "../conf/roles.xml" ),
>     new File( "../conf/components.xml"),
>     new File( "../conf/instrument.xml" ) );
> ---

You mean you don't want to use Fortress?  It has the same basic
approach, and is just as easy to use.

> 2)
> The second utility class is the 
> ExcaliburComponentManagerServlet.  It is 
> located in the servlet subpackage and built into a seperate jar file: 
> excalibur-component-servlet-1.0.jar
> The ECMServlet allows users who wish to use the ECM in a Servlet 
> environment to do so painlessly.

I would really like it if we started divorcing ourselves from ECM.

> The ExcaliburComponentManagerServlet makes use of a proxy system to 
> manage reference to the above managers, so it is not necessary to 
> release them when a servlet is done using them.


but can this be done for Fortress?

To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>

View raw message