Re: VOs

[Tellman, Ed]

I think there may be some confusion about this pattern's name.  The pattern originally called "Value Object" in the Sun J2EE Blueprints has been renamed "Transfer Object."  See: http://java.sun.com/blueprints/patterns/TransferObject.html.   I think it was renamed to avoid confusion with the other use of value object described here: http://c2.com/cgi/wiki?ValueObject.  There is some discussion about whether Value Objects should be immutable at: http://c2.com/cgi/wiki?ValueObjectsShouldBeImmutable.   --Ed Tellman -----Original Message----- From: Glenn Dickson [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 12:21 AM To: [EMAIL PROTECTED] Subject: VOs Hi All Just wondering about VO Value Objects they are to be immutable. I understand (from some people around me) that the vo cannot be changed onyl through createing a new one using constructor.   Is this true and what are the rule that govern this object. In other words what is the industry standard for these object types?   I would appreciate your comments.     TIA Glenn This message (including any attachments) may contain confidential information intended for a specific individual and purpose. If you are not the intended recipient, delete this message. If you are not the intended recipient, disclosing, copying, distributing, or taking any action based on this message is strictly prohibited.