| From: |
"JIRA (on behalf of Fabrizio Giustina)" <dev-list@magnolia.info> |
| Subject: |
[JIRA] Resolved: (MAGNOLIA-2272) Ability to choose a custom save handler per control/field |
| Date: |
Thu, 17 Jul 2008 21:09:13 +0200 (CEST) |
| To: |
dev-list@magnolia.info |
|
 |
|
[ http://jira.magnolia.info/browse/MAGNOLIA-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabrizio Giustina resolved MAGNOLIA-2272.
-----------------------------------------
Resolution: Fixed
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
> Ability to choose a custom save handler per control/field
> ---------------------------------------------------------
>
> Key: MAGNOLIA-2272
> URL: http://jira.magnolia.info/browse/MAGNOLIA-2272
> Project: Magnolia
> Issue Type: Improvement
> Affects Versions: 3.6 RC1
> Reporter: Fabrizio Giustina
> Assignee: Fabrizio Giustina
> Fix For: 3.6.1
>
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|