Java(TM) ME Platform SDK 3.0 - Any hacks to add emulators to this?

Hi, I haven't been developing on mobile platforms for some time, and so just downloaded this SDK to start a new project. I need to test some code using emulators from Nokia and SE, but there seems no way to add new emulators. Is this SDK hardcoded to only use the basic generic devices, and if so, which platform should I be using (Eclipse, Netbeans?)
The "Add Java platform" option fails to find the emulator devices, even if pointed at the correct directories, so I'll be grateful to hear any ideas.
Thanks.

Note: This thread was originally posted in the [Sun Java Wireless Toolkit|http://forums.sun.com/forum.jspa?forumID=82] forum, but moved to this forum for closer topic alignment.

Similar Messages

New to Java(TM) ME Platform SDK 3.0 how to open multiple emulators?

Hi im new to Java Mobile Phone apps.
I want to make a bluetooth game and theres a great bluetooth example in the package but i just cant find anywhere i can open 2 or more emulators.
The compiler does'nt allow multiple instances either, Havent found a setting to change that either.
Please help thank you.

ooo apperently you have to "copy" the project and then change the emulator settings for the project to use a diffrent emulator shell. also you have to fix all build errors.

Error when starting Java(TM) ME Platform SDK 3.0

hey guys, I get this error when starting Java(TM) ME Platform SDK 3.0. When I installed it it installed 'successfully' and then I double clicked the file on the desktop (I'm using Windows Vista 32bit Home premium) and it gave me the following error when saying 'Starting Modules':-------------------------------------------------------------------------------
Log Session: Sunday, February 13, 2011 1:52:25 PM GMT
System Info: Product Version         = Java(TM) ME Platform SDK 3.0
Operating System        = Windows Vista version 6.0 running on x86
Java; VM; Vendor        = 1.6.0_23; Java HotSpot(TM) Client VM 19.0-b09; Sun Microsystems Inc.
Runtime                 = Java(TM) SE Runtime Environment 1.6.0_23-b05
Java Home               = C:\Program Files\Java\jdk1.6.0_23\jre
System Locale; Encoding = en_GB (cdctoolbar); Cp1252
Home Directory          = C:\Users\Molten Ice
Current Directory       = C:\Program Files\Java\Java_ME_platform_SDK_3.0\bin
User Directory          = C:\Users\Molten Ice\javame-sdk\toolbar\3.0
Installation            = C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\javamesdk1
                            C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\ide10
                            C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\java2
                            C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\mobility8
                            C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\profiler2
                            C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\platform9
Boot & Ext. Classpath   = C:\Program Files\Java\jdk1.6.0_23\jre\lib\resources.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\rt.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\jce.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\modules\jdk.boot.jar;C:\Program Files\Java\jdk1.6.0_23\jre\classes;C:\Program Files\Java\jdk1.6.0_23\jre\lib\ext\dnsns.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\ext\localedata.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\ext\sunjce_provider.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\ext\sunmscapi.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\ext\sunpkcs11.jar
Application Classpath   = C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\platform9\lib\boot.jar;C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\platform9\lib\org-openide-modules.jar;C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\platform9\lib\org-openide-util.jar;C:\Program Files\Java\jdk1.6.0_23\lib\dt.jar;C:\Program Files\Java\jdk1.6.0_23\lib\tools.jar
Startup Classpath       = C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\platform9\core\core.jar;C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\platform9\core\org-openide-filesystems.jar;C:\Program Files\Java\Java_ME_platform_SDK_3.0\toolbar\javamesdk1\core\locale\core_cdctoolbar.jar
WARNING [org.netbeans.core.projects.cache]: Inefficient to include an empty layer in a module: jar:file:/C:/Program%20Files/Java/Java_ME_platform_SDK_3.0/toolbar/javamesdk1/modules/org-netbeans-modules-javame-common.jar!/org/netbeans/modules/javame/common/resources/layer.xml
WARNING [org.netbeans.core.projects.cache]: Inefficient to include an empty layer in a module: jar:file:/C:/Program%20Files/Java/Java_ME_platform_SDK_3.0/toolbar/javamesdk1/modules/org-netbeans-modules-e2e.jar!/org/netbeans/modules/e2e/layer.xml
WARNING [org.openide.filesystems.Ordering]: Not all children in Services/MIMEResolver/ marked with the position attribute: [org-netbeans-modules-javame-netmon-data-NetMonDataResolver.xml], but some are: [org-netbeans-modules-java-mime-resolver.xml, org-apache-tools-ant-module-mime-resolver.xml, org-netbeans-modules-editor-settings-storage-mime-resolver.xml, org-netbeans-modules-url-mime-resolver.xml, org-netbeans-modules-pdf-mime-resolver.xml, org-netbeans-modules-jar-mime-resolver.xml, org-netbeans-modules-editor-codetemplates-mime-resolver.xml]
WARNING [org.openide.filesystems.Ordering]: Not all children in Services/MIMEResolver/ marked with the position attribute: [org-netbeans-modules-javame-netmon-data-NetMonDataResolver.xml], but some are: [org-netbeans-modules-java-mime-resolver.xml, org-apache-tools-ant-module-mime-resolver.xml, org-netbeans-modules-editor-settings-storage-mime-resolver.xml, org-netbeans-modules-url-mime-resolver.xml, org-netbeans-modules-pdf-mime-resolver.xml, org-netbeans-modules-jar-mime-resolver.xml, org-netbeans-modules-editor-codetemplates-mime-resolver.xml]
[      0]   INFO - ootstrap.PropertyEditorManager - Registering custom property editors
[    117]   INFO - bootstrap.ObjectGraphProcessor - Consolidating dependencies...
[    217]   INFO - bootstrap.ObjectGraphProcessor - Consolidated dependencies...
[    317]   INFO - bootstrap.ObjectGraphProcessor - Calculating order...
[    417]   INFO - bootstrap.ObjectGraphProcessor - Calculated order
[    523]   INFO - un.jme.toolkit.bootstrap.Batch - Initializing objects...
[    627]   INFO - un.jme.toolkit.bootstrap.Batch - Applying I18N
[    732]   INFO - un.jme.toolkit.bootstrap.Batch - Initialized objects
[    832]   INFO - un.jme.toolkit.bootstrap.Batch - Calling create() methods...
[    932]   INFO - un.jme.toolkit.bootstrap.Batch - Calling start() methods...
[   1032]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[   2166]   WARN - mpl.ObjectServerConnectionImpl - Remote object server is not running at service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[   2268]   INFO - l.process.GenericProcessRunner - Starting process: C:\Program Files\Java\Java_ME_platform_SDK_3.0/bin/device-manager.exe
[   3384]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[   5476]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[   7576]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[   9677]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 11777]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 13877]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 15977]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 18077]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 20177]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 22277]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 23379] ERROR - un.jme.toolkit.bootstrap.Batch - Problem calling start() on DeviceManagerConnection
java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.jme.toolkit.bootstrap.Batch.invoke(Unknown Source)
     at com.sun.jme.toolkit.bootstrap.Batch.tryInvoke(Unknown Source)
     at com.sun.jme.toolkit.bootstrap.Batch.startObjects(Unknown Source)
     at org.netbeans.modules.javame.common.container.Module.start(Module.java:21)
     at org.netbeans.modules.javame.common.container.ContainerSupport.startModule(ContainerSupport.java:67)
     at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManagerConnection(DevicemanagerHelper.java:41)
     at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.ensureConnected(DevicemanagerHelper.java:48)
     at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManager(DevicemanagerHelper.java:84)
     at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.ensureDMStarted(AutoInstaller.java:292)
     at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.restored(AutoInstaller.java:63)
     at org.netbeans.core.startup.NbInstaller.loadCode(NbInstaller.java:421)
     at org.netbeans.core.startup.NbInstaller.load(NbInstaller.java:342)
     at org.netbeans.ModuleManager.enable(ModuleManager.java:906)
     at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:428)
     at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:364)
     at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:276)
     at org.netbeans.core.startup.Main.getModuleSystem(Main.java:165)
     at org.netbeans.core.startup.Main.start(Main.java:312)
     at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:110)
     at java.lang.Thread.run(Thread.java:662)
Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
     java.net.ConnectException: Connection refused: connect]
     at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:338)
     at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
     at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.connect(Unknown Source)
     at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.start(Unknown Source)
     ... 24 more
Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
     java.net.ConnectException: Connection refused: connect]
     at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
     at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1886)
     at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1856)
     at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257)
     ... 27 more
Caused by: java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
     java.net.ConnectException: Connection refused: connect
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
     at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
     at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
     at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:97)
     ... 32 more
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:529)
     at java.net.Socket.connect(Socket.java:478)
     at java.net.Socket.<init>(Socket.java:375)
     at java.net.Socket.<init>(Socket.java:189)
     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
     ... 37 more
SEVERE [org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper]: Cannot connect to device manager
java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:529)
     at java.net.Socket.connect(Socket.java:478)
     at java.net.Socket.<init>(Socket.java:375)
     at java.net.Socket.<init>(Socket.java:189)
     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
Caused: java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
     java.net.ConnectException: Connection refused: connect
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
     at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
     at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
     at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:97)
Caused: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
     java.net.ConnectException: Connection refused: connect]
     at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
     at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1886)
     at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1856)
     at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257)
Caused: java.io.IOException: Failed to retrieve RMIServer stub
     at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:338)
     at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
     at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.connect(Unknown Source)
     at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.start(Unknown Source)
Caused: java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.jme.toolkit.bootstrap.Batch.invoke(Unknown Source)
     at com.sun.jme.toolkit.bootstrap.Batch.tryInvoke(Unknown Source)
     at com.sun.jme.toolkit.bootstrap.Batch.startObjects(Unknown Source)
     at org.netbeans.modules.javame.common.container.Module.start(Module.java:21)
     at org.netbeans.modules.javame.common.container.ContainerSupport.startModule(ContainerSupport.java:67)
     at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManagerConnection(DevicemanagerHelper.java:41)
     at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.ensureConnected(DevicemanagerHelper.java:48)
[catch] at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManager(DevicemanagerHelper.java:84)
     at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.ensureDMStarted(AutoInstaller.java:292)
     at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.restored(AutoInstaller.java:63)
     at org.netbeans.core.startup.NbInstaller.loadCode(NbInstaller.java:421)
     at org.netbeans.core.startup.NbInstaller.load(NbInstaller.java:342)
     at org.netbeans.ModuleManager.enable(ModuleManager.java:906)
     at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:428)
     at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:364)
     at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:276)
     at org.netbeans.core.startup.Main.getModuleSystem(Main.java:165)
     at org.netbeans.core.startup.Main.start(Main.java:312)
     at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:110)
     at java.lang.Thread.run(Thread.java:662)
[ 23598]   INFO - bootstrap.ObjectGraphProcessor - Consolidating dependencies...
[ 23698]   INFO - bootstrap.ObjectGraphProcessor - Consolidated dependencies...
[ 23798]   INFO - bootstrap.ObjectGraphProcessor - Calculating order...
[ 23898]   INFO - bootstrap.ObjectGraphProcessor - Calculated order
[ 23998]   INFO - un.jme.toolkit.bootstrap.Batch - Initializing objects...
[ 24098]   INFO - un.jme.toolkit.bootstrap.Batch - Applying I18N
[ 24198]   INFO - un.jme.toolkit.bootstrap.Batch - Initialized objects
[ 24298]   INFO - un.jme.toolkit.bootstrap.Batch - Calling create() methods...
[ 24398]   INFO - un.jme.toolkit.bootstrap.Batch - Calling start() methods...
[ 24498]   INFO - un.jme.toolkit.bootstrap.Batch - Objects started
[ 24600]   INFO - bootstrap.ObjectGraphProcessor - Consolidating dependencies...
[ 24700]   INFO - bootstrap.ObjectGraphProcessor - Consolidated dependencies...
[ 24800]   INFO - bootstrap.ObjectGraphProcessor - Calculating order...
[ 24900]   INFO - bootstrap.ObjectGraphProcessor - Calculated order
[ 25000]   INFO - un.jme.toolkit.bootstrap.Batch - Initializing objects...
[ 25100]   INFO - un.jme.toolkit.bootstrap.Batch - Applying I18N
[ 25202]   INFO - un.jme.toolkit.bootstrap.Batch - Initialized objects
[ 25302]   INFO - un.jme.toolkit.bootstrap.Batch - Calling create() methods...
[ 25402]   INFO - un.jme.toolkit.bootstrap.Batch - Calling start() methods...
[ 25502]   INFO - un.jme.toolkit.bootstrap.Batch - Objects started
[ 25602]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 26699]   WARN - mpl.ObjectServerConnectionImpl - Remote object server is not running at service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 26799]   INFO - l.process.GenericProcessRunner - Starting process: C:\Program Files\Java\Java_ME_platform_SDK_3.0/bin/device-manager.exe
[ 27914]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 30005]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 32106]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 34206]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 36306]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 38406]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 40506]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 42607]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 44706]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
[ 46806]   INFO - mpl.ObjectServerConnectionImpl - Connecting to service:jmx:rmi:///jndi/rmi://127.0.0.1:1999/device-manager
SEVERE [org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper]: Cannot connect to device manager
java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:529)
     at java.net.Socket.connect(Socket.java:478)
     at java.net.Socket.<init>(Socket.java:375)
     at java.net.Socket.<init>(Socket.java:189)
     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
Caused: java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
     java.net.ConnectException: Connection refused: connect
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
     at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
     at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
     at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:97)
Caused: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
     java.net.ConnectException: Connection refused: connect]
     at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
     at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1886)
     at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1856)
     at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257)
Caused: java.io.IOException: Failed to retrieve RMIServer stub
     at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:338)
     at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
     at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.connect(Unknown Source)
     at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.start(Unknown Source)
     at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.lookupMBean(Unknown Source)
     at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.findObject(Unknown Source)
[catch] at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.openConnection(DevicemanagerHelper.java:53)
     at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManager(DevicemanagerHelper.java:86)
     at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.ensureDMStarted(AutoInstaller.java:292)
     at org.netbeans.modules.javame.platform.jme_sdk.autoinstaller.AutoInstaller.restored(AutoInstaller.java:63)
     at org.netbeans.core.startup.NbInstaller.loadCode(NbInstaller.java:421)
     at org.netbeans.core.startup.NbInstaller.load(NbInstaller.java:342)
     at org.netbeans.ModuleManager.enable(ModuleManager.java:906)
     at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:428)
     at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:364)
     at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:276)
     at org.netbeans.core.startup.Main.getModuleSystem(Main.java:165)
     at org.netbeans.core.startup.Main.start(Main.java:312)
     at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:110)
     at java.lang.Thread.run(Thread.java:662)
[ 48018]   INFO - bootstrap.ObjectGraphProcessor - Consolidating dependencies...
[ 48118]   INFO - bootstrap.ObjectGraphProcessor - Consolidated dependencies...
[ 48218]   INFO - bootstrap.ObjectGraphProcessor - Calculating order...
[ 48318]   INFO - bootstrap.ObjectGraphProcessor - Calculated order
[ 48418]   INFO - un.jme.toolkit.bootstrap.Batch - Initializing objects...
[ 48518]   INFO - un.jme.toolkit.bootstrap.Batch - Applying I18N
[ 48618]   INFO - un.jme.toolkit.bootstrap.Batch - Initialized objects
[ 48718]   INFO - un.jme.toolkit.bootstrap.Batch - Calling create() methods...
[ 48818]   INFO - un.jme.toolkit.bootstrap.Batch - Calling start() methods...
[ 48918]   INFO - un.jme.toolkit.bootstrap.Batch - Objects started
[ 49018]   INFO - bootstrap.ObjectGraphPI did install Nokia's SDK with NetBeans and this works perfectly.
I went through with everything recommended here: http://blogs.sun.com/javamesdk/entry/first_aid_when_emulator_doesn
But nothing worked.
Any help appreciated!
Thanks.

Note: This thread was originally posted in the [Sun Java Wireless Toolkit|http://forums.sun.com/forum.jspa?forumID=82] forum, but moved to this forum for closer topic alignment.

CLDC 1.1, MIDP 2.0 and JSR-75,135 in Java(TM) ME platform SDK 3.0, EA?

Hello.
I am trying to develope a "simple" MP3 playback application using "Java(TM) ME platform SDK 3.0, EA", but I have a problem.
I need to write the program for a device that has CLDC 1.1 and MIDP 2.0 configuration, with optional JSR-75 and JSR-135 packages.
When I start a new MIDP application project, I can choose the platform. Then I have 3 options:
DefaultCldcMsaPhone 1&2 --- CLDC-1.1 & MIDP-2.1 with MMAPI and File Connection (among others)
DefaultCldcPhone 1&2 --- CLDC-1.1 & MIDP-2.1 with MMAPI and File Connection (among others)
DefaultCldcJtwiPhone 1&2 --- CLDC-1.1 & MIDP-2.0 with only MMAPI and Wireless Messaging.
The other options are greyed, so I can not select a combination that has CLDC-1.1, MIDP-2.0, MMAPI and File Connect at the same time... I have tryied switching to the full NetBeans and then I have more flexibility choosing the device configuration and profile, using "Sun Java(TM) Wireless Toolkit 2.5.2 for CLDC" emulator platform. But when I run my application in the emulator, it takes some seconds to start playing the MP3. When I change to SDK 3.0, it plays inmediately.
So my question is, can I create a custom device that has everyting I need with "Java(TM) ME platform SDK 3.0, EA"?
Thank you in advance.
Marc Vallribera i Ros

Hi,
This problem is known and will be resolved in Final Release of SDK.
Now you can try to change configuration in <your_project_path>/project.properties file.
platform.bootclasspath and platform.profile parameters should be changed.
Igor

Error trying to run the HelloMidlet.java in Java(TM) ME Platform SDK 3.0

Hi!
I can not run the example-midlet. I get this error:
pre-init:
pre-load-properties:
exists.config.active:
exists.netbeans.user:
exists.user.properties.file:
load-properties:
exists.platform.active:
exists.platform.configuration:
exists.platform.profile:
basic-init:
cldc-pre-init:
cldc-init:
cdc-init:
bdj-init:
post-init:
init:
conditional-clean-init:
conditional-clean:
pre-clean:
clean-timestamp:
clean-preprocessed:
clean-classes:
Deleting directory C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\build\compiled
clean-obfuscated:
clean-preverified:
Deleting directory C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\build\preverifysrc
Deleting directory C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\build\preverified
clean-manifest:
Deleting: C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\build\manifest.mf
clean-jar:
Deleting: C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\dist\MobileApplication1.jar
clean-jad:
Deleting: C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\dist\MobileApplication1.jad
clean-javadoc:
clean-j9:
Deleting: C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\convert1661546129
Deleting directory C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\build
Deleting directory C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\dist
post-clean:
do-clean:
deps-jar:
pre-preprocess:
do-preprocess:
post-preprocess:
preprocess:
pre-compile:
extract-libs:
Created dir: C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\build\compiled
do-compile:
Compiling 1 source file to C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\build\compiled
post-compile:
compile:
post-obfuscate:
obfuscate:
pre-obfuscate:
proguard-init:
skip-obfuscation:
proguard:
lwuit-build:
pre-preverify:
do-preverify:
Created dir: C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\build\preverifysrc
Copying 1 file to C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\build\preverifysrc
Created dir: C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\build\preverified
Preverifying 1 file(s) into C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\build\preverified directory.
post-preverify:
preverify:
pre-jar:
set-password-init:
set-keystore-password:
set-alias-password:
set-password:
create-jad:
Created dir: C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\dist
add-configuration:
add-profile:
do-extra-libs:
Created dir: C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\dist\lib
jad-jsr211-properties:
do-jar:
Building jar: C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\dist\MobileApplication1.jar
do-jar-no-manifest:
bdj-build-image:
update-jad:
Updating application descriptor: C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\dist\MobileApplication1.jad
Generated "C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\dist\MobileApplication1.jar" is 1423 bytes.
post-jar:
jar:
pre-run:
netmon.check:
open-netmon:
cldc-run:
Copying 1 file to C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\dist\nbrun4923931937783686685
Copying 1 file to C:\Documents and Settings\Ander\My Documents\JavaMESDKProjects\MobileApplication1\dist\nbrun4923931937783686685
Jad URL for OTA execution: http://localhost:8082/servlet/org.netbeans.modules.mobility.project.jam.JAMServlet/C%3A/Documents+and+Settings/Ander/My+Documents/JavaMESDKProjects/MobileApplication1/dist//MobileApplication1.jad
Starting emulator in execution mode
*** Error ***
Failed to connect to device 0!
Reason:
Device 0 not available!
bdj-run:
cdc-run:
profiler.check:
open-profiler:
run:
BUILD SUCCESSFUL (total time: 6 seconds)
I have attempted with other devices and the error is the same Failed to connect to device "X"! Reason: Device "X" not available!.
I have:
1. Restarted the system, not works.
2. Re-install all the sdk, not works.
3. Deleting C:\Documents and Settings\Ander\javame-sdk and restarting the SDK, not works.
4. Shutdown the firewall, antivirus, etc... not works.
I become exasperated, i do not know how to do to solve this situation... could you help me? i am really desperate. Thank you very much for your help, and sorry for my english grammar!!
thank you very much

Note: This thread was originally posted in the [Sun Java Wireless Toolkit|http://forums.sun.com/forum.jspa?forumID=82] forum, but moved to this forum for closer topic alignment.

Java ME Platform SDK - S60 Emulator Problem

Hi Everyone!
I am new to S60 development. I searched the forum, and some other discussion forums but could not find any solution to my problem (If there is one in this forum, sorry about that).
I installed Java ME Platform SDK 3.0 Early Access. I also installed Java SDK for S60-FP1, and added this platform to my IDE with no problems.
The problem is, I can write and execute my code on S60 emulator, but Java IDE has got this annoying exception blinking on the bottom right side saying: "java.lang.IllegalArgumentException: Device S60Emulator not registered!". As I said, I can run the application, but I cannot debug because of some exceptions!
Why this can be happening, can it be a misconfiguration or something?
Thank you all!

Did you check Release Notes of the SDK? I've seen it once - if memory serves it lists quite a lot of known bugs.
Maybe the problem you describe is listed there too... and if you're really lucky then description may even mention some workaround for it.

How can i change backgroud color in Java ME Platform SDK 3?

Hello.
Yesterday i had donwloaded Java ME Platform SDK 3.0. It is IDE based on NetBeans core, but i didn't find any facility to change default colors. (NetBeans have option to change color theme). I am don't like working when background color is white, i prefer black. So, how change a background color? Can anybody help me to figure this problem out?
p.s. sorry for my bad english (

Hello,
Unfortunately it is not possible. We will think about it for next release. Java ME SDK is not supposed to offer full IDE functionality (e.g. changing editor colors), that's why some features are missing. For full IDE support use NetBeans IDE with Mobility support.

Problem in connecting external URLs from Java ME Platform SDK 3.0

Hello all,
I am building a mobile application using Java ME Platform SDK 3.0. My application needs to connect to external web services. I have finished development of first module and it is running perfectly from actual mobile device. But the problem is:
While developing the application I am used to test it with given mobile Emulators in Java ME Platform SDK 3.0. During this test I am not able to connect to external web service if I am testing if within local intranet using proxy server. To solve this I have configured Proxy Setting in the IDE at:
Tools Menu -> Options -> General -> Manual Proxy Settings and given HTTP Proxy Server and it's Port. The same proxy settings are there in all web browsers in my machine.
But It is giving error like:
Unknown error 10054 during socket::read
Strange thing is that the same application is running perfectly If my PC is not in Intranet and connected to internet directly.
Please help me that how can I set proxy settings in Java ME Platform SDK 3.0 to get in working?
Any suggestions regarding this will be helpful for me.
Thanks to spare some time and read my post,
Tejas.

Hi Tejas,
it should work. I tested it right now and my proxy was used without any problems. The way how you set proxy settings is correct.
Could you try following to verify that it is a proxy problem or not, please?
1. run demo application "Demos" (from Start Page or File->Open Sample Project)
2. choose "HttpView" midlet and start it
3. choose "cnn"
4. if proxy is set correctly, you will see page source; otherwise you will get an error message
If the demo runs fine, the problem is probably somewhere else in the communication.
There is one limitation in proxy settings. Only proxy without username and password is supported. Isn't it your case?
Regards,
Radko

Business Intelligence java platform SDK

Hey guys,
I want to work out the advantages of the BI Java platform SDK. For this I have some guides.
At first I want to start with the BI Java SDK Development Guide.
Already at the beginning I have a problem. I thought if I include the libarys from the local WebIntelligence I'll be done, but the jar-files from the guide are not included.
Now my question, do I have to download a special SDK-package.
Where can I find it?
The attached picture shows the libarys I need. The red marked are missing.
Thanks and Regards
Dennis Kliche

Hi,
Please check this link it will help you in developing BI Application:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/55097293-0701-0010-c1b6-efc02e2c956a
/people/moya.watson/blog/2004/12/27/three-new-how-to-guides-for-the-bi-java-sdk
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9a90e590-0201-0010-fdab-cf1691fadb06
Hope it helps you.
Thanks
Mona

Using CLDC Sun Java(TM) Micro Edition SDK 3.0 EA with netbeans

Hi ,
has anyone stumbled upon this - I just installed netbeans and Java(TM) Micro Edition SDK 3.0 and am trying to work with the examples of the sdk inside the netbeans , but when I open them I get the message : "Problem - the project uses platform CLDC Sun Java(TM) Micro Edition SDK 3.0 EA", but it was not found. Create platform named like this - I tried to do it , but it doesn't help.
Is there any way of overcoming this?

Ok , I found the solution.
I installed the Sun Java Wireless Toolkit for CLDC ver 2.5.2.2_01 directly (not as part of the SDK 3.0) , then added new platform and a new project configuration
according to the new platform.
In case someone else stumbles on that....

Ghost connections "Java(TM) 2 Platform Standard Edition"

We have a server application with multiple threads each using JDBC connections. On the Database server (MS SQL Server 7) we notice more and more connections with the SQLQueryAnalyzer-ProgramName "Java(TM) 2 Platform Standard Edition". But all our (known) connections have custom names or the default name of the JDBC driver (jTDS). The developer of jTDS answered that the driver only have connections that are requested by the application. But we don't have connections named dbc connections "Java(TM) 2 Platform Standard Edition" ... ?

We don't use an application server, it's just a plain Java application. No frameworks and only 3rd party libs that don't handle any database connection - and the JDBC driver jTDS. As one of the developers got very angry about my bug report, because he insists that it's not the fault of jTDS, I have to rule out jTDS. That would mean that it's somewhere in my application. But I just have 1 single class that actually creates a JDBC connection, so it's not hard to debug this. And I can't see any additional connections as all of my connections get specific names and not "Java(TM) 2 Platform Standard Edition".
I searched all source code of the Java SDK, jTDS and my source code for occurences of "Java(TM) 2 Platform Standard Edition" and can't find any. I hoped that somebody knows who is using this string (and when). It sounds like general Java (SDK/JRE) is setting this name, but I haven't found it.

User Role problems in Sun Java Application Server Platform Edition 8

I am having two problems setting up user roles in Sun Java Application Server Platform Edition 8. At first, I thought that it was a problem with the higher level features that I was using, so I created a very simple example using the simplest authentication I can use, but the problem still occurs. I am using the file realm and configuring the users in the App Server Admin Console. I create 2 users in different roles. One user should have access, the other should not.
1) The first problem is that both users can access the page
2) The second problem is that the isUserInRole() method returns false for both users with the role that it should be authenticating against.
Here is a sample of my code:
Users Configured in Console:
username password roles
user1 ********** admin
user2 ********** noaccess
web.xml
     <security-role>
          <role-name>admin</role-name>
     </security-role>
     <security-constraint>
          <web-resource-collection>
               <web-resource-name>My Protected Area</web-resource-name>
               <url-pattern>/*</url-pattern>
          </web-resource-collection>
          <auth-constraint>
               <role-name>admin</role-name>
          </auth-constraint>
          <user-data-constraint>
               <transport-guarantee>NONE</transport-guarantee>
          </user-data-constraint>
     </security-constraint>
     <login-config>
          <auth-method>BASIC</auth-method>
          <realm-name>file</realm-name>
     </login-config>
     <servlet>
          <servlet-name>
               TestServlet
          </servlet-name>
          <servlet-class>
               mypackage.TestServlet
          </servlet-class>
          <security-role-ref>
               <role-name>admin</role-name>
               <role-link>admin</role-link>
          </security-role-ref>
     </servlet>
     <servlet-mapping>
          <servlet-name>
               TestServlet
          </servlet-name>
          <url-pattern>
               /TestServlet
          </url-pattern>
     </servlet-mapping>
TestServlet.java:
          out.println("admin role: " + request.isUserInRole("admin") + "<BR/>");
Thanks before hand for any responses.
- Brian

Hi Jeanfrancois,
Your suggestion has lead me to find my problem. There were actually three problems.
1) First, you suggestion to reorder my xml file did not cause any errors to occur. I got suspicious that my web.xml file was wrong. I looked at some sample web-xml files and found that I was missing the header as follows:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN' 'http://java.sun.com/dtd/web-app_2_3.dtd'>
2) When I added this information, the deploy feature failed stating the my web.xml file was out of order. I fixed the ordering. It now deployed, but the security still wasn't working.
3) I then added the sun-web.xml file. This file was missing before hand as I thought it was unnessary. However, this file added the essential mapping from a role to a group. After adding this, it now started to work.
Thanks so much for you time and effort. You really did help me.
- Brian Blank

Is new Windows Mobile VM for Java ME in new SDK 3.0 for common users?

Hi,
There are bunch of buggy VMs for WM Platform such as Esmertec JBED, Esmertec JBLEND, IBM J9 etc. They have lot of bugs and they don't support neccessary JSRs. Now I have read about Windows Mobile integration in new SDK 3.0 EA for Java ME - I undestand that there is a new VM for WM from Sun, is that right? But when I installed CAB version, it seams it is just for on-device debugging with connected Wireless Toolkit on PC. I can't launch midlets located in my WM device on it. Is there also VM for common users? So they could install virtual machine and then install their midlets? I think many developers and users would apreciate it. Or is it at least in plan to release such VM?

Jackson_Bill wrote:
What IDE are you using and what platform?Read first.
Moh Bob wrote:
I'm using J2ME platform SDK 3.0
db

Why java is called platform independent

Hello
Why java is called as platform independent?Any body please give a detailed explanation since im a beginner to java technology.
ThankYou
Jk

BigDaddyLoveHandles wrote:
georgemc wrote:
SunFred wrote:
Java is not platform independent since it depends on the Java platform ;)Don't complicate matters!I always thought the phrase should have been "platform agnostic"It's a phrase I've used meself

Platform independency...any chance ?

hi...java code (.class files ) are platform independence. It is supposed to run any platform.(i believe this) [ // it is fine in different windows machine ].
However, i was in argue with my friend..... He told that each platform (windows,Unix,Macintosh) have different JVM . so there is a chance that the class file may be rejected by the JVM in different platform.
is it true ?
if Yes.......then independency is lost !!! i can not call it is a pure platform independent.......are people trying for any remedy ?

There are many different JVMs. Sun makes JVMs, IBM makes JVMs, M$ used to make JVMs, I think Blackdown makes JVMs, etc.
As long as a JVM matches the spec, then a given class file is portable across different VMs. Just like if I create a Word doc on the PC, I can read it with word on my Mac.
BUT (you knew there was going to be a "but", didn't you), there are different versions of VMs and the spec has changed over the years. Just like MS Word from 1990 probably won't read a document you create with the MS Word that you buy today, similarly you need to make sure the version of your class file is no newer than the VM. If the class file is an older version than the VM, it will generally work--they're backward compatible that way. Or is it forward compatible.
Also, there are things that are legal Java code that won't necessarily translate from one platform to another that well. GUI stuff can be slippery that way, I understand. Some other things too, but I forget what.
Is Java perfectly platform independent in that any class file generated anywhere anytime is guaranteed to run on any other VM? No, of course not.
Is it easy to create applications that you can run with no changes on Mac, Windows, Linux, Solaris, and maybe others that I'm not aware of? Absolutely. Many of the apps I've developed in the last few years have been developed and unit-tested on Windows (and even Mac to some extent) and run on Linux or Solaris, without me even needing to think about it. (Not that you never need to think about it, but it's not an overriding concern.)

Java(TM) ME Platform SDK 3.0 - Any hacks to add emulators to this?

Similar Messages

Maybe you are looking for