avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen McConnell <mcconn...@apache.org>
Subject Re: [avalon] roadmap - library criteria
Date Thu, 04 Mar 2004 12:01:51 GMT
Carsten Ziegeler wrote:

> So, perhaps it would really be better to forget Fortress and move
> everything into Merlin but of course maintain the simplicity of
> Fortress. Embedding Fortress into an own application is four or
> five lines of Java code and some simple configuration file. That's
> it.

I've just committed an example of embedding merlin so that you can get 
an idea of things (available in avalon/merlin/platform/tutorials/main).

The example goes through the following steps:

   1. setup an application cache              -- 4 lines
   2. build the application classloader       -- 3 lines
   3. parameterize and deploy the application -- 3 lines

In general the same pattern applies for any repository enabled 
application.  The demonstration will run with or without a merlin 
install.  If merlin is installed the demo will use the existing merlin 
system repository, otherwise a new system repository will be created and 
populated automatically.  The actual bootstrapping is taken care of by 
the single jar file avalon-repository-main.

Cheers, Steve.


| Magic by Merlin                                |
| Production by Avalon                           |
|                                                |
| http://avalon.apache.org/merlin                |
| http://dpml.net/merlin/distributions/latest    |

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

View raw message