You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "David W. Van Couvering" <Da...@Sun.COM> on 2005/12/05 01:37:29 UTC
Right location for new classes
Hi, all. In my work on writing a classloader that removes issues raised
by mixed versions of Derby in the classpath, I am looking at setting up
a pattern of a stub class delegating to an implementation class, e.g.
EmbeddedDriver (rewritten to be a stub)
|
delegates to
|
V
EmbeddedDriverImpl
Then EmbeddedDriver, when loaded and/or instantiated, uses the
specialized classloader to load EmbeddedDriverImpl.
Because org.apache.derby.impl is not sealed, I can put
EmbeddedDriverImpl in the same package as EmbeddedDriver.
But an alternate approach would be to move it into a different package.
Does anyone recommend this approach, and what are your reasons? And
if so, what package would you recommend relocating it to (I was thinking
org.apache.impl.jdbc).
Unless I hear otherwise, however, I'll keep the Impl class under
org.apache.derby.jdbc.
Thanks,
David