Why would you want to do that?
Connection pooling inside EAP / Jboss AS / WildFly is very much production capable and recommended.
What you are referring to is hibernate docs which talk about hibernate build-in connection pooling, which as noting to do with connection pooling inside application server.
That could be used when you are running hibernate in standalone application not in proper application server.
In short, don't try using C3PO if your only concern is it production readiness in App server.
just configure JPA/Hibernate to use app server provided datasource and you are done.
Thank you for your response....
Ok, but what a bout the performance and stability of the applications? Most places refer to these 2 points which are benefits of using third parties connection pools (c3p0 or ptoxool).
3rd party connection pools are usually used in servlet containers that don't have proper connection management.
good example of that is tomcat, where people need to configure c3po or similar to get proper connection management.
Every EE certified application server needs to provide proper connection pooling as it is requirement of the spec.
In short, you take app server to do stuff for you for good reason, why throw all it provides you away and use 3rd party solutions.