06-20-2012 07:46 AM
We provide our application as a midlet for older BB devices (< OS 5). The application is larger than 256 KB. Now if a user tries to download it, he gets 413 Entity too large. I know, the BES setting "Maximum KB/Connection" can be set to a higher value, but we must tell this every customer. Is there any chance to somehow split the midlet or another solution to get around the 256 KB limit?
06-22-2012 04:24 PM
There is a solution, and it's right here:
06-25-2012 04:24 AM
I don't see how this article solves my problem with installing a java MIDLET which exceeds the maximum size. I have a jar and a jad file not a COD file. And I see no chance in splitting the jar.
06-25-2012 05:01 AM
It is done in Eclipse via Maven.
For old BB devices we provide a java midlet, which we also provide for JavaME devices. BB devices run normal midlets, you don't need a cod file.The project we build is not a BB project, but a standard javaME project. The BB SDK isn't even installed on the machine.
For more recent BB devices (OS 5+) we also provide a BB app (COD file), and the article above probably works in that case. But I need a solution for midlets.
06-25-2012 11:12 AM
You can compile MIDlets into COD files and that will resolve this issue. The device can convert a JAR file into a COD file once downloaded, but it appears that this JAR file is too large.