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

EJB 2.1 Stateful Session Beans don't deploy

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • AS 4.2.1.GA, AS 5.0.0.Beta3
    • EJB 3.0 RC9 - Patch 1, AS 4.2.0 GA
    • None
    • None
    • Workaround Exists
    • Hide

      Put the EJB 2.1 beans in a EJB 2 deployment and reference them from there.

      Show
      Put the EJB 2.1 beans in a EJB 2 deployment and reference them from there.

    Description

      Deploying an EJB 2.1 SFSB through the EJB3 deployer doesn't work. A lot of precondition checks will complain about the code.

      Any of the following exceptions will occur:
      java.lang.RuntimeException: @javax.annotation.PostActivate annotated method has the wrong signature ... (EJB3 12.4)
      java.lang.RuntimeException: @javax.annotation.PostConstruct annotated method has the wrong signature ... (EJB3 12.4)
      java.lang.RuntimeException: @javax.annotation.PrePassivate annotated method has the wrong signature ... (EJB3 12.4)
      java.lang.RuntimeException: Interceptors can only have one post-construct/@PostConstruct method - ...

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. EJBTHREE-963 ejbCreate method is optional in EJB 2.1 bean

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. EJBTHREE-966 setSessionContext not called on an EJB 2.1 bean

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users EJBTHREE-947 Relaxed signature checking

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-engineering-cdewolf Carlo de Wolf
              rhn-engineering-cdewolf Carlo de Wolf
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: