[
https://issues.apache.org/jira/browse/PIVOT-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871453#action_12871453
]
Sandro Martini commented on PIVOT-500:
--------------------------------------
Hi Greg,
before to hide (temporary) the signed demos form the page, I'm trying to better
understand where the problem is.
The expiring on the certificate is only a warning, so it' isn't it the problem,
but should be re-generated before the 1.5 release, tell me if you want that I'd
make it.
Can you explain better in which cases it gives you the error ?
I've just tried to execute many JNLP from the pivot-demos.war (just
re-generated from pivot trunk) from a local Tomcat, but all works good in my
environment (and with JRE 6 Update 20, on Windows 7).
I've read something related to the recent change in JRE 6 Update 19 and seems
that should be Web Start to raise problems if there is/there isn't the security
inside jnlp files, or something like this ... too many outdated or partial
docs, I'm trying to see if this could be the problem.
For example, some fresh infos here:
http://forums.sun.com/thread.jspa?threadID=5435627
Let's update soon on this.
Bye
> JNLP demos that use signed JARs fail to launch
> ----------------------------------------------
>
> Key: PIVOT-500
> URL: https://issues.apache.org/jira/browse/PIVOT-500
> Project: Pivot
> Issue Type: Bug
> Components: demos
> Reporter: Greg Brown
> Assignee: Sandro Martini
> Priority: Minor
> Fix For: 1.5
>
>
> The exception in the Web Start console doesn't offer much help:
> java.lang.NullPointerException
> at
> java.util.jar.JarVerifier.mapSignersToCodeSource(JarVerifier.java:497)
> at
> java.util.jar.JarVerifier.mapSignersToCodeSources(JarVerifier.java:509)
> at java.util.jar.JarVerifier.getCodeSources(JarVerifier.java:827)
> at java.util.jar.JarFile.getCodeSources(JarFile.java:622)
> at
> java.util.jar.JavaUtilJarAccessImpl.getCodeSources(JavaUtilJarAccessImpl.java:25)
> at
> com.sun.deploy.cache.DeployCacheJarAccessImpl.getCodeSources(DeployCacheJarAccessImpl.java:60)
> at
> com.sun.javaws.security.SigningInfo.getCommonCodeSignersForJar(SigningInfo.java:382)
> at com.sun.javaws.security.SigningInfo.check(SigningInfo.java:291)
> at
> com.sun.javaws.LaunchDownload.checkSignedResourcesHelper(LaunchDownload.java:1498)
> at
> com.sun.javaws.LaunchDownload.checkSignedResources(LaunchDownload.java:1268)
> at com.sun.javaws.Launcher.prepareResources(Launcher.java:1222)
> at com.sun.javaws.Launcher.prepareAllResources(Launcher.java:624)
> at com.sun.javaws.Launcher.prepareToLaunch(Launcher.java:332)
> at com.sun.javaws.Launcher.prepareToLaunch(Launcher.java:204)
> at com.sun.javaws.Launcher.launch(Launcher.java:121)
> at com.sun.javaws.Main.launchApp(Main.java:418)
> at com.sun.javaws.Main.continueInSecureThread(Main.java:255)
> at com.sun.javaws.Main$1.run(Main.java:115)
> at java.lang.Thread.run(Thread.java:637)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
