diff options
| author | Sven Gothel <[email protected]> | 2014-01-31 07:34:15 +0100 |
|---|---|---|
| committer | Sven Gothel <[email protected]> | 2014-01-31 07:34:15 +0100 |
| commit | 8c3a54316dbd003c1b265f74e6b18eb5fb48eb4b (patch) | |
| tree | 6cebd6c3568c9f0f2878898f54e2994937e631b5 /netx/javax/jnlp/ServiceManager.java | |
| parent | e56a94189aac504b144100fb1962a1a8b05c86af (diff) | |
JNLPClassLoader.createInstance(): Remove extLoader (same as baseLoader); getInstance(): No new JNLPClassLoader if uniqueKey satisfies
JNLPClassLoader.[get|create]Instance(..):
- Reuse uniqueKey, baseLoader from getInstance()
- Remove extLoader (same as baseLoader)
This is odd and sparked my eye while reusing the baseLoader (above).
JNLPClassLoader.getInstance(..):
- No new JNLPClassLoader if uniqueKey satisfies.
Why should we ? Enables reusing CL and impacts performance.
JNLPClassLoader.toString(): Added for better debugging.
Diffstat (limited to 'netx/javax/jnlp/ServiceManager.java')
0 files changed, 0 insertions, 0 deletions