Databases
StackOverflow2013
Postsdbo
POGood practice to code partition
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGood practice to code partition
    primarykey
    data
    text
    <p>Example I have a JSF managed bean, and in I have method to create user:</p> <pre><code> public String createNewAccount() { FacesContext context = FacesContext.getCurrentInstance(); Map requestParameterMap = (Map) context.getExternalContext().getRequestParameterMap(); try { String userRole = requestParameterMap.get("userRole").toString(); String active = requestParameterMap.get("active").toString(); Boolean act = Boolean.parseBoolean(active); user.setRole(userRole); user.setActive(act); if ((user.getEmail() != null) &amp;&amp; (userDao.findEmailExist(user.getEmail()))) { sendErrorMessageToUser("A user with the given email address exists in the databasee"); return null; } else { userDao.create(user); } } catch (EJBException e) { sendErrorMessageToUser("Register error"); return null; } return "newAccountCreated"; } </code></pre> <p>I read that JSF managedBean should be only used to navigation, and here my question is whether such doing validation in JSF beanie is correct? Should we create a service layer for example, in which the verification will be accomplished? For example, like this:</p> <pre><code>@Stateless public class UserDao implements UserDaoLocal { @PersistenceContext private EntityManager em; private User user; @Override public void create(User user) { em.persist(user); } @Stateless public class UserDaoService implements UserDaoServiceLocal { @EJB private UserDaoLocal userDao private User user; @Override public String create(User user) { if(findEmailExist(user.email) { return "emailExist"; } else { userDao.create(user); return "create"; } } @Override public boolean findEmailExist(String email) { try { Query q = em.createNamedQuery("User.findByEmail"); q.setParameter("email", email); user = (User) q.getSingleResult(); return true; } catch (Exception e) { System.out.println("Błąd email: " + e.getMessage()); return false; } } </code></pre> <p>and then in jsf bean only have this:</p> <pre><code>public String createNewAccount() { FacesContext context = FacesContext.getCurrentInstance(); Map requestParameterMap = (Map) context.getExternalContext().getRequestParameterMap(); try { String userRole = requestParameterMap.get("userRole").toString(); String active = requestParameterMap.get("active").toString(); Boolean act = Boolean.parseBoolean(active); user.setRole(userRole); user.setActive(act); String result userDaoService.create(user); if (result = "emailExist") { sendErrorMessageToUser("A user with the given email address exists in the database"); return null; } else return result; } } catch (EJBException e) { sendErrorMessageToUser("Error registration"); return null; } } </code></pre> <p>That is a good? What is the best way out to partition code in Java EE?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USThe Nightmare
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COThat's basic MVC architecture. View layer (in your case JSF managed bean) has to do only the job of converting the form into manageable data. Processing such data and DAO access has nothing to do with that layer.
      singulars
      1. POGood practice to code partition
      1. USXtreme Biker
 

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