Changes between Version 4 and Version 5 of JLCAssistant

Show
Ignore:
Author:
edrishn (IP: 207.7.108.244)
Timestamp:
01/11/07 17:50:37 (4 years ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • JLCAssistant

    v4 v5  
    1 !JLCAssistant for years was the only Java to .Net translation tool.[[BR]] 
     1!JLCAssistant was the only Java to .Net translation tool for years.[[BR]] 
    22 
    3 It developed by [http://www.artinsoft.com/ ArtinSoft] and included / enhanced in Visual Studio by Microsoft. 
     3It was developed by [http://www.artinsoft.com/ ArtinSoft] and was included in Visual Studio by Microsoft. 
    44 
    5 Janett at first stages of development was a tool complement to !JLCA which fixes problems in resulting code.  
     5At the first stages of development, Janett was a tool complement to !JLCA fixing problems in resulting code.  
    66 
    7 [http://msdn2.microsoft.com/en-us/vstudio/aa718346.aspx Version 3.0] (bundled in Visual Studio 2005) fixes some !JLCA problems but focuses more on !APIs used in applications (!EJB, !JSP, !JMS,...). 
     7[http://msdn2.microsoft.com/en-us/vstudio/aa718346.aspx Version 3.0] (bundled in Visual Studio 2005) has fixed some !JLCA problems but focuses more on !APIs used in applications (!EJB, !JSP, !JMS,...). 
    88 
    99There are essential problems with !JLCA: 
     10 * It maps some classes and methods and leaves a lot of them unmapped. You can't use results with IKVM (Java libraries), and fixing them to use .Net libraries is time-consuming  
     11 * Number of manual changes required will be very large, so preserving them with tools like diff will be problematic in re-translation. 
     12 * It's slow. Translation takes tens of minutes for large projects. For example translating Commons Collections takes over 10 minutes. Janett can translate this project in ~35 seconds. 
    1013 
    11  * It leaves a lot of classes and methods unmapped. You can't use results with IKVM (Java libraries) and fixing them to use .Net libraries is time-consuming  
    12  * Number of manual changes required will be very large so preserving them with tools like diff will be problematic in re-translation. 
    13  * It's slow. Translation takes tens of minutes and even hours (in Version 2.0) for large projects. For example translating Commons Collections takes over 10 minutes. Janett can translate this project in ~35 seconds. 
    14