title: Scope of a Spring-Controller and its instance-variables
body: <p>Are all controllers in Spring-MVC singletons and are shared among different sessions and requests?</p>
  
  <p>If so, I assume that a class-variable like</p>
  
  <pre><code>public String name;
  </code></pre>
  
  <p>would be the same for all requests and sessions? So that if User X makes a request and <code>name</code> is being set to <em>Paul</em>, User Z also has Paul as attribute?</p>
  
  <p>In my case I do NOT want that behaviour but wondered if there is a more easier, or more cleaner OOP-way to have session/request-variables then <code>session.getAttribute()</code>/<code>request.getAttribute()</code></p>