engilyin commented on issue #6309: URL: https://github.com/apache/incubator-kie-drools/issues/6309#issuecomment-2816782740
Great thank you very much! I tried your suggestion with `servicePriority` in my poc/pet project and it works just fine! https://github.com/engilyin/drools-spring-boot-3-sample/blob/4abea744502d0c9698982a27298a47f7d9053c9e/src/main/java/com/engilyin/drools/providers/SpringBootRuleUnitProvider.java#L57-L60 In my case I'm trying to adopt modern Drools with Spring Boot so I managed to simplify the file scanning with `PathMatchingResourcePatternResolver` P.S. sorry if that is wrong place to discuss some off topic related questions. Based on the default `RuleUnitProvider` algorithm I'm wondering. Is it supported at all for modern Unit/Provider (non `classic engine`) approach to organize: 1) the lazy loading of units. I see now it is all loaded at ones. And not at startup time but on the first `fire`. If we have many rules and files that might make the first call very long. And suppose we are running many instances on K8s. The pods can come in and out so that would happen too often. 2) Build the rule units on compile time and load the compiled drl data so we will not spend run time for to build it on every instance? Should we create our Custom `RuleUnitProvider` if we need `1` or `2` or that is possible to activate with default `RuleUnitProvider`? Thanks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
