Summa

We have all been in projects where we use a combination of open source libraries, for different components of our architecture. We know theoretically that it should work, but alas, something blows up at runtime. If we’re lucky, we experience this on a weekly basis, but we don’t get lucky that often. The “Conundrum Solved” series will tackle some of these hair-pulling, sleep-depriving, grouch-inducing problems some of us at Summa have encountered in our projects. We hope that by sharing them with you, you’ll keep your hair, get enough sleep, and maintain a smile on your face!

Problem: Invalidly getting an InvalidStateObjectStateException thrown upon calling  merge(), even if there were no updates to the entity.

Continue Reading 5 comments

Think it’s a weird kind of question? Not for people who have worked (or are working) on applications that are moving from one framework to another. I happened to work on one such project where a transition from Struts to Spring MVC was being done over a few releases. Not unexpectedly, this approach of supporting two frameworks at the same time gave the development team its own share of interesting challenges. And one such issue was how to use a new technology i.e. Spring themes in both frameworks, of course we could choose not to use it in enhancements to legacy Struts based application flows but then that would have meant doing the enhancements twice.

Continue Reading Add comment

What could be simpler than property files? In an enterprise application, it turns out, many things! In this post I’ll take a look at a few subtle complexities to managing properties in an enterprise Java Spring application, and hopefully demonstrate how a little fore-thought in design can yield big savings in terms of time, confusion, bugs, and gray hair down the road.

Continue Reading 5 comments