JDK-6312808 : NullPointerException while trying to import a "component extension"
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 6
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2005-08-18
  • Updated: 2010-09-29
  • Resolved: 2005-09-14
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6 b52Fixed
Related Reports
Relates :  
JDK-6343024 - NullPointerException while trying to launch/import a "component extension"
Description
This works fine with jre1.6.0 build 47, but failed with b48PIT

Steps to reproduce :
--------------------
1. Install mustang JRE b48PIT from http://j2se.east/arc/1.6.0/pit/2005-08-16/windows-i586/
(jre-6_0-fcs-bin-b99-windows-i586-16_aug_2005.exe)
2. Clear cache using javaws -uninstall 
3. Import a jnlp with <component-desc/> element using command ,
javaws -import http://sceri.prc/~yl153753/cacheViewer/CacheViewer_Library.jnlp

It will throw the following exception :
java.lang.NullPointerException
	at com.sun.javaws.Launcher.prepareLaunchFile(Unknown Source)
	at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
	at com.sun.javaws.Launcher.launch(Unknown Source)
	at com.sun.javaws.Main.launchApp(Unknown Source)
	at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
	at com.sun.javaws.Main$1.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
And the console shows error :
----------------------------------------------------
#### Java Web Start Error:
#### null
Comments
EVALUATION Although importing an extension is not really a supported feature, it should not throw a null poiunter exception. In tiger this worked if it were an unversioned component extension, and there is no reason not to allow the same extensions to be directly importable in mustang. An extension can be versioned, in which case only the refering jnlp files specifies the version, so a versioned extension should not be directly importable. All extensions, including installer extensions, should be indirectly importable, by importing the application that uses them.
19-08-2005