c3p0 (was Re: Added some agenda items for 2015-04-17 dev call)

[Cantor, Scott]

On 4/9/15, 10:44 AM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>
>The primary questions I've got are basic : what (is the replacement),
>why, who, and when ?

WRT to c3p0, my answer is probably: nothing, unneeded, never. It doesn't appear to be dead per se, I see some sign of life there this year.

I think we should just treat the ApplicationManagedConnection element as a thing you can use but probably shouldn't, and I documented it that way last night.

If it truly dies, then I would probably suggest we just deprecate ApplicationManagedConnection outright, or at least deprecate the pooling option, and then remove that support.


The configuration options for the pooling support that are available in the schema are specific to c3p0, and so changing to another library isn't that simple and would require config changes anyway. I would rather we just leave it be and focus on documenting and supporting BeanManagedConnections as the way forward. I figured we would add some sample DataSources to some file, and add some properties that plugin the database details, and then it's basically like LDAP.

Whether we actually ship dbcp is I guess an open question, but it's not a dependency. It's in the category of the request in Jira for including SMTP appender support in logback. We don't need it, but if we think it's so commonly used that we should save people the 30 seconds of downloading it, we can I guess.

-- Scott