Java Development

[redpath]

I have a JAD file and signed COD file for deployment from a Blackberry Browser access; working fine from our

website.

I want to have multiple JAD files of which each has one application property value changed in it which will enable

the customer to preconfigure the host depending on which link they select from their Blackbery Browser to install.

For example we can have a web page which has three links in a table, the table says which server has been

configured for each link. Underneath is simply a different JAD file which points to the same signed COD file.

I thought this would work fine. But the application property is the one that was built into the COD file when

you use a JAR and JAD to build the COD. I removed the property when building the COD from the JAD and JAR

build process assuming the link for deployment (JAD) would be used. But of course it does not exist.

I thought this would be a great deployment mechanism for the Blackberry app as it is a great deployment mechanism

for JAR and JAD files on nokia devices, simply change the jad and each user can have a different configuration.

Having a customer build a COD for each configuration that is signed using a different JAD is a bit much to ask for.

So is there a solution? Em I missing something?

richard redpath 

[MSohm]

Reading attributes from a jad file added after an appliation has been built is supported in BlackBerry handheld software version 4.3 and higher.  Please see the developer knowledge base below for more information.

How To - Programmatically read the attributes of a JAD file
Article Number: DB-00638

http://www.blackberry.com/knowledgecenterpublic/livelink.exe/fetch/2000/348583/800708/800646/How_To_...

[bzubert]

This subject was also discussed in a previous forum post:

http://supportforums.blackberry.com/rim/board/message?board.id=java_dev&message.id=10

[redpath]

Okay will give it a try, I guess if I have app.COD at the website with red.jad and blue.jad which references the app.COD,

the statement below

    String moduleName = ApplicationDescriptor.currentApplicationDescriptor().getModuleName();

 will get the JAD file that was used to install the app.COD file from deployment from a website, then I can use the functions you stated in JDE 3.0 which I see CodeModuleGroup is a new one to me to get the AppProperty as I was doing using the Midlet function. Thanks in advance and hopefully

[redpath]

So how do I update my signature for the new SDK version. I have these files in my SDK 4.0

and have downloaded the SDK 4.3 to get the new function.

 142 sigtool.csk
 160 sigtool.db
 208 sigtool.set

What needs to be done so I can sign the COD file for the new function added.

[redpath]

I installed the JDE4.3 SDK to replace the JDE4.0 SDK installed I simply moved the sigtool.* files into the BlackberryJDR4.3.0\bin directory and tried to sign the COD file using the SignatureTool.jar.

I see a table in the Dialog which has duplicate entries for mymidlet.

mymidlet.cod    Not Registered Required RRT RIM Runtime API

mymidlet-1.cod Not Registered Required RRT RIM Runtime API

mymidlet-2.cod Not Registered Required RRT RIM Runtime API

mymidlet-3.cod Not Registered Required RRT RIM Runtime API

mymidlet.cod    signed            Required RBB RIM Runtime API

mymidlet-1.cod signed            Required RBB RIM Runtime API

mymidlet-2.cod signed            Required RBB RIM Runtime API

mymidlet-3.cod signed            Required RBB RIM Runtime API

My csi file sent to me is client-RBB-xxxxxxxx.csi and it has RBB and is what I use to see in the SignatureTool dialog but now I have this RRT and not signed. So what do I need to do to step up to the new SDK and use my purchased signature file.

If I have to get a new signature what is the process again, I know to remember my PIN number of I can use

my current one to step up to the new SDK. 

What a mess.

[redpath]

Correction "RIM Blackberry Apps API" in the table

I installed the JDE4.3 SDK to replace the JDE4.0 SDK installed I simply moved the sigtool.* files into the BlackberryJDR4.3.0\bin directory and tried to sign the COD file using the SignatureTool.jar.

I see a table in the Dialog which has duplicate entries for mymidlet.

mymidlet.cod    Not Registered Required RRT RIM Runtime API

mymidlet-1.cod Not Registered Required RRT RIM Runtime API

mymidlet-2.cod Not Registered Required RRT RIM Runtime API

mymidlet-3.cod Not Registered Required RRT RIM Runtime API

mymidlet.cod    signed            Required RBB RIM Blackberry Apps API

mymidlet-1.cod signed            Required RBB RIM Blackberry Apps API

mymidlet-2.cod signed            Required RBB RIM Blackberry Apps API

mymidlet-3.cod signed            Required RBB RIM Blackberry Apps API

My csi file sent to me is client-RBB-xxxxxxxx.csi and it has RBB and is what I use to see in the SignatureTool dialog but now I have this RRT and not signed. So what do I need to do to step up to the new SDK and use my purchased signature file.

If I have to get a new signature what is the process again, I know to remember my PIN number of I can use

my current one to step up to the new SDK. 

What a mess.

[redpath]

More information, if I remove those functions you suggested to get the function I want for

the JAD files from a deployment; such as in this example. I don't have the signing problem

or these entries in the dialog for SignatureTool which cannot be signed.

mymidlet.cod    Not Registered Required RRT RIM Runtime API

mymidlet-1.cod Not Registered Required RRT RIM Runtime API

mymidlet-2.cod Not Registered Required RRT RIM Runtime API

mymidlet-3.cod Not Registered Required RRT RIM Runtime API

but of course I do not have the function that I was asking for.

What do I need to do? 

public class tbsmbbProperty {
    CodeModuleGroup[] allGroups = CodeModuleGroupManager.loadAll();
    CodeModuleGroup myGroup = null;
    String moduleName = ApplicationDescriptor.currentApplicationDescriptor().getModuleName();

    public void tbsmbbProperty(){
        for (int i = 0; i < allGroups.length; i++) {
            if (allGroups[i].containsModule(moduleName)) {
                myGroup = allGroups[i];
                break;
            }
        }
    }

    public String getAppProperty(String name){
        return myGroup.getProperty(name);
    }
}

[MSohm]

The -# entries you see listed are for the sibling cod files packaged in your main cod file.  It is normal to see this.  You can read more about sibling cod files here: 

What Is - The file size limit for wireless downloads
Article Number: DB-00015

http://www.blackberry.com/knowledgecenterpublic/livelink.exe/fetch/2000/348583/800708/800646/What_Is...

The "Not Registered Required RRT RIM Runtime API" means that the RRT signature key has not been installed.  Please run the RRT csi file to install this.  If you continue to have problems, please contact devsupport@rim.com for help with your signature key configuration.

[redpath]

I only have the RBB csi file that was sent and BB customer support has been contacted.

That I believe is the problem. Basically to upgrade from SDK 4.0 to 4.3 you must copy your

sigtool.* files from  the SDK 4.0 bin to the SDK 4.3 bin and thats all I hope since my RBB works 

but there is no RRT.