Well, I basically renamed the jad file so it had the same filename
as the jar file (except for the extension). But if I then select this
midlet, I get the following errors:

Can't read manifest file
java.io.IOException: line too long
at java.util.jar.Attributes.read(Unknown Source)
at java.util.jar.Manifest.read(Unknown Source)
at java.util.jar.Manifest.<init>(Unknown Source)
at sun.misc.MIDPLauncher.main(Unknown Source)
at sun.misc.CVM.runMain(Unknown Source)

This basically means the jad file is not standards compliant.
There should be line breaks after every 70 characters. Have a
look at the MIDlet-permissions line in the manifest.mf file in the jar
file, which seems to be compliant. The jad file should follow the
same encoding for that MIDlet-permissions attribute and the
digital signatures.

I think for this midlet to run, you need a fully working Wireless API
implementation (the midlet tries to access sms://:1235)

Davy