You were right. I had the bean as request instead of session. (newbie error) That fixed it. Thanks for responding.
Ray --- Bill Dudney <[EMAIL PROTECTED]> wrote: > Hi Ray, > > A couple of thoughts: > > What is the scope of your bean (request, app etc) in > the <managed-bean> > for the object. > > When you say that the db is updated do you mean the > user hits 'go' the > db is updated then when the page is being rendered > the values are set > to null? If that is the case I don't think MyFaces > is doing anything to > make that happen. What is going on in your action > method? Is it > possible that the state of the bean is being reset > from there? Also, if > this is whats happening the location of the state > being saved won't > matter, once the be is reconstituted on the server > its not messed with > by JSF until the next request comes in. > > Thanks for using MyFaces! > > -bd- > > > On Mar 24, 2005, at 8:18 PM, Ray Clark wrote: > > > I have an app that is using tiles and MyFaces > 1.0.8. > > The page comes up and looks great. But something > is > > wrong when the page gets posted back to the > server. > > The data gets sent because it adds a row to the > > database, but when the page is redisplayed the > values > > are lost. The getters always return null (the > initial > > value of the strings). > > > > I've tried client side state saving and server > side > > state saving. I've tried using x:saveState. I've > > tried every combination that I can think of but > the > > values in the bean used to display the page are > always > > null. > > > > I'm sure that someone has an app working with > tiles. > > Any ideas on what I might have set up wrong? > > > > Thanks, > > Ray > > > > --- Ray Clark <[EMAIL PROTECTED]> wrote: > >> I'm using MyFaces 1.0.8 with server side state > >> saving. > >> The backing bean for the page has a list and a > >> couple > >> of string fiels in it. It also has some methods > for > >> adding a row to the list, deleting a row, etc. > >> > >> Ok, the page comes up just fine. But when I go > to > >> add > >> a row, or delete a row, the list is always null, > and > >> the other fields in the bean are always null. > >> > >> I'm using tiles, but that shouldn't have anything > to > >> do with it. > >> > >> I've tried changing to client side state saving > >> using > >> the x:saveState tag, but nothing seems to work. > All > >> of the fields in the bean always seem to get > reset > >> to > >> their initialized state when the page is being > >> rendered. > >> > >> I have a different app that I made without tiles > >> that > >> seems to work fine. I just have something wrong > in > >> my > >> app that uses tiles. > >> > >> Does anyone have any ideas on this? > >> > >> Thanks, > >> Ray > >> > >> > >> > >> __________________________________ > >> Do you Yahoo!? > >> Yahoo! Small Business - Try our new resources > site! > >> http://smallbusiness.yahoo.com/resources/ > >> > > > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam > protection around > > http://mail.yahoo.com > > > > __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/
