[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-2022) Ejb3DescriptorHandler incorrectly assumes a non-stateless session bean to be a stateful session bean

[jaikiran pai (JIRA)]

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

jaikiran pai resolved EJBTHREE-2022.
------------------------------------

               Fix Version/s: EJB3_1 1.0.5
                  Resolution: Done
    Component Fix Version(s): jboss-ejb3-core:1.2.3


> Ejb3DescriptorHandler incorrectly assumes a non-stateless session bean to be a stateful session bean
> ----------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-2022
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2022
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.1.22, Plugin 1.0.19, EJB3_1 1.0.4
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>             Fix For: EJB3_1 1.0.5
>
>
> Ejb3DescriptorHandler which creating containers out of metadata, incorrectly creates a StatefulContainer if the metadata is of type session and not a stateless bean:
> if (enterpriseBean.isSession())
>       {
>          if (((JBossSessionBeanMetaData) enterpriseBean).isStateless())
>             return EJB_TYPE.STATELESS;
>          else
>             return EJB_TYPE.STATEFUL;
>       }
> This no longer is a valid assumption because of the new Singleton bean in EJB3.1. As a result, this piece of code incorrectly ends up creating a stateful container for a singleton bean.

-- 
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