Comments on: Mac OS and Java Me SDK 3.0 http://www.tmro.net/2009/11/mac-os-and-java-me-sdk-3-0/ Mobilise your business Sat, 14 Jan 2012 06:55:20 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Nick http://www.tmro.net/2009/11/mac-os-and-java-me-sdk-3-0/comment-page-1/#comment-1470 Nick Wed, 02 Dec 2009 22:50:20 +0000 http://www.tmro.net/?p=213#comment-1470 Thank you for your comment! I'm afraid I was using jdk 1.6 when I get the device manager errors. See below: java version "1.6.0_15" Java(TM) SE Runtime Environment (build 1.6.0_15-b03-219) Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02-90, mixed mode) I'm looking forward to the next release. Thank you for your comment!
I’m afraid I was using jdk 1.6 when I get the device manager errors. See below:
java version “1.6.0_15″
Java(TM) SE Runtime Environment (build 1.6.0_15-b03-219)
Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02-90, mixed mode)

I’m looking forward to the next release.

]]> By: JavaME SDK Team http://www.tmro.net/2009/11/mac-os-and-java-me-sdk-3-0/comment-page-1/#comment-1468 JavaME SDK Team Wed, 02 Dec 2009 22:07:51 +0000 http://www.tmro.net/?p=213#comment-1468 Thanks for your feedback. We have concentrated on overall stability of emulator and our "mini" ide after EA release and I believe we have resolved most of issues mentioned in your blog post. * shared memory limitation on Mac * perm gen space usage * jdk 1.5 and jdk 1.6 support * lingering process you have mentioned is device-manager component which must be always running and all emulators and devices registers there. When jdk 1.6 is used device-manager displays its status icon in main menu and can be simply stopped. Jdk 1.5 lacks such support and thus device-manager must be killed. Upgrading to jdk 1.6 is recommended and will resolve this problem. * project creation from jad/jar without having sources is not very useful and has been left out. * running jad/jar is possible from context menu on emulator instance or from commandline "emulator -Xdescriptor:" We will be glad to hear your opinion after final release is out. Please check our blog at http://blogs.sun.com/javamesdk where you can find what's new and post your comments which will get right to development team. Thanks for your feedback. We have concentrated on overall stability of emulator and our “mini” ide after EA release and I believe we have resolved most of issues mentioned in your blog post.
* shared memory limitation on Mac
* perm gen space usage
* jdk 1.5 and jdk 1.6 support
* lingering process you have mentioned is device-manager component which must be always running and all emulators and devices registers there. When jdk 1.6 is used device-manager displays its status icon in main menu and can be simply stopped. Jdk 1.5 lacks such support and thus device-manager must be killed. Upgrading to jdk 1.6 is recommended and will resolve this problem.
* project creation from jad/jar without having sources is not very useful and has been left out.
* running jad/jar is possible from context menu on emulator instance or from commandline “emulator -Xdescriptor:”

We will be glad to hear your opinion after final release is out. Please check our blog at http://blogs.sun.com/javamesdk where you can find what’s new and post your comments which will get right to development team.

]]>