Quote:
Do you have a good design pattern, or a way to model the access control to individual methods of services ? (end of quote) The design pattern is to use a service layer that runs in a controlled environment, i.e. on the server ;-) As to defining access control for indivdual service methods, that's what declarative security in EJB (if you use session beans) is for: Just add the appropriate constraints to the EJB descriptor. I think there's some package that supports declarative security in Spring as well. But as far as I know, there is no support for modeling per-method security constraints in AndroMDA yet (I may be wrong though - at the moment, I'm working on a project where I can't use AndroMDA, so I'm not quite up to date on the subject) _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1743#1743 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
