Spring 4: CGLIB-based proxy classes with no default constructor

In Spring, if the class of a target object that is to be proxied doesn’t implement any interfaces, then a CGLIB-based proxy will be created. Prior to Spring 4, CGLIB-based proxy classes require a default constructor. And this is not the limitation of CGLIB library, but Spring itself. Fortunately, as of Spring 4 this is no longer an issue. CGLIB-based proxy classes no longer require a default constructor. How can this impact your code? Let’s see.

One of the idioms of dependency injection is constructor injection. It can be generally used when the injected dependencies are required and must not change after the object is initiated. In this article I am not going to discuss why and when you should use constructor dependency injection. I assume you use this idiom in your code or you consider using it. If you are interested in learning more, see the resources section in the bottom of this article.

Contructor injection with no-proxied beans

Having the following collaborator:

package pl.codeleak.services;

import org.springframework.stereotype.Service;

public class Collaborator {
    public String collaborate() {
        return "Collaborating";

we can easily inject it via constructor:

package pl.codeleak.services;

import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.stereotype.Service;

public class SomeService {

    private final Collaborator collaborator;

    public SomeService(Collaborator collaborator) {
        this.collaborator = collaborator;

    public String businessMethod() {
        return collaborator.collaborate();


You may notice the both Collaborator and the Service has no interfaces, but they are no proxy candidates. So this code will work perfectly fine with Spring 3 and Spring 4:

package pl.codeleak.services;

import org.junit.Test;
import org.junit.runner.RunWith;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.test.context.ContextConfiguration;
import org.springframework.test.context.junit4.SpringJUnit4ClassRunner;
import pl.codeleak.Configuration;

import static org.assertj.core.api.Assertions.assertThat;

@ContextConfiguration(classes = Configuration.class)
public class WiringTests {

    private SomeService someService;

    private Collaborator collaborator;

    public void hasValidDependencies() {



Contructor injection with proxied beans

In many cases your beans need to be decorated with an AOP proxy at runtime, e.g when you want to use declarative transactions with @Transactional annotation. To visualize this, I created an aspect that will advice all methods in SomeService. With the below aspect defined, SomeService becomes a candidate for proxying:

package pl.codeleak.aspects;

import org.aspectj.lang.annotation.Aspect;
import org.aspectj.lang.annotation.Before;
import org.springframework.stereotype.Component;

public class DummyAspect {

    public void before() {
        // do nothing


When I re-run the test with Spring 3.2.9, I get the following exception:

Could not generate CGLIB subclass of class [class pl.codeleak.services.SomeService]: Common causes of this problem include using a final class or a non-visible class; nested exception is java.lang.IllegalArgumentException: Superclass has no null constructors but no arguments were given

This can be simply fixed by providing a default, no argument, constructor to SomeService, but this is not what I want to do - as I would also need to make dependencies non-final.

Another solution would be to provide an interface for SomeService. But again, there are many situation when you don’t need to create interfaces.

Updating to Spring 4 solves the problem immediately. As documentation states:

CGLIB-based proxy classes no longer require a default constructor. Support is provided via the objenesis library which is repackaged inline and distributed as part of the Spring Framework. With this strategy, no constructor at all is being invoked for proxy instances anymore.

The test I created will fail, but it visualizes that CGLIB proxy was created for SomeService:

to be exactly an instance of:
but was an instance of:

After removing the first assertion from the test, it will run just perfectly fine.


In case you need read more about constructor dependency injection, have a look at this great article by Petri Kainulainen: http://www.petrikainulainen.net/software-development/design/why-i-changed-my-mind-about-field-injection.

Core Container Improvements in Spring 4: http://docs.spring.io/spring/docs/current/spring-framework-reference/html/new-in-4.0.html#_core_container_improvements

You may also be interested in reading my other articles about Spring: Spring 4: @DateTimeFormat with Java 8 Date-Time API and Better error messages with Bean Validation 1.1 in Spring MVC application


  1. Nice post, Ya I agree, Spring 4 has made some significant improvements, we have also updated the our bootstrap project (a skeleton project which helps us lift off projects) to use spring 4. In case you any one is interested they can check it out here https://github.com/sudarshan89/bootstrap

  2. I am facing a similar problem right now. A subclass is created by CGLIB, but there is an exception named BeanNotOfRequiredTypeException, which is almost the same assertion as your test. Do you know how to remove this assertion from springsbeansfactory?

  3. Hi, right now I am facing the related problem. I am trying to inject the bean into my controller, but during the runtime, CGLIB also generates a proxy subclass named "CsrfToken$$EnhancerBySpringCGLIB$$17451fad"-as what you received in your test. But in my log, there is an exception caused by the difference between the class names. I wonder if there is any way to skip this check or get rid of using proxy? This exception prevent the framework from starting right now!


Post a Comment

Popular posts from this blog

Different ways of validating @RequestBody in Spring MVC with @Valid annotation