Subversion Repositories general

Rev

Rev 1058 | Rev 1060 | 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
1049 dev 2 
========================================================================================================================
949 dev 3 
 
1058 dev 4 
	Transaction control for listeners.
1010 dev 5 
 
6 
+/-	Save user id for all db-update operations.
7 
 
922 dev 8 
	Set 'editor' for an object by loading and not require it for each property change?
929 dev 9 
	Then problem with objects inside (lazy loaded) collections.
922 dev 10 
 
929 dev 11 
	Specification for the model.
12 
 
949 dev 13 
	Test cases for model, based on the specification. Check all bound conditions
14 
	- e.g. security exceptions. Write a complete scenario to start with default database;
15 
	login as admin, create users, domains, logout; login as normal user,
16 
	create/delete/modify mailboxes and aliases etc.
929 dev 17 
 
949 dev 18 
	Test cases for actions, not so detailed as for the model
19 
	(because it makes no sense to parse html pages).
929 dev 20 
	The scenario for the model test can be used.
21 
 
1010 dev 22 
+/-	Cascade object deletion, confirmation page.
949 dev 23 
 
24 
	Check passwords quality (make a separate project for this).
25 
 
26 
	Show filters, search.
27 
 
1029 dev 28 
+/-	Sort options for lists.
949 dev 29 
 
30 
	Allow to use existing system users: enter uid or name only, check in system for full
31 
	information.
32 
 
33 
	Allow admin to define default language for server and domain.
34 
 
35 
	Show domain for user which is in the domain.
36 
 
37 
	Check, if it's possible to create (or change) an object by admin that the object's owner
38 
	is not allowed to see it.
39 
 
40 
	Check maxlength.
41 
 
1013 dev 42 
	Make hierarchy of domains (forest).
949 dev 43 
 
44 
	Allow user to create domains (?) and subdomains in his domains.
45 
 
1015 dev 46 
	Change shell password for system user if its owner's password is changed (?).
949 dev 47 
 
48 
	Catch-all mail alias. Only one per domain.
49 
 
50 
	Basic scripts to push changes to the system.
51 
 
950 dev 52 
	If mailbox is created, create an user and a mail alias for it in one step - as option.
1015 dev 53 
	Afterwards they are binded and change own name or deleted together. Bind by name? In witch directions?
1029 dev 54 
 
1058 dev 55 
	By build cascade delete tree replace existing objects if new effect is stronger.
1059 dev 56 
 
57 
	Sort the cascade delete tree.
1058 dev 58 
 
1029 dev 59 
Done
1049 dev 60 
------------------------------------------------------------------------------------------------------------------------
1029 dev 61 
 
62 
+	Track database structure version.
63 
 
64 
+	Listeners for all operations.
65 
 
66 
+	User login history.
67 
 
68 
+	I18n. Switch language of page on the fly. Save selection in DB for each user.
69 
 
70 
+	Taglig to show ActionMessages in right way (add it to the StrutsX project).
71 
 
72 
+	Multi-page lists.
73 
 
74 
+	Store user and malbox passwords in several forms; e.g. clear text, md5, encrypt. Allow
75 
	admin to specify which forms to use.
76 
 
77 
+	Change db version to store minor version - changes which don'T affect functioonality,
78 
	e.g. indexes.
79 
 
1032 dev 80 
+	Config in one place. Allow configuration of each listener.
1041 dev 81 
 
82 
+	Split model and store.
83 
 
1045 dev 84 
+	Different user name schemes, not only user@domain. Define an interface to allow admin
85 
	implement an own one. Implement a few common ones.
1049 dev 86 
 
87 
+	Split CoreResources.properties to several files.