Hi Ned,
How does your implementation relate to the Exoffice XA package? I think that
the XA layer is very well implemented. My instinctive approach would be to
add things to the Exoffice package, if we you/we need something extra at the
PooledConnection level. We may also want to separate the two layers into
distinct packages, but then we need to (hopefully only slightly) change the
XA package (which, in its current form, works very nicely for me).
Peter
> -----Original Message-----
> From: Ned Wolpert [mailto:wolpert@yahoo.com]
> Sent: Saturday, December 22, 2001 7:38 PM
> To: pgsql-jdbc@postgresql.org
> Subject: [JDBC] Submittal for JDBC Pooling driver (For 7.3)
>
>
> Folks-
>
> I wasn't going to submit this code until 7.2 was released, but I've
> wanted to have it available for folks to examine. I'm hoping
> to get it
> in the 7.3 release. Its a set of classes that provide a pooling
> data source. Its very similiar to the one I sent in a few months ago.
> Differences are
> 1) Abit more comments
> 2) Using pgsqlDriver.properties rather than psqlProps.properties
> for the property reader
> 3) Its wrapping all the returned classes so exceptions can
> be caught.
> As far as point three above goes, if my classes are accepted,
> I'd rather
> patch the jdbc2 classes to notify the driver instead of wrapping.
> The code is usable now, but your millage may varry. Please
> take a look
> and comment.
>
> Thanks.
>
> =====
> Virtually, | "Must you shout too?"
> Ned Wolpert | -Dante
> wolpert@yahoo.com |
> _________________/ "Who watches the watchmen?"
> 4e75 -Juvenal, 120 AD
>
> -- Place your commercial here -- fnord
>
> __________________________________________________
> Do You Yahoo!?
> Send your FREE holiday greetings online!
> http://greetings.yahoo.com
>
