There is currently quite a convoluted dance here, but essentially want gets bound into jndi is a ConnectionFactory (like a DataSource) that holds a reference to our ConnectionManagerProxy (necessary because we need to have it serializable, i.e. it can disconnect/reconnect from the jmx object).
dataSource -> ConnectionManager.allocateConnection(ManagedConnectionFactory, ConnectRequestInfo); Once we are inside that proxy we can do what we like. At the moment we just delegate to the real ConnectionMananger implementation, a BaseConnectionManager2 implementation. The first thing this does (after some sanity checks) is get the subject then invokes getManagedConnection(Subject, ConnectionRequestInfo) which just delegates to the pool after some ConnectionManager specifc processing. Finally, after it gets the managed connection it asks it for a connection handle and does the necessary book keeping to keep track of references and handle errors. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862976#3862976 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862976 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
