[MAGNOLIA-571] fix Save.getDialogHandler Created: 10/Oct/05  Updated: 23/Jan/13  Resolved: 10/Oct/05

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 3.0 Beta 1

Type: Bug Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

From svn

Modified:
magnolia/trunk/magnolia-gui/src/main/java/info/magnolia/cms/gui/control/Save.java
Log:
uncomment the getDialogHandler methods, but leave the return value as an Object. Are this used anywhere?
We need to get rid of these... Philipp, can you have a look at this?



 Comments   
Comment by Philipp Bracher [ 10/Oct/05 ]

This was not yet used. The idea of this method was the following:

The save control has no knowledge about the dialog wich it is saving. It get's all the needed information only from the saveInfo parameters. With this method a subclass would be able to get the dialog configuration and could use this information in the saving process.

We must look for a better solution: will mean that I will remove this property again.

Comment by Philipp Bracher [ 10/Oct/05 ]

removed

Generated at Mon Feb 12 03:18:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.