Databases
StackOverflow2013
Postsdbo
POSpring Portlet MVC: Forward Request parameters to model
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSpring Portlet MVC: Forward Request parameters to model
    primarykey
    data
    text
    <p>I got two views:</p> <ol> <li>Displays some common information about an entity</li> <li>Displays more details about this entity</li> </ol> <p>The second view has a link back to the first one. To create the link I need some informations, lets say two ids ("id1" and "id2"). Theses ids are passed to the controller of the second view by request parameters.</p> <p>To create the back link in the second view, I have to forward the request parameters to the model manualy. This is not very convenient.</p> <p>Is there any approach to do this forwarding automatically?</p> <p>Here an example:</p> <p><strong>Link to details in the first view:</strong></p> <pre><code>&lt;portlet:renderURL var="detailsUrl"&gt; &lt;portlet:param name="action" value="showDetails" /&gt; &lt;portlet:param name="id1" value="${entity.id1}" /&gt; &lt;portlet:param name="id2" value="${entity.id2}"/&gt; &lt;/portlet:renderURL&gt; &lt;a href="${detailsUrl}"&gt;Details&lt;/a&gt; </code></pre> <p><strong>Render method in the second controller:</strong></p> <pre><code>@RenderMapping(params = "action=showDetails") public String showDetails ( @RequestParam("id1") int id1, @RequestParam("id2") int id2, Model model) { // The current unconvenient approach model.addAttribute("id1", id1); model.addAttribute("id2", id2); return "showDetails"; } </code></pre> <p><strong>Back link in the second view:</strong></p> <pre><code>&lt;portlet:renderURL var="entityUrl"&gt; &lt;portlet:param name="action" value="showEntity" /&gt; &lt;portlet:param name="id1" value="${id1}" /&gt; &lt;portlet:param name="id2" value="${id2}"/&gt; &lt;/portlet:renderURL&gt; &lt;a href="${entityUrl}"&gt;Back&lt;/a&gt; </code></pre> <p>I searched the internet for houres to find something like a trick I missed. But the only thing I found was: "Spring dose it automatically for you". But I can't confirme this.</p> <p>Thanks for your help...</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMark Chorley
    1. USscheffield
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSpring Portlet MVC: Forward Request parameters to model
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSpring Portlet MVC: Forward Request parameters to model
      1. USINElutTabile
      1. VTFavorite
    3. VO
      singulars
      1. POSpring Portlet MVC: Forward Request parameters to model
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COIt would be ok for me, if the answer is that it is impossible.
      singulars
      1. POSpring Portlet MVC: Forward Request parameters to model
      1. USscheffield
 

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