Home/ Questions/Q 684893
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T01:52:01+00:00

I work in a shop that is a mix of mostly Java and .NET

  • 0

I work in a shop that is a mix of mostly Java and .NET technologists. When discussing new solutions and architectures we often encounter impedance in trying to compare the various technologies, frameworks, APIs etc. in use between the two camps. It seems that each camp knows little about the other and we end up comparing apples to oranges and forgetting about the bushels.

While researching the topic I found this: Java –> .Net rough equivalents

It’s a nice list but it’s not quite exhaustive and is missing the key .NET 3.0 technologies and a few other tidbits. To complete that list: what are the near/rough equivalents (or a combination of technologies) in Java to the following in .NET?

  • WCF ~=
  • WPF ~=
  • Silverlight ~=
  • WF ~=
  • Generics ~=
  • Extension Methods ~=
  • Lambda expressions ~=
  • Linq (not Linq-to-SQL) ~=
  • TPL ~=
  • F# ~=
  • IronPython ~=
  • IronRuby ~=
  • …have i missed anything else?

Java Technologies (are there .NET equivalents?):

  • ~= EJB
  • ~= WebSphere
  • ~= GlassFish
  • ~= JBoss App Server
  • ~= Tomcat?

Note that I omitted technologies that are already covered in the linked article. I would also like to hear feedback on whether the linked article is accurate.

Note: This seems to be turning into a wiki-type article so i marked it as such.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    .NET –> Java

    Java –> .NET

    • EJB ~= MTS/COM+
    • WebSphere AS, GlassFish, JBoss AS are all concrete Java EE API implementations. The .NET equivalent would be IIS with at least MTS/COM+ support (is there by the way competition for IIS?).
    • Tomcat is a webcontainer aka servletcontainer, it only implements the Web Component part of the huge Java EE API (basically only the javax.el and javax.servlet parts, the JSP/EL and Servlet API). The .NET equivalent would be still IIS, but then without support for MTS/COM+, mail, message queue, persistence and more. I.e. only a simple web server for pure “Classic ASP”.
    • 0