Liferay diaries: Log4j

Setting up log4j for a Liferay and Spring application is easy: in /WEB-INF/log4j.properties log4j.category.org.springframework=DEBUG,console And some entries in web.xml <context-param> <param-name>log4jConfigLocation</param-name> <param-value>/WEB-INF/log4j.properties</param-value> </context-param> <listener> <listener-class>org.springframework.web.util.Log4jConfigListener</listener-class> </listener>

Liferay diaries: Serving resources from a portlet with Spring

So there comes the day when you finally have to serve an image, pdf or excel report generated by a portlet or, more elegantly, by a Spring controller backing a portlet. At a first take this may seem impossible since the markup produced by a portlet is embedded in the markup (i.e. HTML) of all … Continue reading Liferay diaries: Serving resources from a portlet with Spring →

Compact mockito: shorter answer notation

[Update 2014.10.08] The code is now on github. If you value brevity in tests like I do then maybe you would agree that mockito's doAnswer statements contain much boilerplate. That is certainly not mockito's fault but rather a result of java's inflexible syntax. When testing, i.e. GWT code one will frequently find the need to … Continue reading Compact mockito: shorter answer notation →

Ensuring JUnit test suite contains all tests

While cleaning up today one of my projects I found a JUnit test that was not part of a test suite and never was executed. 'Never again' I say and here is how: a test suite that scans base packages for tests. The particular code: Is tailored to the specific project's needs Compares the tests … Continue reading Ensuring JUnit test suite contains all tests →

A better eq() when matching method arguments with Mockito

I learned late of Mockito [1], even so more I love it. Walking a little farther away from the basics, a frequent needs presents itself to match method parameters (either when specifying or verifying behaviour) based on properties of complex objects which do not implement the java equals contract. Such an example would be verifying … Continue reading A better eq() when matching method arguments with Mockito →