Changes between Version 12 and Version 13 of s2s-login-functionality
- Timestamp:
- 04/01/10 16:45:01 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
s2s-login-functionality
v12 v13 86 86 * Text field for users mail 87 87 * Send button 88 The handler will check if such user exists and if so send the original password back to him/her. The email will be send by a special asteasolutions.net mail. The mail, smpt and port for this will be put in constants so that in future they could be paramethers of the server configuration.88 The handler will check if such user exists and if so send the original password back to him/her. For this I will use the java.mail api. The mail, smpt and port for this functionality will be stored in a configuration file. For this I will use the ConfigKey. 89 89 90 90 * Notification page … … 101 101 * Wrong password conformation 102 102 * [OPTONAL]Unable to upload image 103 Since those fields are slightly different from the initial ideas for user information to be stored, the UserR4 keys and the RegistrationFormBean fields should be changed accordingly. The registration handler will deal with all fields validation. If all requered information is ok the user will be created in the users folder on the server. He/she will also be loged-in by the common method used by the login handler. If the information is not ok the handler provides error messages and returns a RegistrationFormBean that contains the valid information. This way the set fields of the bean are used as default falues for the registration form.103 Since those fields are slightly different from the initial ideas for user information to be stored, the UserR4 keys and the RegistrationFormBean fields should be changed accordingly. The registration handlers will deal with all fields validation. If all requered information is ok the user will be created in the users folder on the server. He/she will also be loged-in by the common method used by the login handler. If the information is not ok the handler provides error messages and returns a RegistrationFormBean that contains the valid information. This way the set fields of the bean are used as default falues for the registration form. The email and password validation will also be extacted in a common methods. 104 104 105 105 * Edit profile page 106 * Basically same as the registration form, with few differences. First of all the mail text field is replaced with label. Second instead of "password" and "confirm password" fields we now have - "password", "new password", "confirm new password". Additional link to profile view is added.106 * Basically same as the registration form, with a few differences. First of all the mail text field is replaced with label. Second instead of "password" and "confirm password" fields we now have - "password", "new password", "confirm new password". Additional link to profile view is added. 107 107 The handler extracts all the given information and changes the stored data for the user that is curently loged in. There is additional password check. 108 108 109 109 * My profile page: Displays users info 110 110 * Same as registration page, but instead of input controls we now have labels and image 111 The handles simply colects all the information for the currently loged in user and sends as a regues parameter in the RegistrationFormBean. 111 The handles simply colects all the information for the currently loged in user and sends as a regues parameter in the RegistrationFormBean. 112 112 * New styles will appear inside main.css file and will be applied through all pages. 113 113 * All pages will be checked via http://validator.w3.org/#validate_by_input 114 115 116 All commom methods will be encapsulated in a util class - RequestHandlerUtil. 117 114 118 = Implementation = 115 119 ^(Describe and link the implementation results here (from the wiki or the repository).)^
