Java threads can be in six different states: NEW, RUNNABLE, BLOCKED, WAITING, TIMED_WAITING, and TERMINATED. We will explore them here.

In this post, we are going to discover a new, important feature that Java 8 brings to us in the event of hash collisions.

This post looks at using and configuring the Log4j 2 properties file, letting you change various configuration options without modifying your application code.

Here we're going to look at the Akka actor model with a simple example: fetching weather data from Yahoo.

Skip the HTML! Learn about utilizing FreeMarker and Vaadin to help you generate HTML templates, so you don't have to write them yourself.

In the upcoming Java 9 release, it will be possible to declare private and protected methods in interfaces. Learn how you can use almost the same features in Java 8 interfaces today.

Adding global exception handling to an Java EE MVC application is quite simple.

James Gosling sounds off on Oracle's culture and handling of Java, clarifies some past comments, and addresses his "low expectations."

The first impressions of a Java enthusiast when looking at Go's features.

The conclusion of this series about multiple dispatch focuses on using the technique in Clojure.

Dropwizard has taken the Java world by storm with it's ease of use and great functionality. The metrics library is particularly powerful for anyone wanting to measure statistics in their Java applications.

In this post, you will learn about autowiring—its limitations, advantages, and disadvantages in detail. You also get to know about different modes of autowiring used in Java web development.

This article discusses the history of polyglot programming, and considers whether it's still a valid premise.

To diagnose any memory problems, the Garbage Collection log file is the best place to start. Take a look at the anatomy of a GC log file in this helpful article.

One of the major new language features in Java 8 is the lambda function. In fact, it is one of the biggest changes since the Java 1 release. Take a look at this introduction to Java 8's lambda function.

An article about how to override the default security-related information associated with a JAX-RS request using a custom SecurityContext.

There are a lot of ways to implement Access Controls, and some are slightly complicated. Have you considered using REST?

Using Maven to effectively test software when test classes are not already packaged by Maven.

Testing that goes beyond just unit testing and integration testing. Why we should be doing full system testing.

[Ivan Zerin provides a primer on mocking methods that contain generic return types.] There are several cases where construction when().thenReturn is not suitable during Unit tests. One of then generic return type. I have faced such issue, let's take a look. There is a method in interface declaration: public interface FooInterface { public Iterable getList(); ... } Implementation looks like this: public class Foo implements FooInterface { public List getList() { ... } ... } At first mocking of such method should not be something unusual: public class UnitTest { @Mock private FooInterface mockFoo; @Test public void someUnitTest() { ... List testList = generateTestList(); when(mockFoo.getList()) .thenReturn(testList); } } But this code won't compile with error: Cannot resolve method 'thenReturn(List). Seems to be some mistake, cause returned type are correct from the interface point of view. This error happening cause compiler can not gurantee that returned type of method getList() will be List. Actually return type of method getList() in this case is Iterable and this means "Return some Iterable object with any objects that extends SomeClass". Let's rename this type as 'X'. So when(mockFoo.getList()) will create object OngoingStubbing> and it has method thenReturn(Iterable). Compiler can not tell what type X before runtime and cannot perform safe cast from List to Iterable (we perfrom actuall call of method thenReturn(List)). Sounds a little tricky but let's assume that SomeClass is standard Java class Number. Then classes Integer and Double are both fulfill the criteria of List. Let's say that as return type of mock we will use List, in this case, compiler should be ready that actual work with code during runtime will be performed with List too, but it is clearly that cast from Double to Integer will be incorrect (try to cast double value 12.6 to int). You could argue that in the case of mockito compiler won't need to bother about the casting of returned type because call of original method would not produce anything, but it is known by mockito. From compiler point of view, it is only Java code, that should be checked for safety and correctness before compiling. Ok, so how we should deal with such cases in mockito? Use doReturn() method: doReturn(testList).when(mockFoo).getList(); Such expression is not type safe, so it were designed for exceprional cases, so use it only when you cannot use standart when().thenReturn(), which is the type-safe, elegant and more readable syntax.