Updated: July 11, 2020 (February 18, 2002)
Charts & IllustrationsPros and Cons of Java Migration Products
Developers who have existing Java code that they want to move to .NET have two alternatives for migrating that code. The following chart identifies some of the pros and cons of using Visual J# or the Java Language Conversion Assistant (JLCA).
| Application Type | Visual J# | JLCA |
| Visual J++ using Sun APIs | Success depends on the amount of non-core APIs used.
Neither tool designed to address the entire set of Java APIs. Application code stays in Java. Some questions about long-term support from Microsoft. |
Success depends on the amount of non-core APIs used.
Neither tool designed to address the entire set of Java APIs. Enterprise Edition has potential to address wider set of APIs, such as EJB. Application code is converted to strategic Microsoft technologies (C# and .NET APIs). |
| Visual J++ using WFC (Windows-specific) APIs | Most applications will run with little to no modification.
Application code continues to use WFC, which is an obsolete API set. |
Most applications |
Atlas Members have full access
Get access to this and thousands of other unbiased analyses, roadmaps, decision kits, infographics, reference guides, and more, all included with membership. Comprehensive access to the most in-depth and unbiased expertise for Microsoft enterprise decision-making is waiting.
Membership OptionsAlready have an account? Login Now