Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-4832

8. Contexts and Dependency Injection (CDI): no mention of specialization

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Trivial
    • Resolution: Out of Date
    • Affects Version/s: 7.0.0.GA
    • Fix Version/s: None
    • Component/s: Documentation
    • Labels:
      None

      Description

      Documentation: https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform//7.0/development-guide/chapter-8-contexts-and-dependency-injection-cdi

      Issue:
      The documentation mentions @Alternative but it does not mention @Specializes which is kind of connected. In certain cases you want to use @Alternative but find out that is not enough and that is when @Specializes comes into play.

      Solution:
      Add a subsection to 8.2.8. Alternative Beans where you mention @Specializes.
      Weld doc has a great sample showing how you actually get from using alternatives to specialization and why. Something on a similar bases might be added here.

      Please note that I am not entirely sure you should add this. It is surely not as common as alternatives and I can see the doc is very basic and general. However it is probably still more common that extensions which are present. So I will leave that up to you whether or not to add this (sub)section.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                rhn-support-pnag Priyanka Nag
                Reporter:
                manovotn Matěj Novotný
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: