Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-1649

Avoid using Class.forName in static factory methods

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • None
    • None
    • core engine
    • None
    • 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31
    • NEW
    • NEW

    Description

      All factory calls should go through the ServiceRegistryImpl instead of using Class.forName

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. DROOLS-1705 Audit remaining Class.forName in static factory methods

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

          Task - Represents a small unit of work that is not end-user facing. DROOLS-1693 ProcessBuilderFactory refactoring dealing tech debt

          • 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

              mfusco@redhat.com Mario Fusco
              mfusco@redhat.com Mario Fusco
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: