title: Attributes naming convention resulting in long EL expressions in JSP Page
body: <p>I'm writing lot of JSP pages for different views. Those JSP retrieve request scope attributes which have very long names to prevent overlapping. An example is:</p>
  
  <pre><code>request.getAttribute("domain1.subdomain1.subdomain11.subdomain111.attributeName");
  </code></pre>
  
  <p>Equivalent in EL would be:</p>
  
  <pre><code>${requestScope['domain1.subdomain1.subdomain11.subdomain111.attributeName']}
  </code></pre>
  
  <p>Sometimes, my EL expressions are very long (for example when I use 3 different JavaBeans to create an HTML tag or call javascript function).</p>
  
  <p>My question is about whether or not the solution I found is a good programming solution. Given the fact that each view has it's own page scope, at the beginning of my JSP, I want to put</p>
  
  <pre><code>&lt;c:set var="attributeName" scope="page" value="${requestScope['domain1.subdomain1.subdomain11.subdomain111.attributeName']}"
  </code></pre>
  
  <p>And then in my EL expressions, I will use</p>
  
  <pre><code>${pageScope["attributeName"]}
  </code></pre>
  
  <p>Isn't this going to create confusion about the actual scope of the attribute when reading the JSP code?</p>