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

Expose contexts via Weld API

    XMLWordPrintable

Details

    Description

      Rework contexts and lifecycle to produce a set of "manageable contexts" which can be activated/deactivated/invalidated via API calls. Some contexts can be bound to underlying data stores such as the Http Session.

      Attachments

        Issue Links

          incorporates

          Feature Request - Feature requests from customers and/or users WELD-656 Move new ConversationManager interface to public API

          • 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

          Feature Request - Feature requests from customers and/or users WELD-675 Add a ServletContext configuration parameter for enabling/disabling automatic session creation in WeldListener/ServletLifecycle

          • 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

          Feature Request - Feature requests from customers and/or users WELD-688 Implement a BoundConversationContext

          • 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

          Feature Request - Feature requests from customers and/or users WELD-451 Allow including the cid in the url to be configurable

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is related to

          Feature Request - Feature requests from customers and/or users WELD-693 Add a way to get the active context easily

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

          Activity

            People

              pmuiratbleepbleep Pete Muir (Inactive)
              pmuiratbleepbleep Pete Muir (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: