Leo Simons wrote:
class MyComponent implements Configurable { public void configure( Configuration config ) { new Thread( getNewWorker() ).start; // quite possible. Wrong, but // possible m_val = config.getChild("blah").value(); } }
We have invented an application framework on top of Avalon to prevent things like that. Yes, we thought about contributing that to Avalon, but it's pretty hard to come up with something sufficiently general.
most interesting! May I ask how? SecurityManager or something like that (hmm, would that work...)? Also, may I ask why? You run untrusted components?
- LSD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
