Re: [Proxool-developer] Driver specific interfaces

[<chr...@em...>]

Phrooh!

Why do you consider tying your code  to a self-produced interface tied 
to the currently exposed methods of a vendor spesific class to be more 
robust and maintainable than tying your code to a ProxoolFacade method?

Using Proxool facade saves you both the writing/maintaining of the 
interface and the extra configration.


CHR

Bill Horsman wrote:

>Bertrand,
>
>On Wed, 2004-03-24 at 21:12, Bertrand Renuart wrote:
>
>  
>
>>You point to another (easier) solution: the ability for people to *inject*
>>interfaces in our proxy class.
>>
>>They could define an interface containing the signature of the methods they
>>want from the vendor jdbc connection (rs and st as well); then register this
>>extra interface with proxool.
>>    
>>
>
>1.
>  <proxool>
>    <alias>my-oracle-pool</alias>
>    <driver-url>jdbc:oracle...</driver-url>
>    <driver-class>oracle.jdbc.OracleDriver</driver-class>
>    <connection-interface>
>      com.outside.jdbc.StrangeConnectionIF
>    </connection-interface>
>  </proxool>
>
>2.
>  public interface StrangeConnectionIF {
>    public void foo();
>  }
>
>3.
>  Connection c = DriverManager.getConnection(url, properties);
>  StrangeConnectionIF sc = (StrangeConnectionIF) c;
>  sc.foo();
>
>Like that?
>
>- Bill
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IBM Linux Tutorials
>Free Linux tutorial presented by Daniel Robbins, President and CEO of
>GenToo technologies. Learn everything from fundamentals to system
>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>_______________________________________________
>Proxool-developer mailing list
>Pro...@li...
>https://lists.sourceforge.net/lists/listinfo/proxool-developer
>
>  
>