XLet entry points do not intentionally block
Title: No intentional blocks in XLet entry points
Number: 10
Specification reference: (Section 6.1.1 page 6)
"There are five entry points defined by the Xlet interface.
- A no-argument constructor
- initXlet()
- startXlet()
- pauseXlet()
- destroyXlet() Applications SHALL NOT intentionally block, including invoking Thread.sleep, during any of these methods."
Assertions:
- The application no-argument constructor does not invoke java.lang.Object.Thread.sleep(long millis)
- In the initXlet() method the java.lang.Object.Thread.sleep(long millis) method is not invoked.
- In the startXlet() method the java.lang.Object.Thread.sleep(long millis) method is not invoked.
- In the pauseXlet() method the java.lang.Object.Thread.sleep(long millis) method is not invoked.
- In the destroyXlet() method the java.lang.Object.Thread.sleep(long millis) method is not invoked.
Test Procedures:
Task - Expected result
- Inspect the source code. - The invocation is not found. Alternative procedure Task - Expected result
- Use java Reflection API or other tools to inspect the class files. - The invocation is not found.
- Printer-friendly version
- Login or register to post comments


community