[jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3659) Bug JBSEAM-3652 corrected in seam v2.0.3 not fully merged in v2.1.0GA

Pete Muir (JIRA) jira-events at lists.jboss.org
Tue Nov 4 07:59:30 EST 2008

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

Pete Muir reassigned JBSEAM-3659:

    Assignee: Shane Bryzak

Dennis, the beahviour you describe for 2.1 sounds correct, whilst 2.0 sounds wrong.

Shane, can you look?

> Bug JBSEAM-3652 corrected in seam v2.0.3 not fully merged in v2.1.0GA
> ---------------------------------------------------------------------
>                 Key: JBSEAM-3659
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3659
>             Project: Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.0.GA
>            Reporter: Denis Forveille
>            Assignee: Shane Bryzak
> This bug is related to bugs JBSEAM-3295 and JBSEAM-3652
> It seems that the code related to bug JBSEAM-3295 has not be fully merged from seam v2.0 to seam v2.1 
> In v2.1 the "SESSION" and "APPLICATION" scope components have their dependencies always disinjected in seam v2.1 when there is no more "active process" in any of the methods, althouth there is never any disinjection that happens in v2.0 for those scopes (See variable "canDisinject" in v2.0
> This will, at a minimum, have a performace impact on (don,t have enough knoledge of the code to evaluate the other impacts) 

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 seam-issues mailing list