The JSP would be ASPX, essentially, with some difference in the byte compile
and coding methodology.
There is no direct EJB equivalent. You would most likely end up with a
combination of Framework components and custom classes, in your solution.
JDBC and ADO.NET - sort of. But JDBC is, technically, a bit more focused on
the connectivity, much like ODBC. You can use ODBC with ADO.NET, and it is
possible to do the same with JDBC. But, many Java developers call more than
the data conn stack JDBC, so ADO .NET could be an equivalent, if that is the
case. The portion of ADO.NET that sits in the client namepaces, like
SqlClient and OracleClient is technically closer to JDBC, but there are
still some differences.
Much of what you are looking at in Java are Frameworks built on top of the
language. The Framework direction for Sun and Microsoft are widely
different.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************
Think Outside the Box!
************************************************
"Frank Rachel" <fr*****@navisys.com> wrote in message
news:%2******************@TK2MSFTNGP09.phx.gbl...
So I can focus on the correct areas of research, I was wondering if
someone could give me the .NET equivelents for this J2EE architecture:
JSP's make calls to local JavaBean Controls. The controls do a JNDI lookup
to invoke methods on EJB's. The EJB's use local Java classes, and these
classes use JDBC to do database work.
Example:
Login.jsp contains "import xxx.LoginControl", and invokes the "login"
method.
LoginControl.login does a JNDI lookup for "LoginWorker", which is an EJB.
It invokes the "login" method of the EJB
LoginWorker.login does some stuff, and eventually calls
LoginDataSource.login, which uses JDBC to talk to the database.
What would be the appropriate areas of .NET to concentrate on? (JSP->ASPX,
EJB->?, JDBC->ADO?)
Whats the equivalent of the "Application Server" (WebSphere/etc)?
Thanks.
