| commit | de3df8699f3dc6d076493c02cd832e0052d05c8b | [log] [tgz] |
|---|---|---|
| author | Welton Rodrigo Torres Nascimento <rodrigo@familianascimento.org> | Mon May 17 21:57:30 2021 -0300 |
| committer | GitHub <noreply@github.com> | Mon May 17 21:57:30 2021 -0300 |
| tree | a85ea1c1d49645e2c040f551a15889fa06add58e | |
| parent | 5354e1ab31dfdbbe4f2910b7cf300d873d9cda8b [diff] |
Update `CommonsInterpolator` doc to reflect actual behavior The stated behavior is not the observed. This is a complement to: https://github.com/apache/shiro-site/pull/82 The relevant section of the commons-configuration class is: > After an instance has been created *it does not contain any Lookup objects*. The current set of lookup objects can be modified using the registerLookup() and deregisterLookup() methods. *Default lookup objects (that are invoked for variables without a prefix)* can be added or removed with the addDefaultLookup() and removeDefaultLookup() methods respectively. (When a ConfigurationInterpolator instance is created by a configuration object, a default lookup object is added pointing to the configuration itself, so that variables are resolved using the configuration's properties.) So, the correct behavior is that you can use `${const:java.awt.event.KeyEvent.VK_ENTER}` but not `${env:EDITOR}`. The current code accepts `${EDITOR}`. If a system property with this name is found not null, it is used, if not, an environment variable is search and if not, the whole substitution `${EDITOR}` is returned.
Apache Shiro is a powerful and easy-to-use Java security framework that performs authentication, authorization, cryptography, and session management. With Shiro’s easy-to-understand API, you can quickly and easily secure any application – from the smallest mobile applications to the largest web and enterprise applications.