-
Enhancement
-
Resolution: Fixed
-
P4
-
7u6
-
Mac OS X
In reviewing RT-20843 Artem questioned why we have duplicate classForName methods in GlassApplication.m and GlassHelper.m. He wrote:
"Right now we have two +SetGlassClassLoader:withEnv and two +ClassForName:withEnv methods: in GlassApplication and GlassHelper. Is it possible to use GlassHelper's functions from GlassApplication code?"
I know of no good reason for the duplicated code. In fact, there is already one place in GlassApplication that is calling GlassHelper.ClassForName, which validates the thinking that we can get rid of the one in GlassApplication in favor of the one in GlassHelper.
"Right now we have two +SetGlassClassLoader:withEnv and two +ClassForName:withEnv methods: in GlassApplication and GlassHelper. Is it possible to use GlassHelper's functions from GlassApplication code?"
I know of no good reason for the duplicated code. In fact, there is already one place in GlassApplication that is calling GlassHelper.ClassForName, which validates the thinking that we can get rid of the one in GlassApplication in favor of the one in GlassHelper.
- is blocked by
-
JDK-8118489 Remove use of ContextClassLoader from Glass
-
- Closed
-