wood burning stoves 2.0*
The moose likes Java in General and the fly likes Invalid signature in jarfile digest -- why now? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Java » Java in General
Bookmark "Invalid signature in jarfile digest -- why now?" Watch "Invalid signature in jarfile digest -- why now?" New topic
Author

Invalid signature in jarfile digest -- why now?

Daniel B. Davis
Greenhorn

Joined: May 11, 2013
Posts: 9
Using Java3d things get cumbersome. There is a repeated error, much mentioned, in which Canvas3D is not found. Everything appears correct, but for me and for others who have encountered it. At first, I tried permuting the sequence of files in the Classpath. This caused a variety of not found errors of things I knew to be there: -- a sure sign that it is not inherent in Canvas3D. None of the suggestions anywhere appeared relevant to me. I did try jiggling around with memory. That caused other messages. As a new approach, I tried within my build unjarring all 3 j3d jar files, and combining them into one with the target code, well-separated by packages. When I did that, I got an unexpected error, and that is what I am writing about: java.lang.SecurityException: Invalid signature file digest for Manifest main attributes
1. Are there limits to the size of .jar files?
2. I never needed to create digests before; why now?
3. Is there a better way to approach the not-found problem?

As always, many thanks.
Henry Wong
author
Sheriff

Joined: Sep 28, 2004
Posts: 18875
    
  40

Daniel B. Davis wrote:Using Java3d things get cumbersome. There is a repeated error, much mentioned, in which Canvas3D is not found. Everything appears correct, but for me and for others who have encountered it. At first, I tried permuting the sequence of files in the Classpath. This caused a variety of not found errors of things I knew to be there: -- a sure sign that it is not inherent in Canvas3D. None of the suggestions anywhere appeared relevant to me. I did try jiggling around with memory. That caused other messages. As a new approach, I tried within my build unjarring all 3 j3d jar files, and combining them into one with the target code, well-separated by packages. When I did that, I got an unexpected error, and that is what I am writing about: java.lang.SecurityException: Invalid signature file digest for Manifest main attributes
1. Are there limits to the size of .jar files?
2. I never needed to create digests before; why now?
3. Is there a better way to approach the not-found problem?

As always, many thanks.



Well, you did unjarred and rejarred three jar files. Are you saying that all three jar files are yours -- and are not signed jar files? Just because you never signed a jar file before, doesn't mean that you haven't been using signed jar files.

Henry


Books: Java Threads, 3rd Edition, Jini in a Nutshell, and Java Gems (contributor)
Daniel B. Davis
Greenhorn

Joined: May 11, 2013
Posts: 9
Thanks Henry, but I have a long-time working application built using Ant which unjars the 3 java3d jar files, then combines them into one large jar file, along with my stuff, and several other things. Are you saying that once a class has been included within a signed jar file, its signature must travel with it? I have also used the unjar/rejar technique in other, less clear-cut settings where the provenance of the jar files are less clear than this. Does it mean that the j3d jars are unsigned? Hence my astonishment at this, seemingly new, requirement.

I have no animus against signing jar files, but in order to do so I would need to invest a chunk of time learning that whole area, an investment I would like to defer, if possible.

Thanks again.
 
GeeCON Prague 2014
 
subject: Invalid signature in jarfile digest -- why now?