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-07 16:01 ------- I submitted a patch to resolve this complaints about the log not being serializable in ActionServlet, RequestProcessor, and MessageResources. These are all one-liners and simply involve setting the log to be transient. the one problem we continue to have is the complaint about RequestProcessor not being Serializable. i think i'd like to take back what i said when i originally posted this bug. i think that actually making RequestProcessor Serializable is not that big of a deal. there are four attributes in RequestProcessor: (1) protected HashMap actions (2) protected ApplicationConfig appConfig (3) protected Log log (4) protected ActionServlet servlet (2) and (4) are already Serializable. (3) can be resolved by making the attribute transient. (1) is a HashMap of Action instances. Actions do not implement Serializable, but there's no good reason why they couldn't.... The only state they maintain is handle to the controller servlet. So it seems this problem could be resolved by simply making RequestProcessor and Action implement Serializable & by setting the log attribute of RequestProcessor to be transient. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
