commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bob mcwhirter <...@werken.com>
Subject RE: [PATCH] Jelly - startup scripts and ideas
Date Mon, 08 Jul 2002 14:58:27 GMT
> 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:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message