Rev 929 | Show entire file | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed
Rev 929 | Rev 949 | ||
---|---|---|---|
Line -... | Line 1... | ||
- | 1 | Host Admiral TODO |
|
- | 2 | ================= |
|
- | 3 | ||
1 | + Save user id for all db-update operations. |
4 | + Save user id for all db-update operations. |
2 | 5 | ||
3 | Set 'editor' for an object by loading and not require it for each property change? |
6 | Set 'editor' for an object by loading and not require it for each property change? |
4 | Then problem with objects inside (lazy loaded) collections. |
7 | Then problem with objects inside (lazy loaded) collections. |
5 | 8 | ||
6 | Specification for the model. |
9 | Specification for the model. |
7 | 10 | ||
8 | Test cases for model, based on the specification. Check all bound conditions - e.g. security exceptions. |
11 | Test cases for model, based on the specification. Check all bound conditions |
9 | Write a complete scenario to start with default database, login as admin, create users, domaind, logout, |
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, |
|
10 | login as normal user, create/delete/modify mailboxes and aliases etc. |
14 | create/delete/modify mailboxes and aliases etc. |
11 | 15 | ||
12 | Test cases for actions, not so detailed as for the model (because it makes no sense to parse html pages). |
16 | Test cases for actions, not so detailed as for the model |
- | 17 | (because it makes no sense to parse html pages). |
|
13 | The scenario for the model test can be used. |
18 | The scenario for the model test can be used. |
14 | 19 | ||
- | 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 | ||
- | 31 | Sort options for lists. |
|
- | 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 | ||
- | 36 | Taglig to show ActionMessages in right way (add it to the StrutsX project). |
|
- | 37 | ||
- | 38 | Allow to use existing system users: enter uid or name only, check in system for full |
|
- | 39 | information. |
|
- | 40 | ||
- | 41 | I18n. Switch language of page on the fly. Save selection in DB for each user. |
|
- | 42 | Allow admin to define default language for server and domain. |
|
- | 43 | ||
- | 44 | Split CoreResources.properties to several files. |
|
- | 45 | ||
- | 46 | Show domain for user which is in the domain. |
|
- | 47 | ||
- | 48 | Check, if it's possible to create (or change) an object by admin that the object's owner |
|
- | 49 | is not allowed to see it. |
|
- | 50 | ||
- | 51 | Check maxlength. |
|
- | 52 | ||
- | 53 | Make hierarchy of domains. |
|
- | 54 | ||
- | 55 | Allow user to create domains (?) and subdomains in his domains. |
|
- | 56 | ||
- | 57 | Change shell password for system user if its onwer's password is changed (?). |
|
- | 58 | ||
- | 59 | Catch-all mail alias. Only one per domain. |
|
- | 60 | ||
- | 61 | + User login history. |
|
- | 62 | ||
- | 63 | Listeners for all operations. |
|
- | 64 | ||
- | 65 | Basic scripts to push changes to the system. |
|
- | 66 | ||
- | 67 | If mailbox is created, create an user and a mail alias for it in one step - as option. |