Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-2022

Ejb3DescriptorHandler incorrectly assumes a non-stateless session bean to be a stateful session bean

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.1.22, Plugin 1.0.19, EJB3_1 1.0.4
    • Fix Version/s: EJB3_1 1.0.5
    • Component/s: core
    • Labels:
      None
    • Component Fix Version(s):
      jboss-ejb3-core:1.2.3

      Description

      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.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jaikiran Jaikiran Pai
                Reporter:
                jaikiran Jaikiran Pai
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: