Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-2282

Revisit the way we fire ApplicationScoped events in servlets

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • 3.1.x
    • 3.0.0.Alpha17
    • Servlet Container Support
    • None

    Description

      Currently, we use kind of a 'nasty' way to fire @Destroyed and @BeforeDestroyed events for App scope in servlet environment. As it is, these events don't really have much value as they are not closely linked to how servlets operate. Plus they are fired one right after the other.

      NOTE: @BeforeDestroyed is added as a part of WELD-2269

      See org.jboss.weld.servlet.HttpContextLifecycle#contextDestroyed for code.

      We should try to think of an alternative approach (SPI?).

      Attachments

        Issue Links

          relates to

          Task - Represents a small unit of work that is not end-user facing. WELD-2229 Reflect the output of CDI-625 - when exactly are @Initialized(X.class) and @Destroyed(X.class) events fired

          • 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.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              manovotn Matěj Novotný
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: