• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Set method not being called in subview

 
Ranch Hand
Posts: 69
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I'm sure it is a very easy problem but can't find the solution. Any help would be appreciated.

I have a JSF file, using a subview that contains a inputText field:


inside the subview, there's an inputText field :




My managed bean is :



My faces-config.xml file is :
I do see the "test" value appearing on my web page but if I set a breakpoint on "setValue" and change it, I never step into the method (and value is never change).

The ONLY way I found was to set the managed-bean to a scope of Session but I want to keep it as a request session. What the hell I'm missing here?!?
 
Saloon Keeper
Posts: 27764
196
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Request-scope objects are (re)created and destroyed each time you send a page request, even if it's still on the same page.

If you're using JSF2, View scope will allow you to keep the same object between requests, but for JSF1, you're stuck with session scope.
 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Please check whether you have set immediate=true for the component
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic