> But it doesn't seem to support the desired functionality, namely specifying
> all the jar files in a particular directory. This seems like a
> clearly-useful addition, given how common this is.
It supports globs.
${foo.home}/lib/*.jar
${foo.home}/lib/*.zip
> Also, I would recommend switching to an XML-based configuration file. This
> has several advantages:
Yah, it also requires knowing where some xml parser's jar is. chicken/egg.
I tried to keep forehead so it has no dependencies.
> But I think a common infrastructure for creating hierarchies of
> classloaders, both declaratively and dynamically, is clearly a valuable
> idea.
I've recently added some stuff to Forehead to all you access
to the Forehead instance during run-time. So, now you can create
sandboxed classloaders, or whatnot, at run-time.
-bob
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
