关于自定义UI加载、编辑、上传Drools文件的技术咨询

Great question! Let's break this down for you based on my experience with Drools and rule management tools:

• Business Central (Formerly Drools Workbench)
  This is the official visual rule management platform from the Drools ecosystem. It fully supports importing existing DRL files, provides guided rule editors, decision tables, and a raw DRL editing interface. You can let users modify or delete rules directly in the UI, then either deploy the updated rule package to your Drools engine or export the revised DRL files. It even supports version control and team collaboration, and you can extend its UI to match your custom requirements if needed.
• Dynamic Rule Loading via KIE API
  If you don't need the full weight of Business Central, Drools' KIE API lets you dynamically load and update rule packages without restarting your application. For example, you could build a simple custom UI for users to upload modified DRL files, then refresh the rule engine using code like this:

  KieServices kieServices = KieServices.Factory.get();
  KieContainer kieContainer = kieServices.newKieClasspathContainer();
  // After user uploads updated DRL, reload the container
  kieContainer.updateToLatestVersion();
  

• Lightweight Code Editor Integrations
  You can use open-source code editor components like Ace Editor or CodeMirror to build a custom DRL editing UI. Both support syntax highlighting (you can find pre-built DRL syntax definitions online), letting users edit rule files directly. Pair this with the KIE API to handle file uploads and rule engine updates—perfect if you need a flexible, minimal UI.
• Third-Party Visual Rule Editors
  Some open-source projects focus on visual rule editing that integrates with Drools. For example, legacy components from Drools Guvnor (now part of Business Central) can be adapted, or you can use low-code rule editors that export rules in DRL format, which you can then load into your Drools engine.

Absolutely not! While storing rule metadata in a database and generating DRL via templates (like using Freemarker or Thymeleaf) is a valid approach (great for non-technical users who prefer structured interfaces), there are several alternatives:

• Store Full DRL Files in Database
  Save complete DRL file content directly in a TEXT or BLOB field. When users modify rules through your UI, update the database record, then have your application read the DRL content and load it dynamically via the KIE API.
• Leverage Version Control
  Host your DRL files in a Git/SVN repository. Build a UI that interacts with the version control API to let users edit, commit, and push changes. Then use Drools' KieScanner to monitor the repository and automatically load the latest rules into the engine.
• Hybrid Visual + Raw DRL Editing
  Offer users two editing modes: a visual interface for modifying rule conditions/actions (for simple rules) and a raw DRL editor (for complex, custom logic). Combine the outputs from both modes into a final DRL file for deployment.

内容的提问来源于stack exchange，提问作者indra