It’s a Dangerous World: Adding Security - Stripes...and Java Web Development is Fun Again - page 310

public void init() {
if (roleDao.read().isEmpty()) {
roleDao.save( new Role("User"));
roleDao.save( new Role("Administrator"));
roleDao.commit();
}
}
}
Stripersist finds StripersistInit implementations through the extension
packages mechanism or with the StripersistInit.Classes initialization para-
meter to StripesFilter in web.xml .
Next, we'll add a roles property to the User class. Users can have more
than one role, and more than one user can have the same role, so it's a
many-to-many relationship:
Download email_35/src/stripesbook/model/User.java
package stripesbook.model;
@Entity
public class User extends ModelBase {
private String firstName;
private String lastName;
private String username;
private String password;
@ManyToMany
private List<Role> roles;
/ * getters and setters... * /
@Override
public String toString() {
return String.format("%s %s", firstName, lastName);
}
}
The roles are ready to go.
A Page with Restricted Access
To manage assigning roles to users and demonstrate the use of roles
at the same time, let's add a User List page, as shown in Figure 14.1 ,
on the following page. The page shows the users with their roles and
allows us to change which users have which roles. Only administrators
are allowed to use this page. The application loads an administrator as
a starting point; when users register, they are initially given the User
role.