SCJP 1.4, SCWCD 1.4, SCBCD 5, SCEA
SCJA 1.0, SCJP 1.4, SCWCD 1.4, SCBCD 1.3, SCJP 5.0, SCEA 5, SCBCD 5; OCUP - Fundamental, Intermediate and Advanced; IBM Certified Solution Designer - OOAD, vUML 2; SpringSource Certified Spring Professional
Kengkaj Sathianpantarit wrote:Value Object is not the same as Transfer Object (TO or DTO pattern).
Value Object means objects that don't have identity. For example, services are Value Objects.
Value Object is an important building block for software design.
However, when I talk about Value Objects, I refer to Domain-Driven Design.
SCJP 1.4, SCWCD 1.4, SCBCD 5, SCEA
Sun Certified Developer for the Java 2 Platform
Sun Certified Enterprise Architect for the Java Platform, Enterprise Edition 5
Ronald Wouters wrote:I guess they should make an update to Figure 8.5 in the following text then, because it still mentions "ValueObject".
http://java.sun.com/blueprints/corej2eepatterns/Patterns/TransferObject.html
SCJP 1.4, SCWCD 1.4, SCBCD 5, SCEA
SCJP, SCWCD, SCBCD, SCEA 5
Piotr Uryga wrote:
Kengkaj Sathianpantarit wrote:Value Object is not the same as Transfer Object (TO or DTO pattern).
Value Object means objects that don't have identity. For example, services are Value Objects.
Value Object is an important building block for software design.
However, when I talk about Value Objects, I refer to Domain-Driven Design.
Are You serious man ?
They changed the name of pattern from Value Object (Ed1 of Core J2EE Pattern) to Transfer Object (Ed2).
You can find bunch of topics here on Javaranch about the whole case, f.e.:
https://coderanch.com/t/154686/Architect-Certification-SCEA/Value-Object-VO-vs-Transfer
http://en.wikipedia.org/wiki/Data_Transfer_Object
Question was regarding Java EE 5, so was my answer.
SCJA 1.0, SCJP 1.4, SCWCD 1.4, SCBCD 1.3, SCJP 5.0, SCEA 5, SCBCD 5; OCUP - Fundamental, Intermediate and Advanced; IBM Certified Solution Designer - OOAD, vUML 2; SpringSource Certified Spring Professional
Kengkaj Sathianpantarit wrote:
Piotr Uryga wrote:
Kengkaj Sathianpantarit wrote:Value Object is not the same as Transfer Object (TO or DTO pattern).
Value Object means objects that don't have identity. For example, services are Value Objects.
Value Object is an important building block for software design.
However, when I talk about Value Objects, I refer to Domain-Driven Design.
Are You serious man ?
They changed the name of pattern from Value Object (Ed1 of Core J2EE Pattern) to Transfer Object (Ed2).
You can find bunch of topics here on Javaranch about the whole case, f.e.:
https://coderanch.com/t/154686/Architect-Certification-SCEA/Value-Object-VO-vs-Transfer
http://en.wikipedia.org/wiki/Data_Transfer_Object
Question was regarding Java EE 5, so was my answer.
I think you misunderstood Piotr . I didn't reply to you. I did reply to the topic creator.
I guess Sun have changed name "Value Object" to "Transfer Object", because it's not the appropriate name.
jeff mutonho wrote:
The confusion started when Sun started using TO for VO , but some people still referred to TOs as VOs.Perhaps I should have been more correct and used
TO in my question
SCJA 1.0, SCJP 1.4, SCWCD 1.4, SCBCD 1.3, SCJP 5.0, SCEA 5, SCBCD 5; OCUP - Fundamental, Intermediate and Advanced; IBM Certified Solution Designer - OOAD, vUML 2; SpringSource Certified Spring Professional
Consider Paul's rocket mass heater. |