02-14-2010 07:16 PM - edited 02-14-2010 07:34 PM
I'm posting my minimalistic console-based (pure Java 1.5) tool that lists all code module signatures (signer IDs only) of COD files specified on the command-line. To run the tool, rename the attachment from .txt to .java, compile the .java file using "javac", and then run the resulting .class file using "java".
The reasoning behind this post is that I noticed that many BlackBerry developers don't have the tools to check which signatures their COD files really have.
Ideally, RIM's own Signature Tool would show which signatures COD files really have, but the tool is still broken in this respect. The Signature Tool sometimes shows non-existent signatures, probably by reading the signature list from the .csl and .cso files. This may happen when some signatures were successfully obtained, whereas other signatures could not be obtained.