Java MIDlet API Forums

« Back to Technical Discussion

RE: 7926G Emulator and NetBeans 7.1.1

Combination View Flat View Tree View
Threads [ Previous | Next ]
Post New Thread
toggle
7926G Emulator and NetBeans 7.1.1
Answer
4/13/12 9:56 AM
Are there any compatibility issues with the 7926G emulator and the latest version of Netbeans?
 
Using  the 7926G Emulator Skin Guide for installation of the emulator skin, I get the following error message in device-manager.log:
 

[    736]  DEBUG - un.jme.toolkit.bootstrap.Batch - Initializing object device-adapter.Cisco7926 
[    736]  DEBUG - strap.BasicObjectConfiguration - Setting field name to device-adapter.Cisco7926 using class com.sun.jme.toolkit.propertyeditors.StringEditor 
[    736]  DEBUG - strap.BasicObjectConfiguration - Setting field deviceRegistrationManager 
[    737]  DEBUG - strap.BasicObjectConfiguration - Setting field deviceAdapter 
[    737]   WARN - strap.BasicObjectConfiguration - Could not find object device-class-adapter-CldcFxEmulator 
[    738]  ERROR - oolkit.bootstrap.MainNamespace - java.lang.IllegalArgumentException: Could not find object device-class-adapter-CldcFxEmulator 
java.lang.IllegalArgumentException: Could not find object device-class-adapter-CldcFxEmulator
at com.sun.jme.toolkit.bootstrap.BasicObjectConfiguration.initializeField(Unknown Source)
at com.sun.jme.toolkit.bootstrap.BasicObjectConfiguration.initializeField(Unknown Source)
at com.sun.jme.toolkit.bootstrap.BasicObjectConfiguration.initializeFields(Unknown Source)
at com.sun.jme.toolkit.bootstrap.ObjectConfiguration.initializeObject(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Batch.initializeObject(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Batch.initializeObjects(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Namespace.startBatch(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Namespace.runModules(Unknown Source)
at com.sun.jme.toolkit.bootstrap.MainNamespace.runModules(Unknown Source)
at com.sun.jme.toolkit.bootstrap.MainNamespace.run(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Container.run(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Container.start(Unknown Source)
at com.sun.jme.toolkit.bootstrap.Container.main(Unknown Source)
[    739]   INFO - un.jme.toolkit.bootstrap.Batch - Flushing... 
Flag

RE: 7926G Emulator and NetBeans 7.1.1
Answer
4/20/12 7:18 PM as a reply to Ove Angelshaug.
Is the default emulator/skin working?  Only the 7926 skin is failing?
Flag

RE: 7926G Emulator and NetBeans 7.1.1
Answer
5/16/12 3:21 PM as a reply to Ove Angelshaug.
I couldn't get the 7926G emulator to work with the latest release of NetBeans 7.x. It's working just fine after downgrading to NetBeans 6.9.1.
Flag

RE: 7926G Emulator and NetBeans 7.1.1
Answer
7/3/12 9:27 PM as a reply to David Staudt.
Is the default emulator/skin working?  Only the 7926 skin is failing?

 
The default emulator works for me on NetBeans 7.2RC1; loading the new emulator doesn't work - it doesn't show up in the list of emulators.
Flag

RE: 7926G Emulator and NetBeans 7.1.1
Answer
7/12/12 10:51 PM as a reply to Kevin Penrose.
After some testing we've found that the 7926 skin will work with the following:
 
- Netbeans 7.1.2 (latest)
- Oracle Wireless Toolkit 3.0 (latest is 3.0.5)
 
Two caveats of note:
 
- The 'complete' Netbeans installation includes the Mobility features, and automatically installs the complete WTK 3.0.5.  It may be possible to also install the WTK 3.0 side-by-side, but care must be taken to install the 7926 skin files only in the WTK 3.0 SDK area.  In our setup we installed the base Netbeans 7.1.2, then added the Mobility plugin and installed the standalone WTK 3.0.
- After adding the 7926 skin files to the WTK 3.0 directory structure, the 'Java ME SDK 3.0 Device Manager' tray icon must be 'Exit'-ed before restarting Netbeans and performing the 'Manage Emulators/Refresh' sequence.
 
We are evaluating further updates to the skin to work with WTK 3.0.5, but the above at least allows use of the latest Netbeans.
Flag

 Go
By API/SDK: