Hi all,

I have another question about another bit of the internals of the Plc4J core 
for you : )
While implementing our Connection Pool I thought of the interface to use and 
observed that PlcDriverManager is no singleton and behaves quite a bit 
different than JDBCs.
One notable difference is that it relies on Javas ServiceLoader to load drivers 
on the classpath.

This leads me to two questions:

  1.  Why did you choose to do so and not use an approach like JDBC took with 
the singleton collection and each driver registering itself there during 
loading in a static init block?
  2.  How do the different service files interact (they have all equal name at 
equal path in the cp). Are they merged somehow during compile time with some 
kind of maven mabo-jumbo? Or how does this work that they don’t overwrite each 
other?

Thanks!
Julian

Reply via email to