09-20-2012 02:48 AM
I have a java app I distribute through App World that needs to make an https connection. Like many, I have struggled to automatically detect the proper network gateway and settings for making a connection on my clients devices. My latest code works pretty well across many devices, I use ConnectionFactory, on the first attempt it tries with a preferred transport order of mds, bis, wifi, carrier tcp, wap2. If that fails it falls back and reattempts a connection using a connection factory with just wifi and carrier tcp. In all cases my factories use requireendtoend=true, which seems to be required for some MDS and BIS connections.
While my above strategy seems to work pretty well, I've still found a client where it fails. For this client the ConnectionFactory always returns null for any transport method. I know the client is on the network because they can email me from their BlackBerry! The only way I can reproduce this type of behavior is to deny all connections in the application permissions, but that results in the device throwing up a permissions dialog whenever the app tries to make a connection, and my client doesn't see these errors.
I'm not a BES expert, so can anyone tell me whether a BES administrator can set a policy that would make a java app run this way? It's very odd since the user was obviously able to use App World and download my App, so clearly the device is connected to a network and some Apps are able to make network connections.
09-20-2012 05:30 AM
09-20-2012 11:59 PM