|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
To unsubscribe from this list please visit:
Perhaps would it be more productive if we rewrite JVM.canUseSun14ReflectionProvider() such that it actually tests if all the relevant classes and methods are present and usable, as opposed to trying to guess whether Sun14ReflectionProvider can be used from other circumstancial evidence?
The code as it is today does feel like a browser capability detection badly done (i.e., "check if the user agent is IE, and if so I can't use window.dispatchEvent")
I can change Sun14ReflectionProvider constructor so that it calls its own methods with some harmless parameters to check if it's functioning correctly, then all that we have to do is to try to instantiate Sun14ReflectionProvider then fall back to PureJavaReflectionProvider.