Quote: But as far as I know, there is no support for modeling per-method security constraints in AndroMDA yet (I may be wrong though (end of quote)
Actually we do have this (with or without EJB + spring), read on. Quote: Do you have a good design pattern, or a way to model the access control to individual methods of services ? (end of quote) Did you try modeling your security and using the acegi declaritive role based support? (there is declaritive role based security for ejb as well but I know you're not using EJB) Unfortunately this hasn't been added to the how-to yet, but all you need to do is have actors for your roles and have dependencies going to the service operations you want the actor to be able to access. If a dependency goes to the service itself, the actor has accesss to all operations. -- Chad Brandon - [EMAIL PROTECTED] http://www.andromda.org _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1745#1745 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
