You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Bryant Luk (JIRA)" <ji...@apache.org> on 2010/04/17 22:48:25 UTC
[jira] Resolved: (WINK-228) sweep code for java2security
compatibility
[ https://issues.apache.org/jira/browse/WINK-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryant Luk resolved WINK-228.
-----------------------------
Assignee: Mike Rheinheimer
Resolution: Fixed
I think we have added our own ClassUtils. Jesse and I've run a few test runs with Java 2 Security enabled and didn't find anything. The issue was fixed by you Mike so I'm going to clean this up.
> sweep code for java2security compatibility
> ------------------------------------------
>
> Key: WINK-228
> URL: https://issues.apache.org/jira/browse/WINK-228
> Project: Wink
> Issue Type: Improvement
> Affects Versions: 1.1
> Reporter: Mike Rheinheimer
> Assignee: Mike Rheinheimer
> Fix For: 1.1
>
>
> Was just thinking about the problems java2security may introduce regarding WINK-226 and WINK-227. The places fixed in these two Jiras probably need to be wrapped in doPrivs.
> Perhaps we'd be better off having our own ClassUtils implementation so we can manage the loadClass utility method
> {code}
> doPriv {
> try {
> use thread context classloader to load class
> } catch (ClassNotFoundException cnfe) {
> use system classloader to load class
> }
> }
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira