Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
The moose likes Java Micro Edition and the fly likes porting in j2me Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Mobile » Java Micro Edition
Bookmark "porting in j2me" Watch "porting in j2me" New topic

porting in j2me

deep rai
Ranch Hand

Joined: Oct 04, 2007
Posts: 56

I would like to know how to test whether j2me applications are compatible for different handsets, or porting any tutorials/links regarding porting would be of great help to me.

Thanks in advance
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 17410

In theory, it's "Write once, run anywhere". In practice, portability has been more of a problem than it is with desktop Java apps. Part of this is because most mobile devices contain not only one of the Java mobile profiles, but also a number of the JSR-defined extensions and the exact mix varies from device to device.

An IDE is no substitute for an Intelligent Developer.
Joachim Rohde
Ranch Hand

Joined: Nov 27, 2006
Posts: 430

I guess when it comes to J2ME testing you still have to rely on manual tests on the real hardware.
A Sen

Joined: Oct 28, 2008
Posts: 4
Hi Deep,

As a first step -- you need to check the API usage. If you have used APIs from Sun'sMIDP/CLDC specification ONLY, you can have a piece of mind that it will work for all Java supported phones.

Next thing to check whether you are using Canvas or is it a complete non-canvas based application. In the latter case, you can be absolutely sure that it will work on all Java supported phones and all sizes as well.

However, if you are using Canvas, then you should analyse each displayable screen as it will require customisation for different phone sizes.

This might get more complex, if you are already using phone specific APIs. You will either need to identify alternative ones for other phone models (may not be available) or remove them (which in turn might mean removing the functionality).

Hope this might give you a direction to plan your porting effort.

I agree. Here's the link:
subject: porting in j2me
jQuery in Action, 3rd edition