Takeshi Kondo wrote:
Hello Rick
I have this use-case experience.
I think your suggestion has two problems. Message class you suggested isn't immutable. Object is call by reference.
Indeed, that's an important concern.
And Message class must implement Serializable because Exception is serialized in RMI. However Object isn't ensure to implement Serializable.
Very good point. We have a similar problem in logback. It can be addressed by serializing all basic Java types (Integer, Long, Doublem etc) "as is" and transforming other types to String before serialization.
I think message need to be build as soon as possible to reduce several problems.
Rick's argument about needing to defer translation to a later stage is quite a valid one. Ralph Goers made a similar argument. Two requests this early in the project must correspond to a real need, don't you think? -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch