Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p><em>.. and redirects to the same JSP page ..</em></p> </blockquote> <p>You shouldn't fire a redirect here, but a <strong>forward</strong>. I.e. do not do</p> <pre><code>response.sendRedirect("page.jsp"); </code></pre> <p>but rather do</p> <pre><code>request.getRequestDispatcher("page.jsp").forward(request, response); </code></pre> <p>This way the original request remains alive, including all the parameters and attributes. A redirect namely instructs the client to fire a <strong>brand new</strong> request, hereby garbaging the initial request.</p> <p>In JSP you can access request parameters by <code>${param}</code> in EL and you can access request attributes the same way with <code>${attributeKey}</code> where <code>attributeKey</code> is the attribute key which you've used to set the object in the request scope in the servlet as follows:</p> <pre><code>request.setAttribute("attributeKey", someObject); </code></pre> <p>As to retaining HTML input values in a JSP, you just need to set the <code>&lt;input&gt;</code> element's <code>value</code> attribtue accordingly with the request parameter value:</p> <pre><code>&lt;input name="foo" value="${param.foo}"&gt; </code></pre> <p>This prints the outcome of <code>request.getParameter("foo")</code> in template text. This has however a <a href="http://en.wikipedia.org/wiki/Cross-site_scripting" rel="nofollow noreferrer">XSS</a> risk, better is to escape any user-controlled input with help of JSTL's <code>fn:escapeXml()</code> as follows:</p> <pre><code>&lt;%@ taglib uri="http://java.sun.com/jsp/jstl/functions" prefix="fn" %&gt; ... &lt;input name="foo" value="${fn:escapeXml(param.foo)}"&gt; </code></pre> <p>Retaining the selected option in a dropdown is a bit different story. You basically need to set the <code>selected</code> attribute of the <code>&lt;option&gt;</code> element in question. Assuming that you're -as one usually would do- using JSTL's <code>&lt;c:forEach&gt;</code> tag to display a <code>Map&lt;String, String&gt;</code> or maybe a <code>List&lt;JavaBean&gt;</code> of option values, you can solve it as follows (assuming <code>${countries}</code> is a <code>Map&lt;String, String&gt;</code> which you've placed as an attribute in the request, session or application scope):</p> <pre><code>&lt;select name="country"&gt; &lt;c:forEach items="${countries}" var="country"&gt; &lt;option value="${country.key}" ${country.key == param.country ? 'selected' : ''}&gt;${country.value}&lt;/option&gt; &lt;/c:forEach&gt; &lt;/select&gt; </code></pre> <p>This prints the <code>selected</code> attribute when the currently iterated option key equals the submitted one in the request parameter map.</p>
    singulars
    1. This table or related slice is empty.
    1. POSet request attributes when a Form is POSTed
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBalusC
    1. USBalusC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI forgot to mention that I am already doing a `rd.forward(request, response)`. But what's confounding me right now is that after the forward() the JSP's dropdown lists are empty - and I can see in Netbeans' HTTP monitor that the request attributes that contained the data used to populate the dropdown lists are no longer present after the forward() completes. I am missing sth!
      singulars
      1. PO
      1. USssahmed555
    2. COHuh, HTTP monitor? Aren't you confusing request attributes with request parameters? Attributes are not visible in HTTP request/response header/body, but only in server's memory. Request parameters are visible in HTTP request/response header/body. You'll really need to provide more detail about the problem. Regardless, didn't the remnant of my answer bring new insights?
      singulars
      1. PO
      1. USBalusC
    3. CONo, but NB's HTTP monitor is able to debug the HTTP request & response traffic between the various components in a web app, and it does show both request parameters and request attributes - when available.
      singulars
      1. PO
      1. USssahmed555
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload