Technically, the problem isn't solved yet. Why won't this work in request scope? actionListeners don't get brand new beans in the true sense of a page being requested for the very first time. If I have an inputText with a name in it and an actionListener on a button, when I press that button, the text is still in the textfield when the page refreshes. The point is, when in request scope, the commandButton is not registering the binding on the method for the non-rendered component, even when it is set to render on refresh. That doesn't make sense?
Can one of you try it in request scope and tell me what happens? Gregg On 8/12/05, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > Yeah, obviously you knew what you were doing since you helped solve > the problem :) > Me and my big mouth :) > > -Mike > > > On 8/12/05, Martin Marinschek <[EMAIL PROTECTED]> wrote: > > I am conentrating very much on exactly this aspect ;) > > > > regards, > > > > Martin > > > > On 8/12/05, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > > > I wrote, > > > >> What happens if you dump the render statement? > > > > > > On 8/12/05, Gregg D Bolinger <[EMAIL PROTECTED]> wrote: > > > >Then the update method is called just fine. > > > > > > I'd say this it the point to concentrate on. Not sure why you and > > > Martin are looking at other things. > > > > > > > > > -- > > > > http://www.irian.at > > Your JSF powerhouse - > > JSF Trainings in English and German > > >
