• Now all data be ready for publish, We had made our blog alive now. Haha.

  • These days CCP GFW blocked all the IPs from US and when I switch my IP in google Cloud, the disk data cannot be restore again. I have to restart my blog totally, Now the website is still building…

What causes “java.lang.IllegalStateException: Neither BindingResult nor plain target object for bean name ‘command’ available as request attribute”?- Stack Overflow

Java PingBook 2 weeks ago (10-30) 18 0


This is meant to be an extensive canonical question & answer post for these types of questions.

I’m trying to write a Spring MVC web application where users can add movie names to an in-memory collection. It’s configured like so

public class Application extends AbstractAnnotationConfigDispatcherServletInitializer {
protected Class[] getRootConfigClasses() {
return new Class[] {};
protected Class[] getServletConfigClasses() {
return new Class[] { SpringServletConfig.class };
protected String[] getServletMappings() {
return new String[] { “/” };


public class SpringServletConfig extends WebMvcConfigurationSupport {
public InternalResourceViewResolver resolver() {
InternalResourceViewResolver vr = new InternalResourceViewResolver();
return vr;

There’s a single @Controller class in the com.example package

public class MovieController {
private final CopyOnWriteArrayList movies = new CopyOnWriteArrayList<>();
@RequestMapping(path = “/movies”, method = RequestMethod.GET)
public String homePage(Model model) {
model.addAttribute(“movies”, movies);
return “index”;
@RequestMapping(path = “/movies”, method = RequestMethod.POST)
public String upload(@ModelAttribute(“movie”) Movie movie, BindingResult errors) {
if (!errors.hasErrors()) {
return “redirect:/movies”;
public static class Movie {
private String filmName;
public String getFilmName() {
return filmName;
public void setFilmName(String filmName) {
this.filmName = filmName;

WEB-INF/jsps/index.jsp contains

<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"%>
<%@ taglib prefix="form" uri="http://www.springframework.org/tags/form"%>

Current Movies:

  • ${movieItem.filmName}

Movie name:

The application is configured with context path /Example. When I send a GET request to


the request fails, Spring MVC responds with a 500 status code, and reports the following exception and stack trace

java.lang.IllegalStateException: Neither BindingResult nor plain target object for bean name ‘command’ available as request attribute

I expected the JSP to generate an HTML

with a single text input, for a Movie name, and a submit button, that I can use to send a POST request with a new Movie. Why does the JSP servlet instead fail to render Spring’s tag?


You’re trying to use Spring MVC’s form tag.

This tag renders an HTML form tag and exposes a binding path to
inner tags for binding. It puts the command object in the PageContext
so that the command object can be accessed by inner tags. [..]

Let’s assume we have a domain object called User. It is a JavaBean
with properties such as firstName and lastName. We will use it as the
form backing object of our form controller which returns form.jsp.

In other words, Spring MVC will extract a command object and use its type as a blueprint for binding path expressions for form’s inner tags, like input or checkbox, to render an HTML form element.

This command object is also called a model attribute and its name is specified in the form tag’s modelAttribute or commandName attributes. You’ve omitted it in your JSP

You could’ve specified a name explicitly. Both of these are equivalent.

The default attribute name is command (what you see in error message). A model attribute is an object, typically a POJO or collection of POJOs, that your application supplies to the Spring MVC stack and which the Spring MVC stack exposes to your view (ie. the M to the V in MVC).

Spring MVC collects all model attributes in a ModelMap (they all have names) and, in the case of JSPs, transfers them to the HttpServletRequest attributes, where JSP tags and EL expressions have access to them.

In your example, your @Controller handler method which handles a GET to the path /movies adds a single model attribute

model.addAttribute(“movies”, movies); // not named ‘command’

and then forwards to the index.jsp. This JSP then tries to render

While rendering this, FormTag (in reality, the InputTag) tries to find a model attribute named command (the default attribute name) so that it can produce an HTML element with a name attribute constructed from the path expression and the corresponding property value, ie. the result of Movie#getFilmName().

Since it cannot find it, it throws the exception you see

java.lang.IllegalStateException: Neither BindingResult nor plain target object for bean name ‘command’ available as request attribute

The JSP engine catches it and responds with a 500 status code. If you want to take advantage of a Movie POJO to simply construct your form correctly, you can add a model attribute explicitly with

model.addAttribute(“movie”, new Movie());

or have Spring MVC create and add one for you (must have an accessible parameterless constructor)

@RequestMapping(path = “/movies”, method = RequestMethod.GET)
public String homePage(@ModelAttribute(“command”) Movie movie, Model model) {…}

Alternatively, include a @ModelAttribute annotated method in your @Controller class

public Movie defaultInstance() {
Movie movie = new Movie();
movie.setFilmName(“Rocky II”);
return movie;

Note that Spring MVC will call this method and implicitly add the object returned to its model attributes for each request handled by the enclosing @Controller.

You may have guessed from this description that Spring’s form tag is more suited for rendering an HTML

from an existing object, with actual values. If you want to simply create a blank

, it may be more appropriate to construct it yourself and not rely on any model attributes.

On the receiving side, your POST handler method, will still be able to extract the filmName input value and use it to initialize a Movie object.

Common Errors

As we’ve seen, FormTag looks for a model attribute named command by default or with the name specified in either modelAttribute or commandName. Make sure you’re using the right name.

ModelMap has a addAttribute(Object) method which adds

the supplied attribute to this Map using a generated name.

where the general convention is to

return the uncapitalized short name of the [attribute’s] Class, according to
JavaBeans property naming rules: So, com.myapp.Product becomes
product; com.myapp.MyProduct becomes myProduct; com.myapp.UKProduct
becomes UKProduct

If you’re using this (or a similar) method or if you’re using one of the @RequestMapping supported return types that represents a model attribute, make sure the generated name is what you expect.

Another common error is to bypass your @Controller method altogether. A typical Spring MVC application follows this pattern:

Send HTTP GET request
DispatcherServlet selects @RequestMapping method to handle request
Handler method generates some model attributes and returns view name
DispatcherServlet adds model attributes to HttpServletRequest and forwards request to JSP corresponding to view name
JSP renders response

If, by some misconfiguration, you skip the @RequestMapping method altogether, the attributes will not have been added. This can happen

if your HTTP request URI accesses your JSP resources directly, eg. because they are accessible, ie. outside WEB-INF, or
if the welcome-list of your web.xml contains your JSP resource, the Servlet container will render it directly, bypassing the Spring MVC stack entirely

One way or another, you want your @Controller to be invoked so that the model attributes are added appropriately.

What does BindingResult have to do with this?

A BindingResult is a container for initialization or validation of model attributes. The Spring MVC documentation states

The Errors or BindingResult parameters have to follow the model object
that is being bound immediately as the method signature might have
more than one model object and Spring will create a separate
BindingResult instance for each of them […]

In other words, if you want to use BindingResult, it has to follow the corresponding model attribute parameter in a @RequestMapping method

@RequestMapping(path = “/movies”, method = RequestMethod.POST)
public String upload(@ModelAttribute(“movie”) Movie movie, BindingResult errors) {

BindingResult objects are also considered model attributes. Spring MVC uses a simple naming convention to manage them, making it easy to find a corresponding regular model attribute. Since the BindingResult contains more data about the model attribute (eg. validation errors), the FormTag attempts to bind to it first. However, since they go hand in hand, it’s unlikely one will exist without the other.

Copyright from PingBook Blog, If not specified, they are original. This site uses BY-NC-SAProtocol authenticated.
For reprinting, please indicate the link of the original text:What causes “java.lang.IllegalStateException: Neither BindingResult nor plain target object for bean name ‘command’ available as request attribute”?- Stack Overflow
LIKE (0)
We create, We sharing! Tag every value data your sharing
Submit comments
Cancel comments
emoji picture bold strikethrough center italic check in

Hi,you need to provide your name and email adress!

  • Name (Required)
  • Email (Required)
  • Website