On Thu, Nov 22, 2012 at 3:47 PM, Justin Deoliveira wrote:
> Makes sense. I think adding an additional store factory parameter named
> "dstype" or something and looking up the source factory implementation
> based on that would work? One of the changes I mad to the source factory
> api was basicall
Thanks Andrea.
On Wed, Nov 21, 2012 at 10:45 AM, Andrea Aime
wrote:
> On Sat, Nov 17, 2012 at 1:10 AM, Justin Deoliveira
> wrote:
>
>> OK... i went around on this one a couple of times... decided in the end
>> to just do the bare minimum to get JDBCDataStoreFactory to delegate to
>> DataSourceFa
On Sat, Nov 17, 2012 at 1:10 AM, Justin Deoliveira wrote:
> OK... i went around on this one a couple of times... decided in the end to
> just do the bare minimum to get JDBCDataStoreFactory to delegate to
> DataSourceFactorySpi. Here is a first cut.
>
>
> https://github.com/jdeolive/geotools/commi
OK... i went around on this one a couple of times... decided in the end to
just do the bare minimum to get JDBCDataStoreFactory to delegate to
DataSourceFactorySpi. Here is a first cut.
https://github.com/jdeolive/geotools/commit/ac06cb8edf8715ac33cc97d50da8f0ae81f38637
I still need to test it o
On Wed, Nov 14, 2012 at 6:02 AM, Justin Deoliveira wrote:
> Hi all,
>
> I am experimenting with a way to supply my own customized DataSource
> wrapper to a jdbc datastore. Basically my use case is playing with a
> connection proxy library like log4jdbc to log some more extended
> information about
Hi all,
I am experimenting with a way to supply my own customized DataSource
wrapper to a jdbc datastore. Basically my use case is playing with a
connection proxy library like log4jdbc to log some more extended
information about connections, monitor possible connection leaks, etc...
Now, I know t
