Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You don't need to. It makes in well designed webapps no sense. The servletcontainer does already the session management. Just put the logged-in user in the session scope.</p> <pre><code>@ManagedBean @RequestScoped public class LoginController { private String username; private String password; @EJB private UserService userService; public String login() { User user = userService.find(username, password); FacesContext context = FacesContext.getCurrentInstance(); if (user == null) { context.addMessage(null, new FacesMessage("Unknown login, try again")); username = null; password = null; return null; } else { context.getExternalContext().getSessionMap().put("user", user); return "userhome?faces-redirect=true"; } } public String logout() { FacesContext.getCurrentInstance().getExternalContext().invalidateSession(); return "index?faces-redirect=true"; } // ... } </code></pre> <p>The logged-in user will be available as <code>#{user}</code> in all pages throughout the same session and also in <code>@ManagedProperty</code> of other beans.</p> <p>On logout, however, it makes more sense to invalidate the session. This will trash all session scoped beans as well. You can use <a href="http://download.oracle.com/javaee/6/api/javax/faces/context/ExternalContext.html#invalidateSession%28%29" rel="nofollow noreferrer"><code>ExternalContext#invalidateSession()</code></a> for this.</p> <pre><code> public String logout() { FacesContext.getCurrentInstance().getExternalContext().invalidateSession(); return "index?faces-redirect=true"; } </code></pre> <h3>See also:</h3> <ul> <li><a href="https://stackoverflow.com/questions/3106452/how-do-servlets-work-instantiation-shared-variables-and-multithreading/">How do servlets work? Instantiation, sessions, shared variables and multithreading</a></li> <li><a href="https://stackoverflow.com/questions/9965708/how-to-handle-authentication-authorization-with-users-in-a-database">How to handle authentication/authorization with users in a database?</a></li> <li><a href="https://stackoverflow.com/questions/7031885/how-to-choose-the-right-bean-scope/">How to choose the right bean scope?</a></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POHow can I create a new session with a new User login on the application?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USBalusC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow can I create a new session with a new User login on the application?
      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. VTAcceptedByOriginator
    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 would definitely invalidate the session. The reason is a little bit contrived, but it covers a theoretical security issue: The old user can note the session id while logged in. Then, when the new user logs in, the old user can use the existing session id (e.g. on a second computer) to work in the session of the new user.
      singulars
      1. PO
      1. USChris Lercher
    2. CO@Chris: sessions (read: cookies) are not shared among computers. You're probably confusing with [session fixation](http://en.wikipedia.org/wiki/Session_fixation) hacks when a session ID has been leaked by bug/mistake/accident. Invalidating the session helps very little to nothing against. When the user is logged out, there's already no user in the session and nothing can be taken over :) Invalidating the session is however a good practice to do a "quick cleanup" of memory resources.
      singulars
      1. PO
      1. USBalusC
    3. CO@BalusC: You're setting a new user in the current session (without invalidate). The session information is (typically) held in a cookie in the browser. Copy the sessionId in that cookie into a new browser e.g on a different machine, and the session *will* be shared between the two computers (I've tested this).
      singulars
      1. PO
      1. USChris Lercher
 

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