Serge Knystautas wrote:
> >>How does depending on Avalon Framework limit reusability? You'll have a
> >>really tough time convincing me here...
>
> I'll try my best. It's mainly a question of what it takes to be able to
> start using components, namely having a container to run the Avalon
> framework.
Absolutely right!
[snip]
> Maybe if someone contributes a servlet context listener to be an Avalon
> container in webapps, an ant-based container, also very important -
What your describing is one of the driving factors that resulted in
the creation of "Merlin" .. a tool used to run a component from an
Ant build file. For example:
<target name="demo">
<load target="org.apache.time.TimeProvider" priority="DEBUG"
disposal="false" verbose="true">
<fileset dir="${lib}">
<include name="*.jar"/>
</fileset>
</load>
</target>
It basically reads a .xinfo file (same as Phoenix style
plus some extensions to handle default configuration info and
context declaration). The main difference between Merlin and
Phoenix is that Merlin handles cascading configurations which
means you can run up a component without any of the config,
or assembly stuff. Phoenix is a lot more powerful when you
start dealing with managing the source of service provision -
however, Merlin is a lot easier to tie into a development
cycle. A the moment Merlin needs to go through the Excalibur
repackaging. If your want something immediately, then a working
version of Merlin (including demo and documentation) is
available under:
jakarta-avalon-apps/enterprise/tools
Cheers, Steve.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
