You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Anil Saldhana (JIRA)" <ju...@ws.apache.org> on 2005/04/13 21:03:16 UTC
[jira] Commented: (JUDDI-72) Refactor connection pooling

     [ http://issues.apache.org/jira/browse/JUDDI-72?page=comments#action_62759 ]
     
Anil Saldhana commented on JUDDI-72:
------------------------------------

---------------------------------------------
() for servlet jUDDIPublishServlet threw exception
java.lang.NoClassDefFoundError: org/apache/commons/pool/ObjectPool
        at org.apache.juddi.datastore.jdbc.JDBCDataStore.<init>(JDBCDataStore.java:84)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
        at java.lang.Class.newInstance0(Class.java:308)
        at java.lang.Class.newInstance(Class.java:261)
        at org.apache.juddi.datastore.DataStoreFactory.getDataStore(DataStoreFactory.java:67)
        at org.apache.juddi.function.GetAuthTokenFunction.execute(GetAuthTokenFunction.java:62)
---------------------------------------------

Now if I remove the commons-dbcp and commons-pooling jars from the juddi deployment, I get NoClassDefs as shown above.  I am wondering if this dependency can be removed in someway, because by default, the connection pooling is not kicking in.



> 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