> Why are you hung up on using only one backing bean? Use as many as you need -- and needing different lifetimes for data is *definitely* a good reason to use more than one bean as necessary.
I agree this is the direction I need to head. I was just concerned about the number of objects and how to organize (say name) them. I have used IBM's Websphere IDE and they create a backing bean per page which seems like the appropriate amount to create. >... It is not JSF's responsibility to ensure that you make sure getStates() is as efficient as possible. Given your example I would fully expect the getter to be called twice if there are two components on the screen accessing the same backing bean property. But that isn't the scenario I have. I instead have a single field (i.e. title - Mr., Ms., Mrs. etc) that is only specified once on the page, but the getter will still be called more than once in some instances. > If you like init() and destroy() on backing beans, you'll definitely like Shale :-) Looks like I need to break down and do a little reading :-) Thanks for your response, Aaron Bartell
