Looking some of the security policy files in the trunk, I'd say that you will probably need to add:
permission java.util.PropertyPermission "derby.YourSharedInfoPropertyName", "read, write"; for the derby.jar codebase...assuming the access to the shared system property will be done within the derby.jar codebase... from a quick glance ;-) --francois On 1/27/06, Mike Matrigali <[EMAIL PROTECTED]> wrote: > In the continuing discussion about how to fix DERBY-700, the > current most likely solution is to require one or more new > internally set system properties. > > Basically there is a need to somehow in a single JVM to share > information from 2 classloaders, such that we can answer the > question of whether database X is currently opened by a > classloader in the current JVM. The proposal is to use the > java system property mechanism as the shared information point. > > Is this ok use of system properties, with respect to the > on-going security work? > > >
