Monday, January 28, 2013
Wednesday, January 23, 2013
Drools - Rete Alogrithm explanation
Quite recently I have found a very nice article about the Rete Algorithm.
Thursday, January 17, 2013
New Too Much Coding repository!
Hi!
As you know there is a code repository of Too Much Coding sources here at Bitbucket. If you don't like it you can also find the Too Much Coding sources at GitHub!
Enjoy :)
As you know there is a code repository of Too Much Coding sources here at Bitbucket. If you don't like it you can also find the Too Much Coding sources at GitHub!
Enjoy :)
Tuesday, January 15, 2013
Drools integration with Spring vs manual rules creation
Hi!
Often in your work you can come across with issues related to business logic. Let us assume that you have dozens of rules (for the time being in our project we have more than 50 and I used to work on a project where we had hundreds of those rules) that you have to implement, divide into some classes, subclasses, abstractions and of course unit test. This can be difficult and timeconsuming to both write and support. There are many ways of dealing with this problem and I will show you one of them - JBoss Drools.
Drools is a library specifically created for such purposes like implementing rules. As presented in Wikipedia:
"Drools is a rule engine implementaion based on Charles Forgy's Rete Algorithm tailored for the Java language."It contains a rule engine that can process rules wirtten using the Drools language (you can also provide rules in Excel spreadsheets! - perfect for Business side to support and maintain).
In the following example we will take a look at the way one can integrate JBoss Drools with Spring and an example of solving a similar problem without Drools.
Monday, January 7, 2013
Very interesting article about XSD
A friend from my project (that will soon start his own blog ;) here is his blog ) has found a very interesting article about XSDs and namespaces.
Tutorial about XSD and namespaces
Tutorial about XSD and namespaces
Thursday, January 3, 2013
Hamcrest Matchers, Guava Predicate and Builder design pattern
Hi coding addicts :)
Often, while coding we have to deal with some POJO objects that have dozens of fields in them. Many times we initialize those classes through a constructor having dozens of arguments which is terrible in any possibly imaginable way :) Apart from that the functions that use those constructors are hardly testable. Let's take a closer look at using a Builder to change that situation, together with Hamcrest matchers and Guava Predicates to unit test it.
Let's start off with taking a look at the POJO class.
Subscribe to:
Posts (Atom)