> That sounds like an interesting idea...the fact that you tag > the entity as an <<Entity>> and <<ValueObject>>. If you were > gonnna appened "VO" or put it in a "vo" package however, then > I think it would probably be worth while to add a seperate > value object template/outlet in the ejb cartridge (since it > would be more specific to EJBs). But then again what about > exposing your primary key do you want to be doing that (since > its an exact replica of the entity), or maybe how about other > attributes/associations you may want to hide from the client?
Maybe we can tag the attributes that should not been exposed. Nevertheless you need to model the valueobject (without attributes) into your diagramm for using it in Service classes for example. ------------------------------------------------------- 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-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-devel
