On 3/28/06, Michael Heinen <[EMAIL PROTECTED]> wrote: > I create the component in my bean manually and populate it with SelectItems. > Do you mean using a managed property and a more complex setter as an > alternative? Is this a better approach than the check in the getter?
It's had to say without knowing specifically what you're doing. Personally, I haven't had the need to manually create a component in the getter. >From what you've posted so far, it doesn't really sound like you need that functionality either. It sounds like all you need is a reference to your selectOneMenu component. It also sounds like you have a couple of different issues you're trying to deal with: Seralization as well as a selectOneMenu that immediately changes what's displayed on the page. I've got more experience with the second. There's no really good way to handle the second case yet. Some of the ways I've seen so far are - OptionalValidationFramework (doesn't work well if you're not using facelets so I'd only suggest it if you have either a lot of immediate controls and are using facelets) - the new sandbox subform stuff (or the ADFFaces equivalent if you're using ADF), - manually updating the backing bean from your immediate actionListener via a component reference - using the "delayed" valueChangeListener component (I think it's called ValueChangeNotifier or StateChangeNotifier?) Again, you might get better advice if you post a bigger picture of what you're trying to accomplish since some of your reported problems may be irrelevent with a different approach.
