Merge of CDC and CLDC

In past there were two Mobility Packs. One for CLDC/MIDP development and one for CDC development (more details.... These two packs were merged into one product in NetBeans Mobility Pack 6.0 Milestone 7 build. You don't have to download two installers anymore.

There isn't available all the CDC functionality in the Milestone 7 build. It will be add later. Anyway, you can create new Mobile CDC project, or change platform of CLDC to an SDK supporting CDC. You can use templates for CLDC and CDC in J2ME project type. It can cause a compilation errors when you'll combine them together, of course. You have to be careful what files you can use on what J2ME platform. This approach provides more freedom to user however it requires more experienced users :)

I took a few screenshots

CDC project created with File |New Project... |J2ME | CDC Application has the same icon as the old CLDC project. The icons will be probably redesign in6.0 anyway :)

CDC and MIDP/CLDC templates are available in J2ME project

You can change the platform from CDC to CLDC (and wise versa). With configurations you can have everything in the same project.

Application descriptor panels changes according to selected platform - Wireless Toolkit (CLDC)

Application descriptor panels changes according to selected platform - Sun Java Toolkit for CDC

Merging of CDC and CLDC is rather irrelevant to me, although I can see this can save substantial resources for Sun. What are the bad news is that new mobility pack seems still to be only available for Windows, instead of pure Java. Common, you can do better than that ! I especially don't get it in the case of CDC as it is based on JDK 1.1, why it must be tied to specific platform ? Also CLDC can be ported to Java, see MPowerPlayer as example. IMO it sends a strong message that Sun is not that serious with Java after all. It says J2SE is dying. J2ME should be a part of J2SE, Xlets and MIDlets should be first class citizens in J2SE. Comments ?

Posted by Quinny on February 23, 2007 at 02:14 AM CET #

Well, let me explain... There are two different things mixed up in your comment.
First don't mix tools and runtime together. Tools are e.g. NetBeans, Mobility Pack, Mobility Pack for CDC. Runtime is Wireless Toolkit, Sun Java Toolkit for CDC.

The tools can run on any platform as they are written in pure java. You can unzip it anywhere. List of Supported platforms is different thing - it only says where it should work because it was tested.

It's more complicated with the runtime. Runtime is usually provided by the device manufacturer. I don't know why they support mainly windows.
Sun provides runtime for both J2ME configurations - CDC, CLDC. These are generic implementation of the JSRs + the emulator. The JSRs are just a jars. You can use them anywhere. The problem is with the emulator that is OS platform dependent (Don't ask me why).

As you can see from my previous paragraphs there isn't a simple answer... The lack of standards and fragmentation of the J2ME market makes it even more difficult.

I don't understand why should J2ME be part of J2SE ? Please remember what is Java MICRO Edition targeting - devices. Devices from Set-Top boxes, phones, vending machines, to Java cards...

Posted by Lukas on February 23, 2007 at 03:48 AM CET #

Lukas, thanks for answer. I don't think I was mixing tools and runtime together, I am aware that it is only the WTK and SJT which is not portable. As this is a required part of your toolchain, it renders whole mobilty pack as non portable, although I understand your clarification. But for the end user, this doesn't really matter, and all of the tools come from the single vendor (Sun) albeit from different units. As I said it doesn't send very good message about J2SE if it is not even a platform of choice for Sun's own products for the desktop (such as WTK).
If you create an implementation of J2ME for J2SE it would be possible to run J2ME MIDlet or Xlet in J2SE application (desktop or web via applet or webstart) - this would render the WTK obsolete - you can develop and showcase your MIDlets and Xlets even on the desktop BEFORE you put them into actual devices. As secondary positive effect it would stop the trend of doing same things in 2 separate ways and thus disabling porting code from one edition to the other (such as new State API in MIDP vs. system properties used elsewhere - and even implemented, but not really used in J2ME)

Posted by Quinny on February 26, 2007 at 06:24 AM CET #

Post a Comment:
  • HTML Syntax: NOT allowed

This is the main channel to share news, tips and other stuff related to my work. Sometimes you can find even personal stuff. Enjoy your reading...


« June 2016

No bookmarks in folder