> A better way of expressing this would be something like: > > <command name="myCommand1"> > <controller-pipeline> > <controller class="com.foo.Bootstrap"/> > <controller class="com.foo.Authenticate"/> > <controller class="com.foo.ModuleSpecific1"/> > <controller class="com.foo.Command1"/> > </controller-pipeline> > <view name="success" path="myPage.jsp"/> > <view name="error" path="errorPage.jsp"/> > </command>
Where do you plan to define a view(s) for authentication, user registration, etc. ? Simple or not simple..., I would like to see following capabilities: A first time user comes with a request to secure command with some get or post parameters like this: http://localhost/app/secureCommand.m?someParam=someValue User is given a possibility to log in or register and once this is done, he or she is redirected to an original page with original get or post parameters. There are views like "success" and "error" for myCommand1. Would you end up having views like: "authentication-error", "registration-success", "module1-specific-error", etc. for every command? It just gets too verbose. with best wishes, Taavi ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp [INVALID FOOTER]
