Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Good job! #2
You filled the space between a drools like engine and a custom predicate model. that is very good and unique.
I would suggest to add to the how-to any verbiage to immutability -just for awareness/guidance sake-: I can see quiet a few folks using this in a web app and they might be wondering about that aspect.
You will be pleasantly surprised on how many folks do not get engines like drools, but would go with something like this instead and realize that is exactly what they needed :)
I have seen many folks (under)using full blown rules engines for very basic requirements, just like using a hammer to kill a fly :-) and this is why I developed Easy Rules.
The point about immutability is very important indeed, I will consider mentioning it in documentation for next release. If you like to contribute it, you are welcome.
Great library! I agree this is a nice simple and lightweight solution between drools and a custom predicate. I had to fork and remove the JMX support to use this library with Android though. The java.lang.management library depends on the JVM which Android doesn't use. Just thought I would mention this. Cheers!
I was not aware that the JMX API is not supported on Android and I understand why you had to fork Easy Rules. You have removed all the JMX related code from the engine but there still the
This is important because, if so, I have to redesign Easy Rules to make the JMX reconfiguration feature optional so that the core engine can be used in Java and Android. I have to provide a better design so that users should not fork the project and remove a feature, they should instead fork the project to add a feature maybe (Open-Closed principle)
PS: I just posted this message on gitter. I think it's a better place to continue this discussion.