Serializable builder should be used as proxy

Effective Java, 2nd Ed. recommends (item 78) that proxy classes be used for serialization in many situations. It would make sense for a value class's builder to be a serialization proxy, since it ensures that validation, format conversion and defensive copying are reused. Why not generate readResolve and writeReplace methods that use the builder as a proxy whenever the builder is also Serializable?