Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Andreas Leitgeb Newsgroups: comp.lang.java.programmer Subject: Re: Is this a correct implementation of an abstract class and implementation class Date: Sun, 13 Aug 2017 10:13:00 -0000 (UTC) Organization: A noiseless patient Spider Lines: 17 Message-ID: References: <87r2wgxz2p.fsf@munus.decebal.nl> Reply-To: avl@logic.at Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sun, 13 Aug 2017 10:13:00 -0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="c9f2ba19e1c5daa470c6851ce1636ea3"; logging-data="14277"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18DKlXPpKuSq5qC4BvxhgYs" User-Agent: slrn/1.0.2 (Linux) Cancel-Lock: sha1:Dc9oL63x0gqUILd+HwfD+qivtqQ= Xref: csiph.com comp.lang.java.programmer:37171 Andreas Leitgeb wrote: > Arne Vajhøj wrote: >> I assume you are aware that with newer Java versions then >> Class.forName is not required. > I googled for "jdbc" and "forName", hoping that I'd find some with > a negative context for "forName", but these still seem to be too > well hidden... Well, found it, afterall, but I'm not overly impressed. iiuc, then instead of providing the driver class name and the dbURI for an app, I'd instead provide the dbURI to the app, and need to provide the used drivername(s) already to the JVM. Not saying that there couldn't be cases where this would be advantageous, I just can't think of one right now.