[
https://issues.apache.org/jira/browse/SHIRO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420265#comment-13420265
]
Ludovic Garcia commented on SHIRO-378:
--------------------------------------
I'm just Shiro for a short time, but in my case, the classpath resource is a
properties file. I already did something to get around this limitation, but
currently it's not proper.
Actually i extended ClassUtils and added a methods, similar as
getResourceAsStream() which returns class loader's getResource results instead
of ClassLoaderAdvisor.getResourceAsStream().
Then, as for me the returned URL is pointing to a file, I instantiate a file
using this path to my file.
I don't know if you consider this correct with shiro's way of reloading.
If you're interested in, I'll put the code (after proper refactoring).
> PropertiesRealm able to reload Classpath properties files
> ---------------------------------------------------------
>
> Key: SHIRO-378
> URL: https://issues.apache.org/jira/browse/SHIRO-378
> Project: Shiro
> Issue Type: New Feature
> Components: Realms
> Affects Versions: 1.2.0
> Environment: Windows 7 x64, Apache Tomcat 6.0.35, JDK 1.6.0_31 X64
> Reporter: Ludovic Garcia
> Priority: Minor
>
> When deploying a project using shiro on Tomcat, users.properties file could
> be referenced as classpath files, with condition in
> PropertiesRealm.afterRoleCacheSet() at line 166, automatic file reloading is
> impossible.
> if (this.resourcePath.startsWith(ResourceUtils.FILE_PREFIX) && scheduler !=
> null) {
> startReloadThread();
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
