hi guys, if changes are being made, can i also suggest that <ValueOject> be changed to <Value> for consistency?
("Object" is redundant and, being pedantic, <ValueObject> is a class anyway, not
an object :-))
regards, greg johnson
----- Message from [EMAIL PROTECTED] --------- Date: Sat, 19 Jun 2004 21:32:45 -0400 From: Chad Brandon <[EMAIL PROTECTED]>Reply-To: Chad Brandon <[EMAIL PROTECTED]> Subject: Re: [Andromda-user] 3.0m2 hibernate cartridge fails if <<entity>> does not declare a <<primary key>> To: [EMAIL PROTECTED], Greg Johnson <[EMAIL PROTECTED]>, 'Users AndroMDA' <[EMAIL PROTECTED]>
----- Original Message ----- From: "Wouter Zoons" <[EMAIL PROTECTED]> To: "Greg Johnson" <[EMAIL PROTECTED]>; "'Users AndroMDA'" <[EMAIL PROTECTED]> Sent: Friday, June 18, 2004 5:51 PM Subject: Re: [Andromda-user] 3.0m2 hibernate cartridge fails if <<entity>> does not declare a <<primary key>>
hi Greg,
my comments are inserted below
Greg Johnson wrote:
> hi wouter, > thanks for your reply - understand. > > i was using the hibernate documentation that says: > > "The identifier property is optional. You can leave it off and let > Hibernate > keep track of object identifiers internally. However, for many > applications it > is still a good (and very popular) design decision." > ah good to know, I'll have to investigate this a little more.
> which would seem to be ok for a composite association. but then, as > you point > out, hibernate requires either an id or compoiste id for any mapped > class. > > i guess if you wanted to be pedantic, you should not need to declare a > <primary > key> in the pim, and have the hibernate cartridge allocate the id. >
good that you bring up this issue because I too find it strange to have to declare the PrimKey in the PIM, as it is not part of any business object's properties
> while on the subject of hibernate, the sterotype name <entity> is a bit > misleading. > > strictly, <entity> should be reserved for first class objects only > (compare with > <value object>) and not have an overloaded implication of persistence. > > as the hibernate docs say: > "An entity exists independently of any other objects holding > references to the > entity." and "Unlike entities, values (in particular collections and > components) are persisted and deleted by reachability" > > ie there should be a separate stereotype <persistent> which can be > applied to > either <entity> or <value object> classes. >
very good, I like this ... good timing too, because if we decide to have new stereotype names we will need to fix them asap (before milestone 2) I would like to have Matthias' response to this one though, as I am not alone to decide
I vote for! anyone else ?
+1 for me as well!
> thanks again, > cheers -- Wouter
------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
----- End message from [EMAIL PROTECTED] -----
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Andromda-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-user
