100% code coverage, Hibernate Validator and Design by Contract Code coverage in unit testing was one of the first things I learned in my software engineering career. The company I worked at taught me that you should have 100% coverage as a goal, but achieving it does not mean there are no bugs in the system. At ...
A really simple but powerful rule engine I have the requirement to use a rule engine. I want something light weight and fairly simple, yet powerful. While there are products out there which are super good, I don't want something with the big learning overhead. And, I fancied writing my own! ...
JSR-299 & @Produces I've been reading JSR-299 and I have a few thoughts. First, a quote from chapter 1: "The use of these services significantly simplifies the task of creating Java EE applications by integrating the Java EE web tier with Java EE enterprise services. In ...
When tool strategy gets on your nerves In the beginning A long time ago, before the days of code prettifiers like Jalopy, we wrote code and we tested code. That code was fun to write. And because it was fun to write, we were motivated to write it well and test it well. Welcome Jalopy It ...
Eclipse e4 - from Client to Server and back again with MVC I recently participated in a course where we learned about Eclipse e4 development. It was all very interesting, especially the reliance on declarative services from OSGi. I decided to have a think about how to build a skeletal application which makes ...
Recent Responses
Re: Persistent State Machine with Apache SCXML Which JPA version did you use? I find this solution very interesting. It opens the door to use SCXML for managing life cycles in business entities. There, persistence is really necessary! Thanks!
Re: JSR-299 & @Produces Hi Ant, It's just because CDI was the latest spec in Java EE 7 and they couldn't go back and change all the other specs. I hope this will be addressed in Java EE 7. There is lot more to do. In JSF and CDI are now the same Annotations ...
Re: JSR-299 & @Produces Hi Anonymous (-/62.91.33.77), I thought for a while about whether I would approve your comment, because frankly, it's tone is very aggressive. The fact you haven't left your name didn't help. In the future, please be a little nicer :-) I won't comment ...