To get the BES to push it as an update you have to increment the version number in the ALX file. I don't know what changing the file names would do to a BES push, never tried it, but file names are largely irrelevant for an OTA load since they are really just a location reference for the web server.
For what it is worth what I've noticed:
OTA: displays version data from the JAD file, but uses the version data from the COD file
DM: displays the version data from the ALX file, but seems to only worry about the version data from the COD file
BES: display and uses the version data from the ALX file
Kind of makes sense if you think about it. OTA only worries about one COD file (or group of associated files). The DM may have to deal with multiple CODs in a package (for multiple versions of devices) but is only dealing with one device at a time. The BES has to handle multiple devices of probably multiple versions.
I've gone through many compile/load cycles with my dev hardware only to load the new package on the BES, having forgotten to increment the ALX version, and wait for hours until smacking my forehead and fixing it.
__________________
My other Blackberry is a PlayBook.
Last edited by hrbuckley; 10-14-2009 at 03:07 PM..
|