Re: DO NOT REPLY [Bug 8487] - Serializability issues in ActionServlet/RequestProcessor

[Andre Beskrowni <be...@hotmail.com>]

Is it possible that a committer could take a look at this bug?  it's been 
languishing since late april and it's a pretty serious problem for anyone 
using weblogic (possibly others too).  we'd like to be able to keep in synch 
with the nightly builds, but having to repeatedly add the changes in the 
patch submitted with bug is a little tedious.

ab



>From: bugzilla@apache.org
>To: beskrowni@alumni.cmu.edu
>Subject: DO NOT REPLY [Bug 8487]  -    Serializability issues in 
>ActionServlet/RequestProcessor
>Date: 7 Jun 2002 16:01:12 -0000
>
>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 beskrowni@alumni.cmu.edu  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.


_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>