Content deleted Content added
the |
→Criticisms: fair |
||
Line 14:
Another point of confusion is that in platforms supported as of 2008, examples such as the SvcDispXlet example in this [http://java.sun.com/developer/technicalArticles/javatv/apiintro/ online introduction] to Java TV circa 2001 are still not deployable because it uses AWT widgets such as java.awt.Button . Most such platforms and BD-J implement Personal Basis Profile with no AWT widgets, as opposed to Personal Profile which includes the widgets.
Sun's reference implementation for Java TV attempts to limit its exposure to support issues to the full [[Java Media Framework]] by having its own small version of JMF that it internally referred to as "jmflite". As with the limitations of the [[MIDP]] emulators that Sun provides, the [[Java TV]] reference implementation provide by Sun has not been updated to make provisions for later JDK's such as removing calls to Thread.stop()
▲As with the limitations of the [[MIDP]] emulators that Sun provides, the [[Java TV]] reference implementation provide by Sun has not been updated to make provisions for later JDK's such as removing calls to Thread.stop() which was made a "final" method in Java 1.5 (meaning that classes which extend Thread and override stop() will fail at runtime in a JRE 1.5). This implies that Sun has not yet made public its plans or a roadmap for the notion that Java ME will ever go beyond JRE 1.3. To be fair, if the upgrade of Java ME to JDK 1.5 or 1.6 ever happens, it will require some work on the part of all vendors of Java ME-enabled devices.<ref>[http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Thread.html#stop() JRE 1.5 Thread.stop() javadoc]</ref><ref>[http://java.sun.com/j2se/1.5.0/docs/guide/misc/threadPrimitiveDeprecation.html Why Are Thread.stop, Thread.suspend, Thread.resume and Runtime.runFinalizersOnExit Deprecated?]</ref>
==Notes==
| |||