Daniel John Debrunner wrote: > So maybe if Derby is booted as a standalone server with no security > manager involved, it should install one with a default security > policy. Thus allowing Derby to use Java security manager to manage > system privileges but not requiring everyone to become familiar with > them.
I like this idea very much. Will there be any backward comptibility issues if we make Derby secure-by-default like this? -- Øystein
