FAQFAQ
| Q.1 | What tools are available for creating Java applications? |
|---|---|
| A.1 | A number of free tools such as SunOne Studio 4, Mobile Edition and the Java ME WirelessToolkit both from Sun Microsystems Inc. as well as the commercially available JBuilder from Borland Inc. can be used for developing MIDP compatible Java applications. NTT DoCoMo, KDDI, and Vodafone KK each provide their own development environment for creating Java applications for their mobile phones. In addition, Zentek Technologies Japan provide an integrated development environment for creating i-mode Java applications called i-JADE. |
| Q.2 | Is there a package available for evaluating JBlend™ [micro]? |
| A.2 | We can provide evaluation licenses. Please contact us for more information. |
| Q.3 | What do you mean by embedding JBlend™ on a device? |
| A.3 | To put it simply, in the case of JBlend™ [micro], embedding JBlend™ on a device refers to the work required to implement the application management software and the device manufacturer's module. Once these have been implemented, the target device will have a Java Runtime Environment capable of running Java applications. |
| Q.4 | Are there any differences in the embedding process and systems requirements for the standard version of JBlend™ [micro] and JBlend™ [micro] with acceleration support? |
| A.4 | The differences are very minor. For example, when embedding this version of JBlend™ [micro] with support for ARM Co. Ltd's Jazelle CPU, the total number of functions that must be implemented is slightly more (although this does depend on the target device), The systems requirements (for example memory required) are also basically the same as for the version of JBlend™[micro] without support for acceleration. |
| Q.5 | Does the version of JBlend™ [micro] with the additional device-resident debugging feature always run in debug mode? |
| A.5 | No. The debug function can be turned on and off. When it is switched off the execution speed and Java heap size are the same as the version of JBlend™ [micro] without debugging functionality. In addition we can provide versions of JBlend™ [micro] both with and without debugging functionality. For example, during development you may want to use the version of JBlend™ [micro] with the debugging feature while your shipped products could run the version without debugging. |
| Q.6 | What should I do if I want to add class libraries controlled by my company such as OEM extensions? |
| A.6 | Have a look at our External Class Libraries Framework. This is an option that allows class libraries created by device manufacturers to be added to the platform. This enables class libraries specified by a JSR or third-party class libraries to be added, including completely original class libraries developed for specific devices and functionality: e.g. rice-cooker API or CD player API etc. Please contact us for more information. |
| Q.7 | Is there any way to directly operate a device from inside a Java application? |
| A.7 | Yes, with JBlend™ [micro]'s optional External Class Libraries Framework there is. The External Class Libraries Framework contains features enabling the use of a native method interface and the KNI. Either of these functions can be used to give the platform greater functionality, enabling the calling of native code from inside Java applications. The External Class Libraries Framework also includes functionality allowing a device to notify a Java application of customized events. |
| Q.8 | What are the differences between the native method interface in the External Class Libraries Framework and the KNI? |
| A.8 | The native method interface provided by Aplix was designed to be simpler than the KNI and easier to use. However, the KNI is sometime more appropriate for certain kinds of complex device control operations. Both the native method interface and the KNI are included within the External Class Libraries Framework allowing device manufacturers to choose the one that is more appropriate each time. |
| Q.9 | Does JBlend™ use bytecode interpretation? |
| A.9 | JBlend™ offers both interpreted (CLDC based) and compiled (CLDC HI based) solutions. |
| Q.10 | Can I download a JBlend™ SDK? |
| A.10 | Some of our customers offer their developers SDKs with JBlend™ included. Please refer to the following list as an example:
|
| Q.11 | Does JBlend™ [embedded] support pJava and eJava? |
| A.11 | Yes. JBlend™ [embedded] is most recently supporting CDC or CDC HI, but with a variety of shipping pJava and eJava devices dating back to 1999 with the first ever Java deployment in a consumer electronics device. |
| Q.12 | Why should I use Java in my consumer electronics product? |
| A.12 | Java was designed to reduce portability issues and enhance code-reuse. Using Java helps manufacturers focus on innovative new features and overall product quality without having to re-invent basic user-interface concepts for each product. |
