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