Sets a newline (\n) delimited string that defines role-to-permission definitions.
<p/>
<p>Each line within the string must define a role-to-permission(s) key/value mapping with the
equals character signifies the key/value separation, like so:</p>
<p/>
<p><code><em>rolename</em> = <em>permissionDefinition1</em>, <em>permissionDefinition2</em>, ...</code></p>
<p/>
<p>where <em>permissionDefinition</em> is an arbitrary string, but must people will want to use
Strings that conform to the {@link hunt.shiro.authz.permission.WildcardPermission WildcardPermission}
format for ease of use and flexibility. Note that if an individual <em>permissionDefinition</em> needs to
be internally comma-delimited (e.g. <code>printer:5thFloor:print,info</code>), you will need to surround that
definition with double quotes (") to avoid parsing errors (e.g.
<code>"printer:5thFloor:print,info"</code>).
<p/>
<p><b>NOTE:</b> if you have roles that don't require permission associations, don't include them in this
definition - just defining the role name in the {@link #setUserDefinitions(string) userDefinitions} is
enough to create the role if it does not yet exist. This property is really only for configuring realms that
have one or more assigned Permission.
@param roleDefinitions the role definitions to be parsed at initialization
Sets a newline (\n) delimited string that defines role-to-permission definitions. <p/> <p>Each line within the string must define a role-to-permission(s) key/value mapping with the equals character signifies the key/value separation, like so:</p> <p/> <p><code><em>rolename</em> = <em>permissionDefinition1</em>, <em>permissionDefinition2</em>, ...</code></p> <p/> <p>where <em>permissionDefinition</em> is an arbitrary string, but must people will want to use Strings that conform to the {@link hunt.shiro.authz.permission.WildcardPermission WildcardPermission} format for ease of use and flexibility. Note that if an individual <em>permissionDefinition</em> needs to be internally comma-delimited (e.g. <code>printer:5thFloor:print,info</code>), you will need to surround that definition with double quotes (") to avoid parsing errors (e.g. <code>"printer:5thFloor:print,info"</code>). <p/> <p><b>NOTE:</b> if you have roles that don't require permission associations, don't include them in this definition - just defining the role name in the {@link #setUserDefinitions(string) userDefinitions} is enough to create the role if it does not yet exist. This property is really only for configuring realms that have one or more assigned Permission.
@param roleDefinitions the role definitions to be parsed at initialization