javax.resource.spi.ManagedConnectionFactory is serializable and hence I would expect it to be safe to keep a reference to one in a session bean since it will passivate OK. (but the ManagedConnections cannot be passivated)
Unfortunatly it has an attribute LogWriter which is of type PrintWriter which is not serializable. In my implementation of a ManagedConnectionFactory I had a non-transient attribute of type PrintWriter and this caused passiviation failures. I'm now going to make it transient but I am wondering what will happen to the logging after re-activation. The LogWriter will be null and I doubt that the contract between the application server and the resource adapter will include calling setLogWriter() at the appropriate time. Is this true or will setLogWriter() be re-called (not sure how the AppServer would know to do this). Not a serious problem, just that logging in the RA may go away after a time. ManagedConnection has the same logWriter interface but is not serializable so no problems with it. thanks, brian wallis... ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
