[ http://issues.apache.org/jira/browse/JUDDI-72?page=history ]
Steve Viens closed JUDDI-72:
----------------------------
Resolution: Invalid
By default jUDDI is configured to use the Connection Pooling available within
the Container (app server) in which it is deployed. Therefore both
commons-dbcp and commons-pooling are not required when deploying jUDDI.
jUDDI uses commons-dbcp and commons-pooling fro connection pooling when running
outside of a container. To take advantage of this feature you *must* set the
juddi.useConnectionPool property to 'true' and include the several JDBC
properties as follows:
# jUDDI-managed ConnectionPool properties (Optional)
juddi.useConnectionPool=true
juddi.jdbcDriver=com.mysql.jdbc.Driver
juddi.jdbcURL=jdbc:mysql://localhost/juddi
juddi.jdbcUser=juddi
juddi.jdbcPassword=juddi
juddi.jdbcMaxActive=10
juddi.jdbcMaxIdle=10
If juddi.useConnectionPool property does not exist within juddi.properties or
if it is set to 'false' then jUDDI assumes it is running in a container and
will attempt to use a JNDI lookup for a DataSource named
'java:comp/env/jdbc/juddiDB'
The name of this datasource may also be changed by setting the value of the
juddi.dataSource property.
> 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
