None of the app spaces are simple to get out there, but even with BlackBerry’s post-to-web-server method, there are few things I to remember:
Prerequisites:
- Make sure that you’ve enabled the right API signing in Project > Configure BlackBerry Project > Code Signing
- Make sure that you have requested and installed your signing keys
- Configure your web server MIME types for .jad and .cod extension
Each time you update:
- Build the Project in eclipse e-JDE
- Preverify? I haven’t yet got all the paths figured out for that.
- Double click on the .cod file in the root of the project folder (make sure the .csl file with the same name is in the same folder)
- Click on one of the ‘Needs signing’ items (if any) and click ‘Request’ to sign the .cod
- Copy the .cod and .jad to a folder, like ‘deploy’
- Change the .cod extension to .zip and try to unzip
- If it doesn’t unzip (it’s not a zip) rename back to .cod (for only small projects)
- If it does unzip, delete the zip file
- Push all the files up to the web server (with, e.g. scp)
Note 1: If you can’t get the signing tool to sign your .cod and you installed both JDE and e-JDE (for eclipse) then check your file associations. Likely it’s pulling the JDE version (because you installed it later). Change the association to the SigningTool.jar file located in the components/bin folder of the JDE plug-in version that you are building for (e.g. 4.5.0).
Note 2: I really need an ant deployment script to take care of this.
Jeremy Wadsack 