db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (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 Wed, 22 Mar 2006 00:12:07 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1125?page=comments#action_12371361 ] 

Kathey Marsden commented on DERBY-1125:

Thanks David, that is my mistake. I did not realize that this was part of the sysinfo code
imported into client in 10.1. Please go ahead and switch it back to the 10.1 setup.

The defect itself  is a regression because a classpath order that worked in 10.1 derbyclient.jar;derby.jar
does not currently work in 10.2.  I found the mail:


I'll bump it up to Critical I guess.  But a must fix for 10.2 I think. As we get closer to
the release I think it is important that product regressions be properly identified and not
slip through the cracks so that is why I brought it up.

Thanks for taking care of this issue.

> 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