What is the default Managed Bean Scope in a JSF 2 application?
Asked Answered
S

1

17

Normally the default scope is the Request scope. I ve tried to delete the scope annotation and expected the bean to have a request bean scoped behaviour (by returning a submitted value on a previous page, I remember i've tried this the past and it worked fine) but i got nothing on the expression language wired to it. So what is the default scope and why it's not the same behaviour?!

Soldiery answered 11/10, 2013 at 15:55 Comment(0)
H
44

Depends on who's managing the bean.

If it's JSF via @ManagedBean, then it defaults to @RequestScoped, as mentioned in the javadoc:

If the scope annotations are omitted, the bean must be handled as if the RequestScoped annotation is present

If it's CDI via @Named, then it defaults to @Dependent, as mentioned in Weld documentation:

Finally, CDI features the so-called dependent pseudo-scope. This is the default scope for a bean which does not explicitly declare a scope type.

The effect is that the bean instance is newly created on every single EL expression. So, imagine a login form with two input fields referring a bean property and a command button referring a bean action, thus with in total three EL expressions, then effectively three instances will be created. One with the username set, one with the password set and one on which the action is invoked. In effects, this behaves the same as JSF @NoneScoped. This confirms the symptoms you're seeing.

If it's Spring via @Component, then it defaults to @Scope("singleton"), as mentioned in javadoc:

Default: "singleton"

In effects, this behaves the same as JSF @ApplicationScoped and CDI @ApplicationScoped.

Netbeans has got nothing to do with it. It's just an editing tool like notepad but then with 1000+ extra features.

See also:

Hypercorrection answered 11/10, 2013 at 15:57 Comment(3)
@Hypercorrection I'm confused ... you said that default scope for ManagedBean is NoneScoped, but documentation says that it's RequestScoped: "If the scope annotations are omitted, the bean must be handled as if the RequestScoped annotation is present" docs.oracle.com/javaee/6/api/javax/faces/bean/ManagedBean.htmlFatimafatimah
But, i have seen several documents which say that "@Dependent scoped beans, inherit the scope of the bean they injected to" in this link, so if the bean that is injected to has a session scope, then a separate bean won`t be generated for each EL.Luiseluiza
@NPE: It will be if you reference it directly in EL as in #{dependentScopedBean} instead of as a property of a session scoped bean as in #{sessionScopedBean.dependentScopedBean}.Hypercorrection

© 2022 - 2024 — McMap. All rights reserved.