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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From [EMAIL PROTECTED] 2002-07-23 17:25 ------- >From Craig's comment, I presumed that RequestProcessor was modified to be Serializable. It appears that it wasn't. After spending some time updating to the latest nightly build, it seems that RequestProcessor is still an issue for us. It is a member of ActionsServlet which extends HttpServlet which is Serializable, so the problem persists. Admittedly, we are running expanded, but changing that would seem to be a side issue. If there were a Junit test for each class that were Serializable, that would shed light immediately on object relationships that break the Serializable contract, outside of the context of what app server is being used or how. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
