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:

  1. The application no-argument constructor does not invoke java.lang.Object.Thread.sleep(long millis)
  2. In the initXlet() method the java.lang.Object.Thread.sleep(long millis) method is not invoked.
  3. In the startXlet() method the java.lang.Object.Thread.sleep(long millis) method is not invoked.
  4. In the pauseXlet() method the java.lang.Object.Thread.sleep(long millis) method is not invoked.
  5. In the destroyXlet() method the java.lang.Object.Thread.sleep(long millis) method is not invoked.

Test Procedures:

Task - Expected result

  1. Inspect the source code. - The invocation is not found. Alternative procedure Task - Expected result
  2. Use java Reflection API or other tools to inspect the class files. - The invocation is not found.