Why isn't a solution like this possible?
modelintercept: push action.getModel (other interceptors like the params) execute action push action.getModel (better;replace if that is possible) execute result
If the action has not changed the reference given from getModel this will work like before.
Popping seems dangerous because I have no idea if the model or someething else is on top of the stack... (depending of where this popping is taking place)
Thanks Jonas
Jason Carreira wrote:
Hmm... The problem with this is that the params can't be set... The params need to be set before execution, and they should be set on the Model. You could "pop" the model off the stack, but that's not keeping your actions and interceptors very disconnected... You could return a proxy/decorator object which implements the same interface as your model, then replace the model instance backing it?
-----Original Message-----
From: Jonas Eriksson [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 09, 2003 11:55 AM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] Desired behaviour in ModelDrivenInterceptor...
Currently the ModelDrivenInterceptor pushes the model onto the stack before action invocation and before many other interceptors that rely on the model beeing on the stack. That's ok!
What is not ok is the scenario when the action is changing the reference of the "model" and thus the result execution will see the old pushed model. With the new interceptor type there is a possibility to intercept before result execution (?), then why not replace the old model on the stack with a new call to getModel?
If this ain't gonna happen in the cvs, how do I replace the old model reference with a new one? (I guess pushing a new one will suffice because it would be found before the older one, but the old is still there)
Comments?
Jonas
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________
Opensymphony-webwork mailing list [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
