On 03.03.2006, at 10:12, Nicolas wrote:
Hi Philipp,
Current solution
----------------
- use the onPostSave (but it looks like I have to override
DialogMVNHandler which does not look that easy)
Yes thats the solution. In the dialog definition you can define
the class property which defines the actual handler.
In the repository ? I just add a node pointing to the handler class ?
In the dialog definition in the repository. You can see an example in
/modules/adminInterface/Config/dialogs/useredit
You will subclass
info.magnolia.module.admininterface.dialogs.ConfiguredDialog
Override onPostSave();
- add the Save class to the list of configurable class
Hm, .. why not. Will add it. But this is only what you should
replace if you like to replace it in general.
Well that was the easiest way I could think of.
OK. I do it.
Future solution (JSF)
---------------------
Use a custom backing bean
Also, how would you go about chaining the different actions on
save as well ?
I think we should not extend the current implementation to much.
In my opinion we should invest the effort into the new solution.
I see. Yeah, definitely.
So it looks like it's mostly done. Let me know if I can do
something on this ... on monday.
Regards,
Niko
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
Regards,
Philipp Bracher
obinary ltd.
-----------------------------------------------------
[EMAIL PROTECTED] http://obinary.com
magnolia content management http://magnolia.info
-----------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
