Path: csiph.com!news.swapon.de!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 09:37:48 -0000 (UTC) Organization: A noiseless patient Spider Lines: 15 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 09:37:48 -0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="c9f2ba19e1c5daa470c6851ce1636ea3"; logging-data="14277"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/u2KLFM9/BOJizNbsesRj7" User-Agent: slrn/1.0.2 (Linux) Cancel-Lock: sha1:clmxuxMThqNGt00lgvJ/E3BKb7Q= Xref: csiph.com comp.lang.java.programmer:37166 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 (like e.g. on second result page)... Any hint for some more more successful google-terms for the new feature? I only remember, when having to call "registerDriver" finally came out of fashion - in favour of just "forName"ing the driver class.