db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1125) Getting security exception because classes in iapi.services.info have been added to derbyclient.jar
Date Sat, 18 Mar 2006 00:07:05 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1125?page=comments#action_12370911 ] 

Andrew McIntyre commented on DERBY-1125:

I agree, option 1 is the way to go.

I remembered after you brought it up in option 3 above that currently the code is already
duplicated in the tools jar. It is assumed that the network server will be running alongside
the engine, so classlister filters out the info classes from derbynet.jar.

These classes are fairly stable. JVMInfo is the only one that has seen any change, and that
was to add a new identifier for JDK 1.6. That change was made in 10.2. The potential for problems
with shadowing, etc. are already there with the duplication in derbytools.jar, I suppose,
but I think the potential for problems is minor, and the problem in a mixed environment would
be fairly obvious to spot.

> Getting security exception because classes in iapi.services.info have been added to derbyclient.jar
> ---------------------------------------------------------------------------------------------------
>          Key: DERBY-1125
>          URL: http://issues.apache.org/jira/browse/DERBY-1125
>      Project: Derby
>         Type: Bug
>     Reporter: David Van Couvering
>     Assignee: David Van Couvering

> From Andrew's email:
> On 3/17/06, Andreas Korneliussen <Andreas.Korneliussen@sun.com> wrote:
> > </snip a whole bunch of stuff>
> >
> > Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:
> already loaded
> See DERBY-848 and DERBY-1046.
> iapi.services.info.ProductVersionHolder and friends were added to
> derbyclient.jar by David in DERBY-848, specifically with revision
> 370815.
> There are two clear solutions: unseal iapi.services.info or copy the
> info classes to a new shared info package.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message