Tag List Report
The following document contains the listing of user tags found in the code. Below is the summary of the occurrences per tag.
| Tag Class | Total number of occurrences | Tag strings used by tag class |
|---|---|---|
| Deprecated | 0 | @Deprecated |
| Todo Work | 15 | todo, FIXME |
Each tag is detailed below:
Todo Work
Number of occurrences found in the code: 15
| org.apache.shiro.authz.ModularRealmAuthorizerTest | Line |
|---|---|
| no way to unset them, not sure if that is a valid use case, but this is consistent with the PermissionResolver logic // now just to be sure, unset them modRealmAuthz.setRolePermissionResolver( null ); for ( Realm realm : realms ) { assertNull( ((AuthorizingRealm)realm).getRolePermissionResolver() ); } | 79 |
| org.apache.shiro.realm.AuthorizingRealmTest | Line |
| - this could/should be expanded to be more robust end to end test for the AuthorizingRealm | 58 |
| org.apache.shiro.realm.activedirectory.ActiveDirectoryRealmTest | Line |
| While the original incarnation of this test case does not actually test the heart of ActiveDirectoryRealm (no meaningful implementation of queryForLdapAccount, etc.) it obviously should. This version was intended to mimic my current usage scenario in an effort to debug upgrade issues which were not related to LDAP connectivity. | 71 |
| org.apache.shiro.realm.jdbc.JdbcRealm | Line |
| separate password and hash from getPasswordForUser[0] | 243 |
| org.apache.shiro.realm.text.PropertiesRealm | Line |
| - complete JavaDoc | 86 |
| - cleanup - this method shouldn't be necessary | 157 |
| org.apache.shiro.realm.text.TextConfigurationRealm | Line |
| - complete JavaDoc | 53 |
| org.apache.shiro.session.mgt.AbstractSessionManager | Line |
| - deprecate this class (see SHIRO-240): This is only here to make available a common attribute 'globalSessionTimeout' to subclasses, particularly to make it available to both AbstractNativeSessionManager and ServletContainerSessionManager subclass trees. However, the ServletContainerSessionManager implementation does not use this value (see https://issues.apache.org/jira/browse/SHIRO-240 for why). That means that only the Native session managers need a globalSessionTimeout property, making this class unnecessary. | 30 |
| org.apache.shiro.session.mgt.DefaultSessionManager | Line |
| - move SessionDAO up to AbstractValidatingSessionManager? | 45 |
| org.apache.shiro.session.mgt.DelegatingSession | Line |
| - complete JavaDoc | 45 |
| org.apache.shiro.session.mgt.ExecutorServiceSessionValidationScheduler | Line |
| - complete JavaDoc | 40 |
| Implement an integration test to test for jvm exit as part of the standalone example (so we don't have to change the unit test execution model for the core module) | 93 |
| org.apache.shiro.session.mgt.SimpleSession | Line |
| - remove concrete reference to DefaultSessionManager | 100 |
| org.apache.shiro.subject.SimplePrincipalCollection | Line |
| - complete JavaDoc | 54 |
| org.apache.shiro.util.AntPathMatcher | Line |
| - complete JavaDoc | 64 |