DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8487>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8487 Serializability issues in ActionServlet/RequestProcessor ------- Additional Comments From [EMAIL PROTECTED] 2002-06-24 15:44 ------- Unfortunately, it's not always going to be possible to create a Serializable Log implementation -- for the same reason as you described for ActionServlet one level down. Consider a Log implementation that writes to syslog on a Unix platform. Deep down inside, you're going to have a java.net.Socket connection to the syslog daemon -- and you cannot serialize a Socket. So, you either need to require all Log implementations to implement enough information to reconstitute themselves when the serialized data is reloaded, or not allow them to be used. It does not seem to me that it will be possible to mandate this in the general case. (For example, consider someone using JDBC connections or connection pools accessed via a servlet context attribute ...). It seems unfortunate to me that this non-standard implementation requirement from BEA is going to force developers to use static variables (with all the issues that causes in multi-class-loader situations) instead of servlet context attributes for application-scope things that cannot be serialized. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
