Hello,
Microsoft is committed to helping customers and developers with this
migration to minimize disruption. Because every organization has different
requirements, businesses and developers should tailor the options that are
most appropriate to fit their own particular needs. Your organization may
decide to select one or more of the following migration options for
migrating Java applets and applications:
Migrate to Microsoft .NET. Microsoft recommends this option because we will
be able to support customers making the migration. Migrating to .NET may
require access to source code.
Migrate applets to other rendering technologies. Although Microsoft cannot
vouch for the security and reliability of solutions offered by other
companies, several offer rendering technology that can be viewed in a
number of browsers. Technology options include Microsoft ASP.NET, DHTML,
Macromedia Flash, and others. Migrating to other rendering technologies
requires access to source code.
Lock down Microsoft Internet Explorer security zones while continuing to
use the MSJVM. Locking down security zones allows for limited usage of the
MSJVM even after it becomes unsupported while helping to limit security
risks by restricting the use of MSJVM to specific sites. This can be done
in parallel with other migration options.
Switch to a third-party Java runtime Environment (JRE). Although Microsoft
cannot vouch for the security and reliability of solutions offered by other
companies, non-Microsoft solutions are available. Customers choosing to
explore such solutions should engage in testing prior to pursuing this
migration path.
Review a list of vendors offering alternative JRE solutionsDevelopers and
IT professionals should download the MSJVM Transition Guide, which provides
the technical information necessary to identify dependencies and to choose
appropriate
http://www.microsoft.com/mscorp/java/faq.asp
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.