There are situations where the XHTML XForms approach we prescribe is not ideal, because clearly, you are going to get some round trips, and the things you can do locally with the XForms events are typically not things that enable you to write a game, or something like that, very pixel oriented. So if you want to do something more like at the pixel level, more visual, more highly interactive, typically consumer oriented applications, J2ME is definitely the way to go. It's a great execution environment for that type of application.

Typically, they have little connectivity to the server back end because it's a little difficult to get down and execute for a certain time perhaps and things like that. That's a typical design point for J2ME. Even though we certainly see some use for J2ME also in the enterprise space. I'd say that's a broad generalization. It's at that end of the spectrum.

On the other extreme, if you have business applications, which are really tapping into databases, doing transactions into a database where you want current information and things like that, we're really going to be focusing on the traditional server-side development technology which will be a J2EE component rendering XHTML and XForms. And then of course there are many types of applications in the middle between those two extremes.