[Proxool-developer] Proxool DataSource inital chek-ins

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

HELO Proxool.

I'm back from hibernation.

I've started to check in the DataSource stuff.

Today all you get is the extremely simple ProxoolManagedDataSource wich 
simply knows a pool alias, and delegates calls to "getConnection" to 
that pool.

This DataSource is useful for people who wants to use data sources 
outside of a J2EE environment. Proxool will create and bind this 
datasource if the "jndi-name" property is set.

I have taken a slightly different approach to the InitialContext 
configuration than what we planned before. Previously we had defined 
constants for the set of JNDI configuration properties Proxool could 
recognise. This is problematic because different JNDI providers will 
have different properties. I have chosen a more generic approach: 
Proxool will now pass all parameters prefixed with "jndi-" on to the 
InitialContext. See the DataSourceTest testcase to for how it is used. 
Is this approach ok?

I have some questions:

    * I have added a jndi package to the admin package. Is this the
      rigth place to put it?
    * The Proxool api currently prevents us from supporting the
      getConnection(user, pwd) DataSource method. How can we fix this?


Tomorrow I'll hopefully check in the other two Proxool DataSources: 
ProxoolDataSource and ReferencableProxoolDataSource.
The first is the standard Proxool DataSource that will be configured by 
a J2EE server via bean properties, the second is a subcalss of this that 
will facilitate DataSource configuration, creation  and serialization 
via standard JNDI protocols.

Theres also lots of other stuff we need to discuss. For instance: We 
should make our DataSources implement ConnectionPoolDataSource. This 
will force us to make our proxy connections implement PooledConnection. 
We must also create some adapters between the PooledConnection event 
mechanism and the Proxool event mechanism.

More about this and other stuff in the morrow.

Sorry for dissapearing.

CHR