Uploaded image for project: 'Product Technical Learning'
  1. Product Technical Learning
  2. PTL-935

AD183-29: Factual errors in POJO to EJB conversion

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • AD183 - EAP 7.0 1 20171212
    • AD183
    • None
    • 3
    • ILT, ROLE, VT
    • en-US (English)

      URL:
      Reporter RHNID: grega.bremec@softergee.si
      Section: - Demonstration: Converting a POJO to an EJB
      Language: en-US (English)
      Workaround:

      Description: There are several severe factual errors in the explanation of step 5 of the POJO to EJB conversion.

      Adding @RequestScoped and @Named annotations to a POJO does NOT make it an EJB. It makes it a request-scoped CDI bean bound to an EL name.

      Adding an @EJB annotation to the eightBallEJB field does NOT use CDI but rather causes a no-interface EJB lookup.

      The Arquillian test works, of course, because it doesn't test the CDI bean.

      The web application works, because the entire UoW happens within the scope of one client request (which requires it to use the same CDI bean).

      However, this is pure coincidence and does not do anything to expose the delicate relationship between CDI and EJB containers; on the contrary, it obscures it.

       

              rht-zgutterman Zachary Gutterman
              gregab@p0f.net Grega Bremec
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: