Skip to main content

PhoneME Feature Messaging Problem

5 replies [Last post]
orlandobarrera
Offline
Joined: 2010-03-08
Points: 0

Hi everyone,

Well, first of all im posting this issue here in the phoneME Advance forum since there seems to be a problem in the phoneME feature forum.

Ok then, im having a problemt trying to run a Midlet wich is supposed to receive sms messages then made an http connection to a servlet to write some data on a database.

A time ago, i was being able to do this using the Esmerte Jbed CLDD/MIDlet patform for windows mobile, but suddenly it stops working, it seems to wont be able to made the conecction with the servlet.

So then, i try to do it using davy's PhoneME Feature MIDP build for windows mobile, so i install the application and when i try to run the midlet im getting this exception:

The application has unexpectedly quit. Contact the application provider to resolve the issue.
javax/wireless/messaging/MessageListener.

So it seems to be a problem with the Messaging API but as far as i have read, this platform have support for this API. I made another version of the app removing all the messaging features just to check the connection to the servlet and is working nice...

I dont kknow what could be wrong, so i would be very thankfull if anyonce could help me,

greetings.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Hinkmond Wong

On 10/12/2010 10:41 AM, phonemeadvanced@mobileandembedded.org wrote:
> ...
>
> So then, i try to do it using davy's PhoneME Feature MIDP build for windows mobile, so i install the application and when i try to run the midlet im getting this exception:
>
> The application has unexpectedly quit. Contact the application provider to resolve the issue.
> javax/wireless/messaging/MessageListener.
>
> So it seems to be a problem with the Messaging API but as far as i have read, this platform have support for this API. I made another version of the app removing all the messaging features just to check the connection to the servlet and is working nice...
>
> I dont kknow what could be wrong, so i would be very thankfull if anyonce could help me,
>

When you try running using the Windows Mobile emulator on a Windows/x86
PC, what more do you see in the console window when it crashes? Do you
see any additional error messages that give greater detail on what made
the app unexpectedly quit?

If you don't see any more details in the console window, try adding
System.out.println statements to your program and find which exact line
of source code causes the crash. Have you narrowed that down yet?

Thanks,
Hinkmond

---------------------------------------------------------------------
To unsubscribe, e-mail: advanced-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: advanced-help@phoneme.dev.java.net

orlandobarrera
Offline
Joined: 2010-03-08
Points: 0

hi, thx for the response.

When running the app on an emulator it works fine.. of course im not able to recevie SMS's on the emulator (at least i dont know if its posibble or how can be done). Im also able to comunicate with the Servlet.

The problem is when running the app on the mobile device itself.. the app wont start, it just show the exception.

davyp
Offline
Joined: 2007-01-03
Points: 0

Although phoneME supports JSR120/JSR205, my phoneME Feature and phoneME Advanced
builds do not provide an implementation for Windows Mobile. That is probably why you are
getting the exception.

Davy

orlandobarrera
Offline
Joined: 2010-03-08
Points: 0

Oh I see... Well then that must be the problem, a big problem cause i have no idea how to make my own build with the necessary JSR's and features... hope you could give me and starting point..

thx very much for the response..

davyp
Offline
Joined: 2007-01-03
Points: 0

It is not just a matter of rebuilding the phoneME Feature stack with the appropriate JSRs.
Most of the Java code and APIs are there (in the subversion repository), but you still need to
implement the native bindings for Windows Mobile. This requires some C/C++ development work.

Davy