On Wed, 13 Aug 2003 13:45, Adrian Brock wrote: > Serializable is a contract, if the ManagedConnectionFactory breaks > it, there is nothing you can do.
My concern is the setLogWriter()/getLogWriter() methods on the ManagedConnectionFactory that represent an attribute of type PrintWriter. This attribute's type is not serializable. How does the ManagedConnectionFactory maintain this attribute's state over serialization. It seems like a hole in the specification to me. > You should really be going through a resource adapator > deployment (e.g. a DataSource) and its associated connection manager. > It sounds like you want the session bean to (re)obtain > the resource in ejbActivate (e.g.using jndi or the service locator > pattern) I am re-acquiring the resource on each call; but the factory, being serializable, should be persistent over the passivation and I wouldn't have thought it would need to be re-acquired in ejbActivate(). That is a work around I suppose. 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
