Title: destroyXlet() follows MHP directions

Number: 80

Specification reference: (Section 6.1.1.5 page 8)
“Applications SHALL follow the directions for this state transition as described in [MHP] clause 11.7.1.2:
• Cause any threads that they have created to exit voluntarily;
• Stop, deallocate and close any JMF players that they have created;
• Stop and destroy any JavaTV service selection ServiceContext objects that they created;
• Release any other scarce resources that they created, e.g., NetworkInterfaceControllers if they do any
tuning;
• Flush any images using the Image.flush() method;
• Xlets shall not cause any unnecessary delay in their Xlet.destroyXlet method;
• De-register any event listeners.
In addition to these tasks, an application SHALL terminate any active timers. Also, an application SHALL NOT sleep during destroyXlet()."

Assertions:
1. Within destroyXlet() the application causes any threads that they have created to exit voluntarily
2. Within destroyXlet() the application s tops, deallocates and closse any JMF players that they have created
3. Within destroyXlet() the application stops and destroys any JavaTV service selection ServiceContext objects that they created
4. Within destroyXlet() the application releases any other scarce resources that they created
5. Within destroyXlet() the application flushes any images using the Image.flush() method
6. Within destroyXlet() the application does not cause any unnecessary delay
7. Within destroyXlet() the application de-registers any event listeners
8. Within destroyXlet() the application terminates any active timers
9. Within destroyXlet() the application does not sleep

Test Procedures:
1. Manually inspect the source code.
2. Use Java reflection API or other tools to inspect the application .class files

Expected result
1. The appropriate invocations are found within destroyXlet()
2. The appropriate invocations are not found within destroyXlet()