Hi folks, I'm developing a MIDP1.0 application. I have installed the WTK2.0 succesfully on linux, and the application runs fine when I use the 'Run' and 'Run via OTA' options. However, when I push the jad and jar files to my web server, I have issues. When I run the emulator on the command line: emulator -Xjam and enter in the address to the jad file, it fails with the error 'No Midlet Suites found. Check the URL to make sure it is correct'. I've verified that I can download the jad file with a browser. And I can see the emulator in the logs, getting the jad file. I've also tried the IP address and I get the same error (and see the request in the logs). I've tried increasing the verbosity level of the emulator, but either I target the wrong area and don't get relevant information, or I turn on -Xverbose:all and get way too much to see what's going wrong. I've googled on this, but found not much. I've also looked through this: OTA doc from Sun Any ideas? Dan
I disagree. I've been working on this project with the original poster. It is not necessary to point to a .wml file to point to a .jad file. We have successfully installed on several devices by making a request to the .jad file alone.
posted 15 years ago
Michael, Why in this case is a *wml* file needed instead of an *html* file? In my tests with WTK20_01 the emulator creates an html file containing an href anchor pointing to the jad file. Is it because it is a MIDP 1 MIDlet? Is it because most MIDP 1 decice have a WAP browser instead of an HTML one? serge
Originally posted by serge masse: Michael, Why in this case is a *wml* file needed instead of an *html* file? In my tests with WTK20_01 the emulator creates an html file containing an href anchor pointing to the jad file.
Because wml is safer as not all phone browsers support xHTML but nearly everyone supports wml. If your phone supports HTML, then ".html" would work just fine. cheers Michael
Originally posted by B Rook: I disagree. I've been working on this project with the original poster. It is not necessary to point to a .wml file to point to a .jad file. We have successfully installed on several devices by making a request to the .jad file alone.
Well, direct link to the jad file may work on *some* devices. But there are 150+ different J2ME devices out there. Not every one of them has the same OTA characteristics. My NexTel phone would only install jad files that I upload into its application manager web site. You were having problems with WTK, right? I was trying o point out the way WTK works (and I think this was what the OTA recommendation says). cheers Michael
Hi everyone. What Michael suggested (creating a .html file that had a link to the .jad file) worked just fine for my version of WTK: [moore@localhost WTK2.0]$ ./bin/emulator -version J2ME Wireless Toolkit 2.0_01 Profile: MIDP-2.0 Configuration: CLDC-1.0 Thanks for all the help.
It does not work with the live web server. When I enter "http://localhost:8080/j2me/HelloMIDlet.html" on my emulator, it works. However, when I enter "http://www.mydomain.com/j2me/HelloMIDlet.html", it does not work. It gives me "No MIDlet Suites found. Check the URL to make sure it is correct" message.
because of the older info in that JAD file. Of course, you can download the corresponding JAR file and load it locally on the Sun emulator, but how annoying. The Sun OTA tool should have tried to be more robust.
posted 10 years ago
Oh, it seems that you can embed both *.jad and *.jar files into the HTML page. For the *.jad files, the Sun OTA installer can report the file size whereas it just takes the jar as-is.
Something must be done about this. Let's start by reading this tiny ad:
Programmatically Create PDF Using Free Spire.PDF with Java