[MAGNOLIA-2272] Ability to choose a custom save handler per control/field Created: 16/Jul/08 Updated: 23/Jan/13 Resolved: 17/Jul/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface, core, gui |
| Affects Version/s: | 3.6 RC1 |
| Fix Version/s: | 3.6.1 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Fabrizio Giustina | Assignee: | Fabrizio Giustina |
| Resolution: | Fixed | 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)
|
||||||||
| Description |
|
We know that the current SaveHandlerImpl is a big limit in creating customized controls and behaviours (for example it could be needed to create an image and save it into the repo from a configured text). SaveHandlerImpl could easily be expanded in order to allow the configuration of custom save handles per dialog fields (without breaking or requiring any api change). I'd like to commit this contribution (already done) for 3.6 |
| Comments |
| Comment by Fabrizio Giustina [ 17/Jul/08 ] |
|
committed to trunk (3.6.1), you can now choose a specific save handler by adding the fully qualified class name of a class implementing the CustomSaveHandler interface in the property "saveHandler" in a field |