Group items matching

in title, tags, annotations or url

Git Plugin — This plugin allows use of Git as a build SCM

Subversion Plugin — This plugin adds the Subversion support (via SVNKit) to Jenkins

Subversion Release Manager — This plugin allows you to set up a job in Hudson for building specific revisions of a project.

PermissionResolver

use the PermissionResolver to convert the string into a Permission instance, and perform the check that way

All Shiro Realm implementations default to an internal

Mapping enum to database column using JPA/Hibernate You can use any of the 3 approaches discussed above. Map the enum to an integer column. The persistence implementation should automatically convert enum to ordinal() and back for you. Map the enum to a String column. The persistence implementation should automatically convert the enum value to String value via the name() function. Map the enum using a business value. You should mark the enum field as @Transient, and create another String field which you can map to a String column in your database table. Here’s an example code snippet. view plaincopy to clipboardprint?@Entity  public class Product {   @Column   private String colorValue;     @Transient   public Color getColor() {    return Color.fromValue(colorValue);   }     public void setColor(Color color) {    this.colorValue = color.toValue();   }  }  

Approach 3: Using a user defined business value – Recommended approach! This approach involves assigning a an explicit user defined value to each enum constant and defining a toValue() and fromValue() methods on the enum to do the serialization and deserialization.

public enum Color {   RED("RED"), GREEN("GREEN"), BLUE("BLUE"), UNKNOWN("UNKNOWN");     private final String value;     Color(String value) {     this.value = value;   }     public static Color fromValue(String value) {     if (value != null) {       for (Color color : values()) {         if (color.value.equals(value)) {           return color;         }       }     }       // you may return a default value     return getDefault();     // or throw an exception     // throw new IllegalArgumentException("Invalid color: " + value);   }     public String toValue() {     return value;   }     public static Color getDefault() {     return UNKNOWN;   }  }  public enum Color { RED("RED"), GREEN("GREEN"), BLUE("BLUE"), UNKNOWN("UNKNOWN"); private final String value; Color(String value) { this.value = value; } public static Color fromValue(String value) { if (value != null) { for (Color color : values()) { if (color.value.equals(value)) { return color; } } } // you may return a default value return getDefault(); // or throw an exception // throw new IllegalArgumentException("Invalid color: " + value); } public String toValue() { return value; } public static Color getDefault() { return UNKNOWN; } } This approach is better than approach 1 and approach 2 above. It neither depends on the order in which the enum constants are declared nor on the constant names.

A proper way for JPA entities instantiation

creating the entities I would like to focus in this post

JPA2.0 entities

AllPermission

always implies any other permission

implies method

RolePermissionResolver

resolves a String value and converts it into a Collection of Permission instances

 Collection<Permission> resolvePermissionsInRole(String roleString)

invariants

customer's last name must not be null

must be between 3 and 80 characters long

can cluster Subject sessions natively and never need to worry again about how to cluster sessions based on your container environment

if you configure a cluster-capable SessionDAO, the DAO can interact with a clustering mechanism and Shiro's SessionManager never needs to know about clustering concerns

Serializing between ActionScript and Java

java.util.Date (formatted for Coordinated Universal Time (UTC))

FindBugs, a program which uses static analysis to look for bugs in Java code

Maven http://mojo.codehaus.org/findbugs-maven-plugin/

Netbeans SQE: Software Quality Environment

first token is the

second token is the

A Permission represents the ability to perform an action or access a resource. A Permission is the most granular, or atomic, unit in a system's security policy and is the cornerstone upon which fine-grained security models are built.

a Permission instance only represents functionality or access - it does not grant it

permissions are immutable and reflect an application's raw functionality

used as a base class for JPA/Hibernate persisted permissions that wish to store the parts of the permission string in separate columns (e.g. 'domain', 'actions' and 'targets' columns)

«Boundary»

Boundary is a stereotyped class or object that represents some system boundary

«Control»

If your application's authentication process is username/password based (like most), instead of implementing this interface yourself, take a look at the UsernamePasswordToken class, as it is probably sufficient for your needs.

UsernamePasswordToken

HostAuthenticationToken interface to retain the host name or IP address location from where the authentication attempt is occuring.

A simple username/password authentication token to support the most widely-used authentication mechanism

JdbcRealm

Realm that allows authentication and authorization via JDBC calls

this class can be subclassed and the appropriate methods overridden. (usually doGetAuthenticationInfo(org.apache.shiro.authc.AuthenticationToken), getRoleNamesForUser(java.sql.Connection,String), and/or getPermissions(java.sql.Connection,String,java.util.Collection)

AuthorizationInfo

represents a single Subject's stored authorization data (roles, permissions, etc)

Roles are represented as a Collection of Strings