[ http://issues.apache.org/jira/browse/JUDDI-72?page=comments#action_63468 ] Anil Saldhana commented on JUDDI-72: ------------------------------------
I have checked in a class called J2EEJDBCDataStore that is an exact replica of the JDBCDataStore but it just gets the DataSource from JNDI and the DataSource provides the connection pooling. Users running in a J2EE environment can either use JDBCDataStore or J2EEDataStore. Both have the same behavior. Except JDBCDataStore has a reliance on commons-pooling and commons-dbcp (they dont kick in a J2EE env). > Refactor connection pooling > --------------------------- > > Key: JUDDI-72 > URL: http://issues.apache.org/jira/browse/JUDDI-72 > Project: jUDDI > Type: Sub-task > Components: Feature Requests Section > Reporter: Anil Saldhana > Assignee: Steve Viens > Priority: Minor > > To carry on the discussion about improving jUDDI to help integration with > managed environment, I want to add the following comment. > In a managed environment like a J2EE application server, the JCA component > provides connection pooling capability. > Can the connection pooling (commons dbcp/pooling) be factored out of jUDDI > data store implementation so that the datasource that the app server provides > takes care of the pooling? > Basically, I am wondering if the dependencies on commons-dbcp and > commons-pooling can be removable by an integrator if needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
