• 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

bean not available in scope but accessible thru property

 
Ranch Hand
Posts: 354
Eclipse IDE Oracle Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator


On an action method in UIController, I call the Persistence API and create a new ProfileBean instance and then set it in the profileBean property of UIController.
The outcome is success and the next page is displayed.

In the resultant page, if I try to get some value from the profile bean using #{ProfileBean.name} I don't get back anything. However, if I do
#{UIController.profileBean.name} it works.

I can see another instance where the same approach works... though I am willing to concede that looks could be deceiving.
If this is not the right way, how do I set my ProfileBean bean in request so that its available to the next page?


 
reply
    Bookmark Topic Watch Topic
  • New Topic