Siemens AC65 User Manual
Java User’s Guide
11.3 Java IDE
97
s
wm_java_usersguide_v12
Page 75 of 123
2008-02-25
Confidential / Released
11.3
Java IDE
The SMTK is integrated into your Java IDE during installation. Please note that the IDE inte-
gration is intended to create MIDlets suitable for the Java enabled module and for debugging
using the emulator. JAR files used in the module must be configured according to the batch file
examples given. If the SMTK install succeeded, you can easily switch between the Siemens
environment and Standard-JDK environment, the special libraries/APIs and emulators are
available, and AT commands can be sent to the module. Regular function of the IDE for non-
Siemens projects is unchanged.
gration is intended to create MIDlets suitable for the Java enabled module and for debugging
using the emulator. JAR files used in the module must be configured according to the batch file
examples given. If the SMTK install succeeded, you can easily switch between the Siemens
environment and Standard-JDK environment, the special libraries/APIs and emulators are
available, and AT commands can be sent to the module. Regular function of the IDE for non-
Siemens projects is unchanged.
Using the debugger please keep in mind that the MIDlet-URL, included in the Jad file, has to
indicate and store the location where the emulator will find the corresponding Jar file. Generally
the location will only be the file name for the Jar file.
indicate and store the location where the emulator will find the corresponding Jar file. Generally
the location will only be the file name for the Jar file.
If you are using Eclipse IDE the location of the Jar file is “deployed\<filename>.jar”. Please
check this path name inside the Jad file before starting a debugging session with Eclipse IDE
and change it manually, if the “deployed” subdirectory is missing. Please keep in mind, that the
subdirectory “deployed” is used as a default setting in the Eclipse IDE and can be changed by
the user within the Eclipse menu.
check this path name inside the Jad file before starting a debugging session with Eclipse IDE
and change it manually, if the “deployed” subdirectory is missing. Please keep in mind, that the
subdirectory “deployed” is used as a default setting in the Eclipse IDE and can be changed by
the user within the Eclipse menu.
While using "on-device debugging" the ME is restarted after the end of each debugging ses-
sion. This is independent of the used IDE (Eclipse 3.0.1, Eclipse 3.0.2, Eclipse 3.1.0, Eclipse
3.1.1, Eclipse 3.1.2, Eclipse 3.2.x
sion. This is independent of the used IDE (Eclipse 3.0.1, Eclipse 3.0.2, Eclipse 3.1.0, Eclipse
3.1.1, Eclipse 3.1.2, Eclipse 3.2.x
10
, NetBeans IDE 5.0, NetBeans 5.5.x
, JBuilder X, JBuilder
2005, JBuilder 2006 Enterprise/Developer).
Please note that the USB port has to be disconnected manually before the module is restarted,
in case of using a connected terminal program on USB port for directing the Java “System.out”.
It is recommended to use ASC0 or ASC1 for directing Java “System.out” to avoid closing man-
ually the COM port.
in case of using a connected terminal program on USB port for directing the Java “System.out”.
It is recommended to use ASC0 or ASC1 for directing Java “System.out” to avoid closing man-
ually the COM port.
Please keep in mind, that it is not possible to use obfuscated files for a debugging session.
When writing and debugging a midlet be aware of the midlet life cycle (see
Life Cycle”).
11.3.1
NetBeans IDE 5.0, NetBeans 5.5 or NetBeans 5.5.x
Integration for NetBeans IDE 5.5 and 5.5.x is only supported for TC65. The described steps for
using Netbeans IDE 5.0 are identical for NetBeans IDE 5.5 and Netbeans 5.5.x.
using Netbeans IDE 5.0 are identical for NetBeans IDE 5.5 and Netbeans 5.5.x.
This section indicates the changes to your IDE you will see after integrating the SMTK and
describes how to exploit these features to build and debug your applications.
All installed emulators can be found using the NetBeans IDE 5.0 menu
Tools
describes how to exploit these features to build and debug your applications.
All installed emulators can be found using the NetBeans IDE 5.0 menu
Tools
→
Java Platform Manager. See
10.
only supported for TC65