DO NOT REPLY [Bug 9828] - ValidatorForm can not be serialized

[bu...@apache.org]

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=9828>.
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=9828

ValidatorForm can not be serialized





------- Additional Comments From Joe@Germuska.com  2002-06-28 00:54 -------
Note also that LogSource is a deprecated class in the commons logging api.

Anyway, I'll make a patch that makes it static and updates the implementation
class -- in this case, the need to sometimes put ValidatorForms in sessions and
sessions sometimes requiring serializable objects seems to justify the change.  

A quick grep through the source tree shows that Log objects are usually not
implemented as static members; is there a reason for this?  I usually make Log
classes static and final, but maybe I'm a fool.  I'm certainly not a committer,
so someone else can intervene if this is a bad idea.

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