Most default values are sensible and in most cases can be accepted. The only one we
should change if necessary is the Scope field.
Managed beans can have different scopes. A scope of request means that the bean
is only available in a single HTTP request. Managed beans can also have session
scope, in which case they are available in a single user's HTTP session. A scope of
application means that the bean is accessible to all users in the application, across
user sessions. Managed beans can also have a scope of none, which means that
the managed bean is not stored at any scope, but is created on demand as needed.
Additionally, managed beans can have a scope of view, in which case the bean is
available until the user navigates to another page. View scoped managed beans are
available across Ajax requests.
We should select the appropriate scope for our managed bean, in our particular
example, the default request scope will meet our needs.
After finishing the wizard, a boilerplate version of our managed bean is created in
the specified package.