Microsoft.NET and J2EE Technology Map

Table 1.1 shows a technology map between the .NET Framework and the J2EE specification. This table is meant to be used for looking up the corresponding product or feature set on the other platform. Use the table to understand the fundamentals described in this book, not to compare and contrast the two technologies. Also be aware that many of the rows in this table do not represent one-to-one mappings. For example, MSMQ is a product, whereas JMS is an API.

Table 1.1: Microsoft .NET and J2EE Technology Map

Service or Feature	Microsoft .NET (Product or Framework Class)	J2EE (API or Vendor Product)
Client-side GUI/forms	WinForms	AWT/SWING
Web GUI	ASP.NET	JSP
Web scripting	ISAPI, HttpHandler , HttpModule	Servlet, Filter
Web application hosting	Internet Information Services (IIS)	Multiple possibilities, including Apache Tomcat, and vendor-specific servers
Server-side business logic component	Serviced Component (COM+)	Session Bean
Server-side data component	Serviced Component (COM+) with Database Logic	Bean Managed Persistence (BMP) Bean
Server-side data component	Third-Party Solution	Container Managed Persistence (CMP) Bean
Directory access	ADSI (via LDAP)	JNDI (via LDAP)
Remote invocation	.NET Remoting	RMI-IIOP
Data access	ADO.NET	JDBC, SQL/J
Messaging	MSMQ	JMS
Transactions	COM+/DTC	JTA