commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 37727] - [resources] Fix serializability contracts
Date Thu, 01 Dec 2005 06:32:04 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37727>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37727





------- Additional Comments From rahul@apache.org  2005-12-01 07:32 -------
So the reasoning is (I hope you're right, it'll be good to be wrong here) -

 * BasicMessage has this field - Object[] values
 * The purpose of these "values" is to serve as replacement values in a 
MessageFormat
 * There is no restriction on replacement values for a MessageFormat to be 
serializable, MessageFormat will just use the toString() operator while 
substituting as a String replacement value
 * Therefore, one may not guarantee serializability of BasicMessage

The rest is just a cascading effect since BasicMessage's go everywhere. Am I 
being too convoluted about some corner cases? ;-) The more I think about the 
above, there is little that can be done either way.

And I agree with you when you say that there is little that we can do with the 
other classes we *surely* know are not serializable. Maybe its best to leave 
a "known issue" in the release notes about these and move on?


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message