Hi TLN, In 5.0 SaveHandler was deprecated along with the old UI. The new UI uses Vaddin and Vaadin data binding. The dialogs operates on Vaadin interfaces, primarily com.vaadin.data.Item and com.vaadin.data.Property. Magnolia have implementations of these interfaces that operates on JCR nodes and properties. In this model these objects collectively fills the purpose that SaveHandler did in 4.5.
To tune the behavior of a field you can configure a transformer that saves the field's value in a new way. To augment the data saved by a dialog you can use a custom action that gets run when the dialog is saved. Can you provide more details on what you want to achieve? What does the SaveHandler you're trying to replace do? -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=0612f2d8-6e20-4436-a3c9-8e25a64ffb97 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
