Comparing .NET and J2EE Features

Table 2.2 shows a comparison of features and functions in .NET and J2EE. However, differences in the background makeup of each platform make direct comparisons between .NET and J2EE not always applicable. For example, MSMQ is a product whereas JMS is an API. Therefore you cannot simply rip out one component and replace it with the equivalent from the other platform.

Table 2.2: Comparison Between .NET and J2EE Functionality
Feature or ServiceMicrosoft .NET ElementJ2EE ElementComments
Technology TypeProductStandard
Middleware VendorsMicrosoft and partners50+ vendors
Client Side GUIWindows Forms EnvironmentAWT/SWINGSWING/AWT are part of J2SE
Web ScriptingISAPI
HttpHandler HttpModule
Web Application HostingInternet Information ServerMultiple (depends on vendor implementation)J2EE examples include Apache Tomcat
Server Side Business Logic Component.NET Class or Serviced Component (COM+)EJB Session Beans
Server Side Data Components 1Serviced Component with DB LogicEJB with Bean Managed Persistence
Server Side Data Components 2ADO.NET Data Set EJB with Container Managed PersistenceOnly an approximate equivalence
Directory AccessActive Directory Services Interface (ADSI) through LDAPJava Naming and Directory Service (JNDI) through LDAPLDAP compatibility makes switching between directory services very easy.
Remote Invocation.NET RemotingRMI-IIOP
MessagingMicrosoft Message QueuingJMSMicrosoft Message Queuing is a product. JMS is a specification, and therefore requires an underlying implementation.
Transactional SupportCOM+/Distributed Transaction Controller (DTC)JTA

Application Interoperability. Microsoft. NET and J2EE
Application Interoperability: Microsoft .NET and J2EE: Microsoft(r) .Net and J2ee (Patterns & Practices)
ISBN: 073561847X
EAN: 2147483647
Year: 2003
Pages: 104 © 2008-2017.
If you may any questions please contact us: