KissMDA icon indicating copy to clipboard operation
KissMDA copied to clipboard

Cartridge kissmda-cartridges-simple-java: add Stereotype "Boundary" to create DTO (Data Transfer Object) or VO (Value Object)

Open lofidewanto opened this issue 12 years ago • 6 comments

We need to be able to create DTO with stereotype "Transport Object".

lofidewanto avatar Aug 13 '13 19:08 lofidewanto

Or we just use stereotype "Value"

lofidewanto avatar Jan 10 '14 19:01 lofidewanto

Isn't a DTO a UML boundary object? Look at this page http://www.cs.sjsu.edu/~pearce/modules/lectures/ooa/analysis/ecb.htm.

idueppe avatar Jan 10 '14 20:01 idueppe

Yes correct. DTO == TO == Value Object == Value == Boundary Object. I thought it is good to have these elements in our UML language:

Entity, Service, Value

lofidewanto avatar Jan 11 '14 14:01 lofidewanto

I don't think so that a Value object is equal to a Dto. See http://www.adam-bien.com/roller/abien/entry/value_object_vs_data_transfer.

idueppe avatar Jan 11 '14 16:01 idueppe

Ahhh.... sometimes I think that those JEE design patterns are typical of "over engineering" in our enterprise software development. Also the whole specifications with JEE. My analogy: do we need a specification for Android OS so that every vendor can implement "other" Android OS? Nope! So who needs those JEE servers from IBM, Oracle, JBoss, etc.? You only need ONE JEE server just like ONE Android OS. You can still do your own Android OS just like Linux because it's Open Source but you don't need such over specifications like JEE... I think I need to blog this ;-)

lofidewanto avatar Jan 11 '14 16:01 lofidewanto

OK, @idueppe you are right. We should make "boundary". Here is a good example: http://goo.gl/kpiOEK

lofidewanto avatar Jun 17 '14 11:06 lofidewanto