[webbeans-issues] [JBoss JIRA] Updated: (WBRI-264) JSF 2.0 Wrong Scope

Pete Muir (JIRA) jira-events at lists.jboss.org
Fri Jun 26 07:23:56 EDT 2009

     [ https://jira.jboss.org/jira/browse/WBRI-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir updated WBRI-264:

    Fix Version/s: 1.0.0.CR2
                       (was: 1.0.0.CR1)
         Priority: Minor  (was: Critical)

> JSF 2.0 Wrong Scope
> -------------------
>                 Key: WBRI-264
>                 URL: https://jira.jboss.org/jira/browse/WBRI-264
>             Project: Web Beans
>          Issue Type: Bug
>          Components: JSF Integration
>    Affects Versions: 1.0.0.PREVIEW1
>         Environment: Tomcat 6.0.18
> JSF 2.0 (Mojarra)
>            Reporter: Alexander Bell
>            Priority: Minor
>             Fix For: 1.0.0.CR2
>         Attachments: source.zip, source.zip
> I've created a "User" class which sould be request scoped with the properties "name" and "password".
> Also I've created a AuthenticationService which is session scoped and injects the User with @Current (so the User from the request scope must be injected).
> Finally I've got a xhtml page which you can enter the user and the password and press a button which triggers an "login" action in the AuthenticationService.
> (very similar to the jsf-web-example of chapter 2 of the introduction guide. only with jsf 2.0)
> When I am in the login action the properties "name" and "password" from the injected user are null.
> But the setters (for name and password) of the User were called before the action was invoked.
> So I suppose there are two User objects in two different scopes.
> Actually it should always be the request scope.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the weld-issues mailing list