db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <knut.hat...@oracle.com>
Subject Re: [jira] [Updated] (DERBY-5253) Engine code references org.apache.derby.shared.common.sanity.SanityManager
Date Tue, 31 May 2011 08:23:08 GMT
dag.wanvik@oracle.com (Dag H. Wanvik) writes:

> "Kristian Waagan (JIRA)" <jira@apache.org> writes:
>
>> Attached patch 1a, which replaces the imports from common with imports from iapi.
>
> So, if the "shared" and "common" stuff can't be used by the embedded
> driver/engine code, how is it shared? Shared between client driver and
> tools?

The "shared" and "common" stuff is actually used by the engine code,
since the iapi SanityManager class is a sub-class of
shared.common.sanity.SanityManager. The sanity classes were given a
special exception from the rule because they're not in the production
jars. See this thread:
http://mail-archives.apache.org/mod_mbox/db-derby-dev/200603.mbox/%3C44160E0C.3010500@sun.com%3E

I think the reason for the names "common" and "shared" was that the code
was intended to be shared between the drivers, but the details on how
this could be done without causing shadowing problems had not been
worked out yet. There are some proposals on how to solve it on
DERBY-289. Also lots of long threads on derby-dev (search the archive
for "shared" between Sep 2005 and Nov 2005 in case you're interested),
but it never got completed.

-- 
Knut Anders

Mime
View raw message