We have a MIDP 1.0 application that we would like to have work on MIDP 2.0 devices. We are building and packaging the application using Sun's WTK. On the API settings tab in Sun's WTK you can choose 'Target Platform' as MIDP 1.0 or JTWI for MIDP 2.0. We are choosing MIDP 1.0 in hopes that packaging our app in this way will allow us to deliver to MIDP 1.0 and 2.0 handsets. We are having problems, however, with MIDP 2.0 phones as we get a 'Not Acceptable' message when transferring over-the-air. On MIDP 1.0 it seems to be working fine. Can anyone comment on the difference in packaging an application for MIDP 1.0 and MIDP 2.0 or know what might be causing the 'Not Acceptable' message on MIDP 2.0 phones.
Not sure why you get this problem, but one thing to keep in mind is that installing a 1.0 application on a 2.0 compatible phone will make your application install in the untrusted doamin. If you are trying to use a Connection that requires permission, maybe this is where the problem lies. It could be a permission that isn't granted to 1.0 applications.
Unfortunately, sometimes writing to a series of phones and having different versions of your application will make it more widespread for installation.
We do make use of an HttpConnection in our application...not sure exactly what you mean by "requires permission" though. Is the only difference between packaging as MIDP 2.0 vs. 1.0 the following JAD parameters: