Oh. Duh. Yes, of course. An XA resource adapter won't use XAManagedConnectionFactory or XAManagedConnection. They'll have their own implementations. So doing it on the ConnectionListener makes total sense.
Thanks. "[EMAIL PROTECTED]" wrote : On the main point, we don't control/write the ManagedConnectionFactory or ManagedConnection. These are application classes. | | But we do control where these are created and we can wrap them with our | own processing, e.g. ConnectionListener wraps ManagedConnection. | | What we actually want to wrap is the XAResource associated with the ManagedConnection | to perform any necessary padding or flag manipulation. | | In particular we want to modify the start()/end() used by our ConnectionListener | and recover() used by the yet to written Recoverable implementation. | | This processing then becomes transparent to the transaction manager | and is configured/controlled at each resource. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869077#3869077 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869077 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
