Spring @Scope("request") does not work with Servlet 3.0

Question

I am trying to use a request scoped been inside my servlet 3.0 application.

I am not using the web.xml but an implementation of WebApplicationInitializer. The onStartup method looks like this:

@Override
public void onStartup(ServletContext servletContext) throws ServletException {

    AnnotationConfigWebApplicationContext applicationContext =
            new AnnotationConfigWebApplicationContext();

    applicationContext.setServletContext(servletContext);
    applicationContext.scan("package containing proxy scoped bean and other stuff");

    applicationContext.refresh();        

    servletContext.addListener(new ContextLoaderListener(applicationContext));
    servletContext.addListener(new RequestContextListener());
}

and the request scoped bean looks like this:

@Component
@Scope(value = "request", proxyMode = ScopedProxyMode.TARGET_CLASS) 
public class CallerInformation {

    private String clientIp;

    public String getClientIp() {
        return clientIp;
    }

    public void setClientIp(String clientIp) {
        this.clientIp = clientIp;
    }
}

Now the injected "CallerInformation" is not a CGLIB-proxy but behaves like prototype scoped, it is a different instance in every class and it does not hold any information through the request...

Any ideas what I am doing wrong?

EDIT:

I have tried the same scenario with servlet 2.5 and web.xml config and it worked like hell ;)

Have you tried it with servlet 3.0 and web.xml? try it also... — rahul maindargi, Apr 25 '13 at 11:56
Also try to change the order as `servletContext.addListener(new RequestContextListener()); servletContext.addListener(new ContextLoaderListener(applicationContext));` Listerner orders can also do some problems . Not 100% sure thats the cause here.. ` — rahul maindargi, Apr 25 '13 at 12:07
Why using proxyMode = ScopedProxyMode.TARGET_CLASS ? if you use proxyMode=ScopedProxyMode.INTERFACES it will fix your problem, it fixed the problem to me in this question. http://stackoverflow.com/questions/23724716/problems-with-bean-declared-as-scope-request-in-servlet-3-0-configuration — alexzm1, May 19 '14 at 03:47

Philipp Sander · Answer 1 · 2013-04-25T09:17:46.130

0

the behavior is right. the instance only lives the one request. see this site for further information.

try to inject the spring-component with the @Autowired annotation

edited Apr 25 '13 at 09:17

answered Apr 25 '13 at 07:54

Philipp Sander

10,139
6
45
78

I think you did not understand my problem: Inside of ONE request there are n different instances of CallerInformation, each with own (in my case null) property values. – woezelmann Apr 25 '13 at 07:59
ah okay i understand. have you tried checking if there are multiple request instance? – Philipp Sander Apr 25 '13 at 08:07
I don't think that's the problem. The CallerInformaion instance should be some kind of CGLIB-proxy, but it isn't. I think Spring does not evaluate the @Scope or somthink... – woezelmann Apr 25 '13 at 08:30
how do you autowire it? constructor, setter, or field? – Philipp Sander Apr 25 '13 at 08:41
with the @Inject annotation – woezelmann Apr 25 '13 at 08:58
@Autowired did not help. The problem is not, that there is no bean injected, the problem is that the bean is not request scoped. – woezelmann Apr 25 '13 at 09:48

Spring @Scope("request") does not work with Servlet 3.0

1 Answers1