Uploaded image for project: 'CDI Specification Issues'
  1. CDI Specification Issues
  2. CDI-730

The order in which contexts are destroyed is undefined.

    XMLWordPrintable

Details

    • Clarification
    • Resolution: Obsolete
    • Minor
    • None
    • 2.Future, 1.2.Final, 2.0 .Final
    • None
    • None

    Description

      The order in which contexts are destroyed is not defined in the spec, I believe this should be made explicit.

      At present weld destroys conversation, request, then session context in that order. I think this should become the standard and written into the spec.

      For background there is this email by Martin Kouba: http://lists.jboss.org/pipermail/weld-dev/2018-June/003694.html

      Attachments

        Issue Links

          is duplicated by

          Feature Request - Feature requests from customers and/or users CDI-732 Clarify that the Context for RequestScoped must be active during @PreDestroy calls

          • 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

              Unassigned Unassigned
              benjamin-confino Benjamin Confino (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: