This week's book giveaways are in the Scala and Android forums.
We're giving away four copies each of Machine Learning Systems: Designs that scale and Xamarin in Action: Creating native cross-platform mobile apps and have the authors on-line!
See this thread and this one for details.
Win a copy of Machine Learning Systems: Designs that scale this week in the Scala forum
or Xamarin in Action: Creating native cross-platform mobile apps in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

@ViewScoped not working  RSS feed

 
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am using JSF2 on Tomcat 6 with Spring 3.

My manged bean is:


I have an editQuestion.xhtml page. As i click any action button on page e.g. Cancel, Save Question etc the manged bean is created again. In JSF 1 we achieved it usign keepAlive but @viewScoped is supposed to replace it in JSF 2.

I have to use @Component because i need to inject some spring beans in managed bean and spring does not recognize @ManagedBean.

 
anyz mick
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Could it be issue with Spring. Because Spring scope is "request" it makes it created every time. I tried removing the spring scope then ViewScoped bean is never created again even i navigate to differnt pages.
 
Bartender
Posts: 19459
88
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It's a fundamental JSF principal that you cannot inject a short-scoped object into a longer-scoped one. In particular, you cannot inject Request-scope objects into Session-scoped ones. ViewScope is a variant of Session Scope with a longer lifespan than Request Scope and a shorter lifespan than full Session Scope. ViewScope objects can therefore only be injected with View, Session, and/or Application scope objects. If you inject a Request Scope object into it (assuming JSF doesn't complain), the injected Request scope object will be invalid the first time the backing bean is updated on postback.

Normally, my Spring Beans are effectively at Application Scope, not Request scope. I say "effectively", since if the JSF bean gets serialized, all bets are off, but that's something I hope JSF will fix some day and it doesn't matter here.

For Request-scope objects, I use JSF, not Spring. I may inject Spring objects into the Request-scope objects, but the objects themselves are JSF_managed, not Spring-managed.
 
anyz mick
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Tim for detailed explaination.

I created the custom Spring scope as guided at this webpage.

So @ViewScoped bean now contains objects of same scope.
 
We find this kind of rampant individuality very disturbing. But not this tiny ad:
Rocket Oven Kickstarter - from the trailboss
https://coderanch.com/t/695773/Rocket-Oven-Kickstarter-trailboss
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!