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

Build EJB Timer Service on top of Quartz

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • EJB 3.0 RC9 - FD
    • None
    • None
    • None

    Attachments

      Issue Links

        is related to

        Feature Request - Feature requests from customers and/or users EJBTHREE-1432 Provide EJB3 timer config files for other 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.
        • Open

        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

        Task - Represents a small unit of work that is not end-user facing. EJBTHREE-1697 Move the current ejb3 timer service to a separate optional component

        • Critical - To be worked on immediately following BLOCKER issues.
        • Resolved

        Task - Represents a small unit of work that is not end-user facing. EJBTHREE-630 EJB timers not persisted upon undeployment

        • 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 JBAS-1091 Allow ejb timers to persist across server restarts

        • 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:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: