From: <wes...@jb...> - 2006-05-05 06:24:47
|
This is pretty much complete, and actually was implmented the 'right' way (ie no hack to use MBean to get DataSource etc, etc). However, a few things remain: The XLST has been updated to include a element that gets set on the JBossManagedConnectionPool. However, as explained before, only certain SubPools can support the prefill mechanism. What will most likely happen is people will put the element in the *-ds.xml file, expect the pool to be filled and be surprised when it doesn't happen. Best solution is to probably implement the prefill method on the other pools and print a warning saying, pool does not support etc, etc. Or, we can check the Criteria in the XSLT and force the attribute to false if things don't match. Again, a bit of cleanup in order but I plan on closing this one down first thing in the morning. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3941464#3941464 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3941464 |