• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

7u45 java update broke my webstart deployment

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
After users apply Java 7u45 update, webstart deployment of my JavaSE application throws exception:
'Unable to launch the application' with this exception: ' java.lang.SecurityException: com.sun.deploy.net.JARSigningException: Found unsigned entry in resource: ....'
Can anyone help me with this ? Thank you in advance !
 
Ranch Hand
Posts: 64
Netbeans IDE Linux Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Without more details or being able to look at the actual trouble jars I can only guess.

A lot of people are having trouble with 1.7's update 45 with web start. Some of the things causing trouble include:

  • JNLP-INF/APPLICATION-TEMPLATE signing
  • Using the versioning protocol breaks attributes


  • Check the release notes to see if you're running into known issues:

    http://www.oracle.com/technetwork/java/javase/7u45-relnotes-2016950.html

    I've seen this error for a different reason. I build a project that has a common library I try to reference as an extension resource. Unfortunately my build process also pulls the same library in under lib/ and references it in the main jar's manifest. The library jar is built and signed twice and for some reason is slightly different in size. This trips up the javaws loader with errors about signatures. That was hard to sort out because I would look at the extension jar and test it's signature and it was fine, yet it's name was appearing as the one being unsigned.
     
    Consider Paul's rocket mass heater.
    reply
      Bookmark Topic Watch Topic
    • New Topic