A Java geek

Apr 28, 2013 integration testing test unit testing

Integration tests from the trenches

This post is the written form of one of my submission for Devoxx France 2013. As it was only chosen as backup, I lacked the necessary motivation to prepare it. The subject is important though, so I finally decided to write it down. In 2013, if you’re a standard developer, it is practically a given that you test your code. Whether you’re a practicioner of TDD or just create them afterwards, most realize a robust automated test harness is not optional but mandatory. Unit Test vs Int

Apr 21, 2013 bean validation

Design by contract and bean validation

I must confess that despite all benefits of defensive programming, I usually limit myself to not expose mutable attribute to the outside world. Why is that? I believe this is mostly because of readability. Have a look at the following piece of code.

Apr 14, 2013 commerce hybris solution

The middle path approach

I’ve been doing software development for most of my career, so that I think myself as a software developer (or software architect), even though I’ve dabbled in solutions engineering more than once. This surely has an effect on how I see the architecture landscape, but I’ll try to be as objective as possible. Historically, there have been two approaches in providing software solutions to business requirements.

Apr 7, 2013 javascript

JavaScript namespace and restricted access

I began developing with JavaScript more than 10 years ago in order to handle DOM updates on the client-side. At this time, this usage was called DHTML and I was one of the few Java developers that had some interest in it. Still, JavaScript was considered a second-class language, something that was somewhat necessary but wasn’t professional enough. Fast-forward: the year is 2013 and JavaScript is everywhere: developers are using JavaScript both server- and client-sideHTML5 uses JavaScript

Mar 30, 2013 devoxx html5 jboss spring

Devoxx France 2013 - Day 3

Classpath isn’t dead… yet by Alexis Hassler Classpath is dead! — Mark Reinold What is the classpath anyway? In any code, there are basically two kinds of classes: those coming from the JRE, and those that do not (either becasue they are your own custom class or becasue they come from 3rd-party libraries). Classpath can be set either with a simple java class load by the -cp argument or with a JAR by the embedded MANIFEST.MF. A classloader is a class itself. It ca

Mar 29, 2013 devoxx gwt scala

Devoxx France 2013 - Day 2

This is a a sum-up of talks I attended on the second day of Devoxx France. It includes Scala, GWT, a comparison of web frameworks and not-mainstream data structures.

Mar 28, 2013 angularjs devoxx html5 vaadin

Devoxx France 2013 - Day 1

Rejoice people, it’s March, time for Devoxx France 2013! Here are some notes I took during the event. It includes Java EE, Angular JS, Gradle, HTML5 and Vaadin.

Mar 17, 2013 Architecture

KISS your architecture

The project I’m working on these days is not properly legacy but has seen some twists that renders it less than ideal. On this project, one of the worst point that has been an obstacle for me to develop a simple feature is layered architecture. What, shout all experienced developers, layered architecture is at the root of maintainability! and I agree wholeheartedly. So, how could layer architecture be an obstacle?

Mar 10, 2013 javaconfig spring

Consider replacing Spring XML configuration with JavaConfig

Spring articles are becoming a trend on this blog, I should probably apply for a SpringSource position :-) Colleagues of mine sometimes curse me for my stubbornness in using XML configuration for Spring. Yes, it seems so 2000’s but XML has definite advantages: Configuration is centralized, it’s not scattered among all different components so you can have a nice overview of beans and their wirings in a single placeIf you need to split your files, no problem, Spring let you do that.

Feb 24, 2013 search solr

Solr overview from a beginner's point of view

I’ve recently begun diving into Search Engines in general and Solr in particular. This is my understanding of it so far. Why Solr? It isn’t really feasible to execute blazing fast search queries on very big SQL databases for 2 different reasons. The first reason comes SQL databases favoring lack of radiancy over performance. Basically, you’d need to use JOIN in your SELECT. The second reason is about the nature of data in documents: it’s essentially unstructured plain