[ http://jira.andromda.org/browse/SPRING-112?page=comments#action_12045 ] Peter Friese commented on SPRING-112: -------------------------------------
I suggest to allow for "final" services. This will allow users to model services that will appear in the applicationContext.xml files, but for which AndroMDA will NOT genererate any Java code (e.g. because the code for the service is contained in an already existing Jar file, as is the case with the RemoteAuthenticationManager). > Add rich-client support to Acegi support > ---------------------------------------- > > Key: SPRING-112 > URL: http://jira.andromda.org/browse/SPRING-112 > Project: Spring Cartridge > Type: New Feature > Versions: 3.1RC1 > Reporter: Peter Friese > Assignee: Peter Friese > Fix For: 3.1RC1 > > For rich clients, it is essential to be able to contact the server in order > to perform some kind of authentication before the user is allowed to use tha > application. > Acegi comes with a remote authentication manager > (net.sf.acegisecurity.providers.rcp.RemoteAuthenticationManager) that helps > with this. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
