Databases
StackOverflow2013
Postsdbo
POEasy way of populating Javabeans based on request parameters
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEasy way of populating Javabeans based on request parameters
    primarykey
    data
    text
    <p>I have a simple person class:</p> <pre><code>package simpleApp.entities; public class Person { private String name; private String secondname; public void setSecondname(String cognome) { this.secondname = cognome; } public String getSecondname() { return secondname; } public void setName(String nome) { this.name = nome; } public String getName() { return name; } } </code></pre> <p>and a simple html page:</p> <pre><code>&lt;html&gt; &lt;body&gt; &lt;form action="/simpleApp/person/" method="POST"&gt; name: &lt;input type="text" name="name"&gt;&lt;br&gt; second name: &lt;input type="text" name="secondname"&gt;&lt;br&gt; &lt;input type="submit"&gt; &lt;/form&gt; &lt;/body&gt; &lt;/html&gt; </code></pre> <p>and a simple servlet:</p> <pre><code>public class Person extends HttpServlet { private static final long serialVersionUID = 1L; public Person() { } protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { } protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { //LOOK HERE: simpleApp.entities.Person p = new simpleApp.entities.Person(); p.setName(request.getParameterValues("name")[0]); p.setSecondname(request.getParameterValues("secondname")[0]); response.sendRedirect("/simpleApp/index.html"); } } </code></pre> <p>Is there a way to automate the parameter setting?</p> <p>Something magic like</p> <pre><code> protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { simpleApp.entities.Person p = new simpleApp.entities.Person(); Magic.justSetEverything(p, request); // NOT NEEDED ANYMORE!!! MUAHAHAHA more time for coffee // p.setName(request.getParameterValues("name")[0]); // p.setSecondname(request.getParameterValues("secondname")[0]); response.sendRedirect("/simpleApp/index.html"); } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBalusC
    1. USSimon
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTDuplicate
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POEasy way of populating Javabeans based on request parameters
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POEasy way of populating Javabeans based on request parameters
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POEasy way of populating Javabeans based on request parameters
      1. USTiny
      1. VTFavorite
    1. COThis could certainly be done through the reflection API, but the question is if it's not more trouble than it's worth, unless you encounter this situation very often or have an enormous number of attributes to set. Also keep in mind that you probably want to do some validation ("was the parameter given?" "is the value valid for this field?")
      singulars
      1. POEasy way of populating Javabeans based on request parameters
      1. USjohusman
    2. COFor your sanity, rename your servlet to `PersonServlet` or something.
      singulars
      1. POEasy way of populating Javabeans based on request parameters
      1. USJeremy
    3. COThanks johusman, I was hoping there is already something. The validation and other logic is done later on on the instance of the class.
      singulars
      1. POEasy way of populating Javabeans based on request parameters
      1. USSimon
 

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