I just finished reading an article in the Java Developers Journal about Java Value Types (JVTs) and I am very confused what the difference is between these and Data Transfer Objects (DTOs). I understand that a value objects (VO) is very simple data holder (such as a Date or a Number) which is defined entirely by its values. That makes sense, as the article details in contrast how Java Value Types represent the state of entities in the persistence framework and are used to coarsely transfer a state between layers. But how is this different from DTOs and why would they use "Java" in the name of the pattern, limiting its use to a single programming language (without a flamewar)? Is the author just confused or giving it a special name?
Dan -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Daniel Allen, <[EMAIL PROTECTED]> http://www.mojavelinux.com/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The idea of implementing a serious complex set of business logic rules in a scripting language like Perl really scares me. Perl is too much 'write once, read never again'. And that's no good for business logic that requires maintenance. - voostind - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
