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

Consolidated approach for dumping generated sources

    Details

    • Type: Story
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 7.28.0.Final
    • Fix Version/s: None
    • Component/s: core engine
    • Labels:
      None
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      Using `drools.dump.dir = <String>` from KnowledgeBuilderConfiguration one can configure directory for dumping generated sources. New DRLs are generated out of decision tables and new java classes are generated out of DRLs into that location which makes it possible to analyze errors and have better understanding how code will actually work.

      DSL parser uses different approach for dumping. It looks for `#result` switch and one need to configure logging for respective classes to see result of the parsing, see

      org.drools.compiler.lang.dsl.DefaultExpander.expand(String drl)
      

      Could it be consolidated approach used for all generated sources? Dump directory as a single place for all generated sources looks very handy. Could you please add respective logic for DefaultExpander to mimic

      org.drools.compiler.builder.impl.KnowledgeBuilderImpl.generatedDrlToPackageDescr
      

      and dump generated sources into one place if respective property set?

        Gliffy Diagrams

          Marvel

          Marvel Prototype Add-On for Confluence Server written by David Simpson.

            Attachments

              Activity

                People

                • Assignee:
                  tkobayashi Toshiya Kobayashi
                  Reporter:
                  mykhaylo.adamovych Mykhaylo Adamovych
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated: