<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Let&#8217;s Talk About Java CDC One More Time&#8230; &#8230;native compiling for MIDP3</title>
	<link>http://blog.javabluetooth.com/2009/11/29/lets-talk-about-java-cdc-one-more-time-native-compiling-for-midp3/</link>
	<description>The Best Wireless Blog, Anywhere</description>
	<pubDate>Thu, 29 Jul 2010 12:20:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Bruce Hopkins</title>
		<link>http://blog.javabluetooth.com/2009/11/29/lets-talk-about-java-cdc-one-more-time-native-compiling-for-midp3/#comment-7962</link>
		<author>Bruce Hopkins</author>
		<pubDate>Mon, 30 Nov 2009 21:44:13 +0000</pubDate>
		<guid>http://blog.javabluetooth.com/2009/11/29/lets-talk-about-java-cdc-one-more-time-native-compiling-for-midp3/#comment-7962</guid>
		<description>@NeA,

Hey, I agree with you agreeing with me. Native compiling MIDP 3.0 source to Andorid should be the easiest thing to do since they both use Java syntax. Sun had better do something quickly before Flash takes over as the best cross-platform solution for mobile devices.</description>
		<content:encoded><![CDATA[<p>@NeA,</p>
<p>Hey, I agree with you agreeing with me. Native compiling MIDP 3.0 source to Andorid should be the easiest thing to do since they both use Java syntax. Sun had better do something quickly before Flash takes over as the best cross-platform solution for mobile devices.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Hopkins</title>
		<link>http://blog.javabluetooth.com/2009/11/29/lets-talk-about-java-cdc-one-more-time-native-compiling-for-midp3/#comment-7948</link>
		<author>Bruce Hopkins</author>
		<pubDate>Mon, 30 Nov 2009 17:38:09 +0000</pubDate>
		<guid>http://blog.javabluetooth.com/2009/11/29/lets-talk-about-java-cdc-one-more-time-native-compiling-for-midp3/#comment-7948</guid>
		<description>@Shawn,

Hey Shawn, nice to hear from you again. Thanks to Verizon, the Storm 2 will probably be a moderate success, although it's going to have an uphill battle against the iPhone because I've never seen a business person on the street with a Storm.

Now, to address your question specifically. Yes, the Blackberry OS has excellent support for Java CLDC and MIDP 2.1. It also has alot of support for a slew of JSRs which makes Blackberry a haven for Java ME developers. My concern is that RIM has no implementation for Java ME CDC, which is the middle-ground Java implementation between CLDC and Java SE. Java ME CDC *was* supposed to be a JVM platform for both high-end mobile phones and set-top boxes, but it never succeeded as a commercially available JVM platform for phones.</description>
		<content:encoded><![CDATA[<p>@Shawn,</p>
<p>Hey Shawn, nice to hear from you again. Thanks to Verizon, the Storm 2 will probably be a moderate success, although it&#8217;s going to have an uphill battle against the iPhone because I&#8217;ve never seen a business person on the street with a Storm.</p>
<p>Now, to address your question specifically. Yes, the Blackberry OS has excellent support for Java CLDC and MIDP 2.1. It also has alot of support for a slew of JSRs which makes Blackberry a haven for Java ME developers. My concern is that RIM has no implementation for Java ME CDC, which is the middle-ground Java implementation between CLDC and Java SE. Java ME CDC *was* supposed to be a JVM platform for both high-end mobile phones and set-top boxes, but it never succeeded as a commercially available JVM platform for phones.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Hopkins</title>
		<link>http://blog.javabluetooth.com/2009/11/29/lets-talk-about-java-cdc-one-more-time-native-compiling-for-midp3/#comment-7944</link>
		<author>Bruce Hopkins</author>
		<pubDate>Mon, 30 Nov 2009 14:52:14 +0000</pubDate>
		<guid>http://blog.javabluetooth.com/2009/11/29/lets-talk-about-java-cdc-one-more-time-native-compiling-for-midp3/#comment-7944</guid>
		<description>@David,

Ugh. And I had such high hopes for the Titan platform, especially since it used OSGi. It looks like Sprint is committed WebOS, Android, and Blackberry. Thanks David!</description>
		<content:encoded><![CDATA[<p>@David,</p>
<p>Ugh. And I had such high hopes for the Titan platform, especially since it used OSGi. It looks like Sprint is committed WebOS, Android, and Blackberry. Thanks David!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ove Nordström</title>
		<link>http://blog.javabluetooth.com/2009/11/29/lets-talk-about-java-cdc-one-more-time-native-compiling-for-midp3/#comment-7930</link>
		<author>Ove Nordström</author>
		<pubDate>Mon, 30 Nov 2009 10:21:21 +0000</pubDate>
		<guid>http://blog.javabluetooth.com/2009/11/29/lets-talk-about-java-cdc-one-more-time-native-compiling-for-midp3/#comment-7930</guid>
		<description>and also Enable MIDP3.0 application code to natively compile to Maemo runtimes</description>
		<content:encoded><![CDATA[<p>and also Enable MIDP3.0 application code to natively compile to Maemo runtimes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NeA</title>
		<link>http://blog.javabluetooth.com/2009/11/29/lets-talk-about-java-cdc-one-more-time-native-compiling-for-midp3/#comment-7925</link>
		<author>NeA</author>
		<pubDate>Mon, 30 Nov 2009 08:43:39 +0000</pubDate>
		<guid>http://blog.javabluetooth.com/2009/11/29/lets-talk-about-java-cdc-one-more-time-native-compiling-for-midp3/#comment-7925</guid>
		<description>Hi

This is such an important post and should be made public to all and everybody because this is a very good point. I am watching CDC going down for years now without even really getting started. And now, with iPhone, Android und Palm on the market, which do not even support CLDC anymore the lifetime of MIDP overall seems to end, even with 3.0 not even really being there.

Nevertheless, your three points of basically cross-compilation seem OK but I do not totally agree with them. Of course, it would be nice to them being cross-compiled natively to the different phones, but that could be more complicated than trying to really get their space in their. For example, it would be nice to see 3.0 going directly into the Android SDK. But overall your are right, Sun definitely has to do something, has to get in there, the one way or another.</description>
		<content:encoded><![CDATA[<p>Hi</p>
<p>This is such an important post and should be made public to all and everybody because this is a very good point. I am watching CDC going down for years now without even really getting started. And now, with iPhone, Android und Palm on the market, which do not even support CLDC anymore the lifetime of MIDP overall seems to end, even with 3.0 not even really being there.</p>
<p>Nevertheless, your three points of basically cross-compilation seem OK but I do not totally agree with them. Of course, it would be nice to them being cross-compiled natively to the different phones, but that could be more complicated than trying to really get their space in their. For example, it would be nice to see 3.0 going directly into the Android SDK. But overall your are right, Sun definitely has to do something, has to get in there, the one way or another.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn</title>
		<link>http://blog.javabluetooth.com/2009/11/29/lets-talk-about-java-cdc-one-more-time-native-compiling-for-midp3/#comment-7917</link>
		<author>Shawn</author>
		<pubDate>Mon, 30 Nov 2009 04:34:08 +0000</pubDate>
		<guid>http://blog.javabluetooth.com/2009/11/29/lets-talk-about-java-cdc-one-more-time-native-compiling-for-midp3/#comment-7917</guid>
		<description>Hi Bruce,  You mentioned at #6 the Blackberry Storm2.  Why?  Is this based on MIDP3.0 support or JavaME in general.  If JavaME then I'm a bit confused as my understanding is Blackberry's all support Midlets and "BB Applications" which are really just CLDC apps with the BB UI and extended APIs, but still Java.

I'm currently working on a Storm2 deploying an app, and in the 5.0 JDE there is midlet support.  Just want to make sure I'm not going to get the rug pulled out of the project. :)

But your statements on ME I couldn't agree with you more about. Something needs to get going on JavaME with smartphones.  In mobile development warfare the ME world is kinda fighting with sticks and rocks compared to B1 and Stealth fighters everyone else has now.

-Shawn</description>
		<content:encoded><![CDATA[<p>Hi Bruce,  You mentioned at #6 the Blackberry Storm2.  Why?  Is this based on MIDP3.0 support or JavaME in general.  If JavaME then I&#8217;m a bit confused as my understanding is Blackberry&#8217;s all support Midlets and &#8220;BB Applications&#8221; which are really just CLDC apps with the BB UI and extended APIs, but still Java.</p>
<p>I&#8217;m currently working on a Storm2 deploying an app, and in the 5.0 JDE there is midlet support.  Just want to make sure I&#8217;m not going to get the rug pulled out of the project. :)</p>
<p>But your statements on ME I couldn&#8217;t agree with you more about. Something needs to get going on JavaME with smartphones.  In mobile development warfare the ME world is kinda fighting with sticks and rocks compared to B1 and Stealth fighters everyone else has now.</p>
<p>-Shawn</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Beers</title>
		<link>http://blog.javabluetooth.com/2009/11/29/lets-talk-about-java-cdc-one-more-time-native-compiling-for-midp3/#comment-7891</link>
		<author>David Beers</author>
		<pubDate>Sun, 29 Nov 2009 21:55:15 +0000</pubDate>
		<guid>http://blog.javabluetooth.com/2009/11/29/lets-talk-about-java-cdc-one-more-time-native-compiling-for-midp3/#comment-7891</guid>
		<description>Java ME CDC isn't even alive with the Sprint Titan Platform, which was quietly "disappeared" by Sprint just before their October developer conference.  Here's what the Sprint execs at the conference had to say when I asked about it: http://www.pikesoft.com/blog/index.php?itemid=258</description>
		<content:encoded><![CDATA[<p>Java ME CDC isn&#8217;t even alive with the Sprint Titan Platform, which was quietly &#8220;disappeared&#8221; by Sprint just before their October developer conference.  Here&#8217;s what the Sprint execs at the conference had to say when I asked about it: <a href="http://www.pikesoft.com/blog/index.php?itemid=258" rel="nofollow">http://www.pikesoft.com/blog/index.php?itemid=258</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
