On Thursday 13 May 2004 02:09, Farr, Aaron wrote: > - It looks like this is off by default. Is this correct? Even if there > are entries in the kernel.xml?
Correct. > - How does this interact with a security policy given via the command line? > (ie -Djava.security.policy=$MERLIN_HOME/bin/security.policy) > > - Why? Why not just use a normal policy file? What does this security > give us? Sorry, I'm not a java security expert (my bad). Because we haven't been able to work it out, call it non-functional at the moment. The point was, that to provide a component level policy individual for each container. I.e. This component is trusted in that particular container, but no where else. I and Stephen decided to push the effort forward in time... (The side-effect became a dynamic composition model, and a simpler activation subsystem.) Niclas -- +---------//-------------------+ | http://www.bali.ac | | http://niclas.hedhman.org | +------//----------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
