[MGNLPUR-23] make the config more flexible so it can have a list of Strategies instead of a fixed number Created: 08/Oct/09 Updated: 04/Oct/13 Resolved: 04/Oct/13 |
|
| Status: | Closed |
| Project: | Magnolia Public User Registration |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Bert Leunis | Assignee: | Roman Kovařík |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
When you need an extra strategy, you have to adapt the PublicUserRegistrationConfig class. Instead of having a fixed set of 3 strategies, a list of strategies could be present in the config. Probably a module class has to be created that loads the strategies in a Map<String, Strategy>. From the module instance the strategy can then be retrieved by name. |
| Comments |
| Comment by Roman Kovařík [ 04/Oct/13 ] |
|
Solved in |