Java Development

[PengZhang]

Hi, everybody,

i need add a project as a libary. But at fist i must sign this libary, and i cant sign this RIMAPPSA2 !!! 

How to sign a libaryproject ?

Need HELP !!!!!

[rcmaniac25]

RIMAPPSA2 is a private signing key that only RIM has. If you get this then you are using a non-public library class/interface/field/function.

[PengZhang]

yes, i used my project as a libary. I can also put the whole files in 1 project, but it looks bad, and there r many java files.

So, sounds like i must put all of things in one big big project, right?

[rcmaniac25 · Accepted solution]

Not really what I meant. I meant that RIM has some functions and libraries that aren't supposed to be avalible to the average developer.

If you use those libraries or functions you get told you need a RIMAPPSA2 signing key (which you can't get).

You need to try to find what isn't public (or has been talked about on these forums that many people use). Then remove/replace them so you can sign your library.

[PengZhang]

thx for the answer.

Is there maybe an other way to make a privat project as a library, and without signing problem?

[CobiRic]

This is an attempt to clean up any confusion on this RIMAPPSA2 signature. A lot of people have this problem even though they are not using secret methods on purpose. There is a bug in the RIM tools, and in the RIM documents involving working with JAR files.

Some people get thie RIMAPPSA2 signature when trying to build a JAR file into their project.

It turns out there is a mistake in this doc, which many people follow: Working with Libraries - shared, bundled, releasing, and using 3rd Party SDKs

The trick is to build your "library" project as a MIDLET, not as an APPLICATION.

Following all steps from there on out leads to correct signing, and no longer getting the RIMAPPS2 signature required.