Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Put all fields in its own class, also called an entity or DTO class (e.g. <code>User</code>, <code>Product</code>, <code>Order</code>, etc) and reference it instead. Those can be JDBC/JPA entities. Put all business methods in its own class, also called a service or domain object (e.g. <code>UserService</code>, <code>ProductService</code>, etc) and reference it instead. Those can be EJB's.</p> <p>E.g. thus not</p> <pre><code>public class Bean { private Long id; private String field1; private String field2; private String field3; // Etc... All model fields. @PostConstruct public void init() { // &gt;20 lines of business/domain code to prefill the fields from DB. } public void save() { // &gt;20 lines of business/domain code to save the fields in DB. } // Getters/setters for all fields and possibly also all nested fields. } </code></pre> <p>But more so</p> <pre><code>public class Bean { private Long id; private Entity entity; @EJB private EntityService service; @PostConstruct public void init() { entity = service.find(id); } public void save() { service.save(entity); } // Getter/setter for id and getter for entity. } </code></pre> <p>Further, I've also seen code wherein the nested objects/entities are delegated through by additional getters/setters in the bean like so</p> <pre><code>private Entity entity; public String getField1() { return entity.getField1(); } public void setField1(String field1) { entity.setField1(field1); } // Etc... </code></pre> <p>This is totally unnecessary. Just a single getter for the entity is sufficient (setter is not mandatory!), in combination with</p> <pre class="lang-html prettyprint-override"><code>&lt;h:inputText value="#{bean.entity.field1}" /&gt; </code></pre> <p>The entities at its own can also be further divided. E.g. <code>street</code>, <code>houseNumber</code>, <code>zipCode</code>, <code>city</code>, <code>country</code> of an <code>User</code> could be replaced by another entity/DTO <code>Address</code> within the same <code>User</code>.</p> <hr> <p>If you have bad luck, the code has been autogenerated by a visual editor (e.g. Netbeans + Woodstock). There's not much to refactor anyway without completely redesigning it, I would rather look for another project.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to (or should you) avoid long methods/classes in jsf
      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. POHow to (or should you) avoid long methods/classes in jsf
      singulars
      1. PTQuestion
    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. COUnfortunatly we have none of these :) We use DTO's and service layer, the code is not auto-generated, but has seen lots of changes by lots of developpers. How about dividing independent parts of the view to `<ui:includes/>` and assigning their own beans? Does it become harder to maintain in time?
      singulars
      1. PO
      1. USSelimOber
    2. COYou should use one bean per `<h:form>`. You could use `<ui:include>` to overcome section/field repetition (e.g. combo of 2 fields, label+input+message, etc). You could use `<ui:insert>`/`<ui:define>` to overcome template repetition (e.g. header/menu/footer).
      singulars
      1. PO
      1. USBalusC
 

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