Title: Self termination follows MHP directions

Number: 90

Specification reference: (Section 6.1.1.5 page 8)
“An application can terminate itself by calling XletContext.notifyDestroyed(). In this case, the implementation willNOT call the destroyXlet() entry point, so the application SHOULD perform all of these functions before calling notifyDestroyed().”

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