BlackBerry : How to OTA Install my RIM signed .cod file on the handset ?

Question

Blackberry :
I am using phone book access in my project.
I created the .cod file using rapc and signed it online using signatureTool and RIM provided key.
I am able to install this RIM signed .cod file of my project to the handset BlackBerry 7100G using usb cable and .alx file
with Desktop Manager. It works perfect.
I have already set the mime type for .cod on my server.And put the signed .cod, .jar and .jad files. With my wap page having
link to the jad file.
When I open this wap page from my Black Berry 7100G Browser and clik on the link, I see the details of my application. Then I
press download, it starts the download but then gives error in JAD.
For the project version without PIM, where no signature is required I am able to download it OTA on the handset using the
.jad & .jar file only.
Issues that I feel are creating this problem.(I am using JDE 4.0.2)
1) RAPC.exe added RIM specific attributes to jad file that shows project.cod & project-1.cod with different byte sizes and
different SHA-1 codes.
But in the bin directory, after runing rapc over the jad & jar file I get only project.cod with size almost same as the
sum of project.cod & project-1.cod and project-1.cod is not found.
2) RAPC adds the SHA-1 code & byte size to jad file. But when I use SigntureTool to sign the .cod file its size is changed
but the jad file is not updated by it.
Thank you,
Amitabh

Answer 1

Since my last post I have been discussing this issue with commercial application developers and have been experimenting with various applications.
Firstly, let's make the JAR/JAD situation absolutely clear. Some, but not all, applications unquestionably require the JAD file as a part of the installation process. If the application is a "signed" application then the security authorisation is contained within the JAD file, not the JAR file. The JAD file is created from the JAR file and contains security verification information that is separate from the JAR file and which enables the application to signed as kosher.
The Nokia PC Suite Application Installer does not need to show you the JAD file. The JAR file is sufficient. If you install the application from a folder on your PC that contains both the matching JAR and JAD files then Application Installer will correctly install the application from both the JAR and JAD files. If the folder ONLY contains the JAR file then it will only install from the JAR file. I have proved this.
So, if you cannot get the application to work then the reason is not the installation process. The reason is far more likely to be that you are trying to install the application on a branded handset rather than on a standard Nokia handset. Some service providers heavily modify the base standard software that Nokia installs on its vanilla handsets and these modifications may well include changes to security authorisation rules that will prevent many applications working on handsets that they sell.
I am in dispute with one such as we speak. I will not name them right now but if I am unable to achieve a satisfactory outcome then be assured I will let EVERYONE know. Thank God for YouTube.