<snip> On Wed, 26 Jan 2005 16:12:17 -0500, Rick Reumann <[EMAIL PROTECTED]> wrote: > If someone has a better way to handle this, please let me know. </snip>
I don't know if this is "better" or not, but I really prefer having some sort of "module" or "area" or whatever you want to call it that handles state for the view separate from page, request, session and application scopes. I prefer having the state be a map backed or list handler backed class that is easily used to display state to the view. Also, I like to have this state object wrapped such that there is an interface not unlike getState(...) for either the Action or the model. Whatever is in between the interface and the map is purely implementation and subject to whatever choices, improvements, etc. one might make. For me, and of course I speak for myself alone, I could not stand the view being so tightly bound as your suggestion. Maybe I misunderstand what you are doing. The reason I like the approach I favor is that you can write the Struts code in the Action, etc., and the code on the JSP pages without knowing a thing about what is happening behind the scenes. You really don't even need collaboration. You can even write simply tools to build test classes by code generation for whatever is on the JSP pages without much difficulty. Anyway, that is my $.02 worth on this. I think we have different approaches on this and have the greatest respect for yours as well. Jack -- ------------------------------ "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ "You can't wake a person who is pretending to be asleep." ~Native Proverb~ "Each man is good in His sight. It is not necessary for eagles to be crows." ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ ----------------------------------------------- "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
