> We just need a way to configure Java security though the database,
> instead of editing JVM configuration files.

Agree.

>> I'd say we don't need to worry about this topic a lot, I can't think
>> about a scenario that Java plugin can't handle provided it has some
>> configuration (I'd prefer to have a system table for it with write
>> access to database owner, but a file on a disk is also ok).
>
> System table = plugin table, right?

Yes.

> I would like to have plugin functions to manipulate these tables.

What kind of? I am thinking about plugin exporting management
functions/procedures, which are, let's say, accesible to database owner
or SYSDBA.

> Note that all this could be done in a second version of the plugin, if
> by default we ship the first plugin version configured to a restricted
> environment, similar to applets.

Yes, this is what I'm thinking as well.

Roman