Dick Zetterberg wrote:
By using this one could avoid doing form names such as
"myBean/oneProperty" and simply use "oneProperty" instead, if the
getModel() method returns the model to be used both as "input" and as
"result".
But if your bean contains other beans then you still have to use names like
"otherBean/newProperty", and if you today use several beans in your action
you would have to create a wrapper class for them to use as the model
(instead of just adding a get method for each bean in the action).
In that case you could continue to use the action as the "wrapper".
So I do not see a very big practical advantage with the proposed addition.
For the cases you mention, sure. But there's quite a number of cases
where only one bean is being used as input/output and for that case it
becomes much cleaner.
However, I am not "against" it if you find it useful, as long as the old way
of doing it still works.
As I noted the default would be that it works exactly like today.
/Rickard
--
Rickard Öberg
[EMAIL PROTECTED]
Senselogic
Got blog? I do. http://dreambean.com
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
