Subversion Repositories general

Rev

Rev 950 | Go to most recent revision | Details | Compare with Previous | Last modification | View Log | RSS feed

Rev Author Line No. Line
949 dev 1
Host Admiral TODO
2
=================
3
 
929 dev 4
+	Save user id for all db-update operations.
916 dev 5
 
922 dev 6
	Set 'editor' for an object by loading and not require it for each property change?
929 dev 7
	Then problem with objects inside (lazy loaded) collections.
922 dev 8
 
929 dev 9
	Specification for the model.
10
 
949 dev 11
	Test cases for model, based on the specification. Check all bound conditions
12
	- e.g. security exceptions. Write a complete scenario to start with default database;
13
	login as admin, create users, domains, logout; login as normal user,
14
	create/delete/modify mailboxes and aliases etc.
929 dev 15
 
949 dev 16
	Test cases for actions, not so detailed as for the model
17
	(because it makes no sense to parse html pages).
929 dev 18
	The scenario for the model test can be used.
19
 
949 dev 20
	Cascade object deletion, confirmation page.
21
 
22
	Store user and malbox passwords in several forms; e.g. clear text, md5, encrypt. Allow
23
	admin to specify which forms to use.
24
 
25
	Check passwords quality (make a separate project for this).
26
 
27
	Show filters, search.
28
 
29
	Multi-page lists.
30
 
950 dev 31
	Sort options for lists.
949 dev 32
 
33
	Different user name schemes, not only user@domain. Define an interface to allow admin
34
	implement an own one. Implement a few common ones.
35
 
958 dev 36
+	Taglig to show ActionMessages in right way (add it to the StrutsX project).
949 dev 37
 
38
	Allow to use existing system users: enter uid or name only, check in system for full
39
	information.
40
 
950 dev 41
+	I18n. Switch language of page on the fly. Save selection in DB for each user.
42
 
949 dev 43
	Allow admin to define default language for server and domain.
44
 
45
	Split CoreResources.properties to several files.
46
 
47
	Show domain for user which is in the domain.
48
 
49
	Check, if it's possible to create (or change) an object by admin that the object's owner
50
	is not allowed to see it.
51
 
52
	Check maxlength.
53
 
54
	Make hierarchy of domains.
55
 
56
	Allow user to create domains (?) and subdomains in his domains.
57
 
58
	Change shell password for system user if its onwer's password is changed (?).
59
 
60
	Catch-all mail alias. Only one per domain.
61
 
62
+	User login history.
63
 
64
	Listeners for all operations.
65
 
66
	Basic scripts to push changes to the system.
67
 
950 dev 68
	If mailbox is created, create an user and a mail alias for it in one step - as option.