Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-1697

Move the current ejb3 timer service to a separate optional component

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Critical
    • 1.1.0
    • None
    • None
    • None

    Description

      Currently EJB3 doesn't use the EJB3 TimerService. It should be moved out of the default setup and made optional.

      Attachments

        Issue Links

          blocks

          Component Upgrade Subtask - A subtask tracking an update to a bundled component JBAS-6430 Upgrade EJB3 to 1.1.2

          • 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
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. JBAS-6304 EJB3TimerService cannot start with some databases

          • 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
          is related to

          Task - Represents a small unit of work that is not end-user facing. JBAS-6417 Move ejb3-timer-service.xml to docs/examples/ejb3

          • 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
          relates to

          Feature Request - Feature requests from customers and/or users EJBTHREE-619 Build EJB Timer Service on top of Quartz

          • 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

          Patch - An improvement or enhancement to an existing feature or task. Includes patches submitted by community commiters. JBAS-1310 EJB timer implementation on top of Quartz

          • 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

          Activity

            People

              rhn-engineering-cdewolf Carlo de Wolf
              rhn-engineering-cdewolf Carlo de Wolf
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: