Discussions

News: Stryon announced iNet: Tool converts .Net code to Java bytecode

Bookmark and Share Get thread feed

  1. Stryon announced iNet: Tool converts .Net code to Java bytecode (11 messages)

    • Posted by: Dion Almaer
    • Posted on: August 12 2004 13:30 EDT
    Styron has announced iNet, which seems to be a product which takes .Net intermediate code, and converts it to Java bytecode. They have also converted the .Net class libraries, else there wouldn't be much use.

    The company claims:

    "Applications can be redeployed to Java application servers such as IBM WebSphere, BEA WebLogic, or JBoss."

    However, converting bytecode is only one step in the path. You still need to setup the deployment descriptors... etc etc.

    Tool converts .Net code to Java
    Reply to this

    Threaded Messages (11)

  2. .NET Framework EULA[ Go to top ]

    Does anyone know if this product from Sytron violates any part of the .NET Framework EULA?
    Reply to this Reply to original

  3. .NET Framework EULA[ Go to top ]

    Probably not since the .Net intermediate language is an ECMA standard and they could have converted the Mono class libraries which are open source and could be converted to Java byte code without violating the Mono license.
    Reply to this Reply to original

  4. Stryon announced iNet: Tool converts .Net code to Java bytecode[ Go to top ]

    Interesting...

    Yet I believe the oposite translation would be just as much useful, if not even more usefull.

    Regards,
    Olivier Refalo
    Reply to this Reply to original

  5. IKVM[ Go to top ]

    http://www.go-mono.org/images/ikvm-screenshot.png
    Reply to this Reply to original

  6. Stryon announced iNet: Tool converts .Net code to Java bytecode[ Go to top ]

    I agree. There is little value in transforming .NET MSIL into Java bytecode as there are much less mature .NET apps then Java. Also Java libraries are much much better and mature then .NET (this is major Java strength I believe, even more important then platform independence).

    Converting .NET libraries to Java bytecode??? What an oximoron!

    MC
    Reply to this Reply to original

  7. Mature or not, there is real value here...[ Go to top ]

    For client-side development, it makes perfect sense. If there is a custom control built in a .Net language that I'd like to use in my Java Swing or SWT application, something like this would give me a way to do that easily.

    For server-side development, this would give me the ability to throw away IIS and host my applications on a real app server, such as WebSphere, WebLogic, Orion, JonAS, JBOSS, Geronimo, and so on.
    Reply to this Reply to original

  8. Stryon announced iNet: Tool converts .Net code to Java bytecode[ Go to top ]

    Totally disagree. That should make consumption of e.g. a COM library very easy:
    1. create .Net Interop assemblie
    2. create Java wrapper using the INet tool
    3. use COM from Java

    A lot of customers of us ask for Java APIs to our products, which are somewhat COM heavy. Using JNI or tools like dtjcb are pretty clumsy to create a Java wrapper.

    Another use case for a tool like this would be to go away from the "Interoperability by use of Webservices" scenario, which is nice on the drawing board, but pretty slow.
    Reply to this Reply to original

  9. Stryon announced iNet: Tool converts .Net code to Java bytecode[ Go to top ]

    The reverse is also possible. Check out:
    http://www.ikvm.net/
    Reply to this Reply to original

  10. Visual MainWin for J2EE[ Go to top ]

    Checkout http://www.mainsoft.com/products/vmw_j2ee.html for something similar.
    Reply to this Reply to original

  11. Bridging Java/J2EE and .NET, Bridging Java/J2EE and COM[ Go to top ]

    I recently found Intrinsyc's J-Integra for .NET and J-Integra for COM.

    J-Integra for .NET is a bidirectional interoperability bridge between Java/J2EE and .NET. It "enables your .NET software to access existing Java/J2EE applications as though they were actually .NET applications. It is fully bi-directional, which means that your Java/J2EE software can also access .NET components as though the .NET components were written with Java."

    J-Integra for COM is a bidirectional interoperability bridge between Java/J2EE and COM. It allows Java accessing COM component through either DCOM or native interface, as well as COM component written in VB/VC++ accessing Java object through either DCOM or native interface.

    http://j-integra.intrinsyc.com
    Reply to this Reply to original

  12. Bridging Java/J2EE and .NET, Bridging Java/J2EE and COM[ Go to top ]

    BTW, you can also use ASP to access any Java objects using J-Integra for COM, even with zero client installation. Pretty neat...
    http://j-integra.intrinsyc.com/com/doc/#asp_java/zero_client.htm
    Reply to this Reply to original