I'm currently designing services that need knowledge of entities managed by other services eg. I have a PictureService that manages all information for a picture entity including various thumbnails and large size versions etc.
Many entities managed by other services need to maintain a foreign key to such 'picture' entities eg. StaffService includes the Employee entity which needs link to a 'picture' I know for the example quoted I could simply have pictures modelled explicitly inside the StaffService but I want to manage pictures the same everywhere to avoid constantly recoding the same stuff. I'm guessing anyone else who's used AndroMda extensiuvely would have hit this same issue. What is considered best practice in this case? Maybe to simply manage the links in a higher (hand-coded) business layer that uses both services and feeds foreign keys as needed down into each AndroMda generated service OR to have one of the AndroMda generated services directly using the other? If its the later of those two, is there a way to represent 'foreign' entities within the UML model? ie. ones which exist in another package and require reference but no generation? or is that something I'd need code into the impl classes as needed? [Question] -- Audere est Facere _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1443#1443 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
