This discussion is archived
2 Replies Latest reply: Nov 6, 2013 5:22 AM by matbroughty RSS

Threat of jnlp app startup failure in future java release

Greg Stavenow Newbie
Currently Being Moderated

I am the developer of a java jnlp app and have just upgraded to 1.7.0_45.  Web start is now threatening to block my app from starting in a future release because my jar file is missing the Permissions manifest attribute.


It is easy enough to add the attribute to my main jar, where I get confused is with 3rd party jars.  For example, my application makes use of about a dozen libraries, one of which is commons-logging-1.0.4.jar.  I can see many warnings related to this in the java console.  To prevent the warning (and threatened blockage) do I need to alter all of my 3rd party jars?  Is it enough to just add the permission to my main jar?


  • Correct Answers - 10 points
  • Helpful Answers - 5 points