Top 3 Java-to.NET Interoperatability Issues

As firms try to make Java / J2EE work with .NET, the top 3 Java-to.NET Interop Issues they face, as compiled by Identify Solutions are:

  1. Problem Isolation
  2. Performance bottlenecks
  3. Communication challenges

Other issues that were noted:

  • Data capture
  • Addressing configuration problems
  • Team interop approaches may not align
  • Cross-platform skill sets

Reference:
>> Users Cite Top Java-to.NET Interop Issues

The following two tabs change content below.
Content Team

Content Team

The IndicThreads Content Team posts news about the latest and greatest in software development as well as content from IndicThreads' conferences and events. Track us social media @IndicThreads. Stay tuned!
Content Team

Content Team

The IndicThreads Content Team posts news about the latest and greatest in software development as well as content from IndicThreads' conferences and events. Track us social media @IndicThreads. Stay tuned!

  • Noname

    Brings up these issues for J2EE:
    1) Big and Heavy Application Servers -> it depends on your requirements. Do you need clustering, zero downtime, security constraints, messaging, distributed computing etc.?

    2) Top-controlled decision making on the platform -> Ever heard from JCP?

    3) Not easy to deploy -> Ever heard from Ant build tool?

    4) Costly -> Ever heard from JBoss, Jonas, Geronimo, Tomcat?

    5) Slow development of the platform -> Ever heard from Ant, XDoclet, Eclipse?