Originally posted by Ransika deSilva:
1) What is class file look up order? and do I have know about it other than knowing that you CAN'T change it in JTWI.
It's the order the class files will be loaded to the system. Since we will not have Custom Class loader in CLDC 1.1, we will not be able to change the order...
2)The Q is, is it possible to have a class for example, 'Connector' in a user package? so that there are 2 classes with the same name in different packages.
Unless you modified the original "Connector" class or extend it, it is possible that you include the javax.microedition.io package in your JAR... But who wants to do that, since it is already available in the device?
3) Do I have to know the Byte Code TypeChecker and its mechanism?
No, you don't need to know. It's out of exam topics...
4) Do I have to know the Runtime Verification step by step, I mean, first, memory is allocated for the types of the local variables and stack items and so on (from the spec)
Yes and No. You have to know how they work in overview... But you don't need to know the details of how memory are allocated for which local variables and so and so...
5) In the JTWI specification (4.8) "Compliant devices must implement a mechanism for selecting a phone number from the device phone book when the user is editing a TextBox or TextField and the constraint of the TextBox or TextField is TextField.PHONENUMBER. This requirement is voided if the phone book is not accessible", could you please explain this, cause I thought it is not possible to access the phone book through a J2ME program.
Actually, it is implementation-dependent. The device may or may not let you access the phone book, when you are using TextField.PHONENUMBER. If it lets you, when the user cursor is focus to that textfield, the entries from the phone book will automatically listed. Well, it depends on the implementation how the entries from phone book can be viewed... As a deveoper, you don't need to care about how to access the device phone book from your textfield... It may or may not be provided to the MIDlet, depending on the device policy...
Hope my explanation helps...