>so one option would be to have a namespace >property that allows you to specify whether or not modeled >entity operations should exist on the DAO or the entity itself >(but that would be pretty limiting). I agree.
>Another way would be to have a tagged value on the >operation that allowed you to specify whether or not the >operation should go on the entity or the DAO (and we could >have a property that set the default -- whether or not modeled >entity operations should by default go on the entity >or DAO). What do you think? Yep, that sound quite flexible. Exactly the way I like it. - Peter ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
