Hi all I want to mentioned that it is not important which API is used from JAVA to say that your application is a J2EE application or not. The only two thinks which count are 1) it is written in java (of course) and 2) it is a distributed application.
The API itsels like EJB, JNDI, JDBC, Java Servlets, hibernate, spring, etc is just to support the developer to develop a J2EE(distributed system) or other application and not to prove that this is a J2EE application or not. best regards Hans 2006/1/30, Peter Crowther <[EMAIL PROTECTED]>: > > > From: Jess Holle [mailto:[EMAIL PROTECTED] > > Nice terminology quandry that the app server marketeers have > > dug for us. > > > > They've painted a world of "J2EE == EJB" and "J2EE == the only (good) > > way to do Java in the enterprise" and transitively "EJB == the only > > (good) way to do Java in the enterprise". > > EJB implies J2EE, but the reverse implication does not hold. That > recognition is enough to defeat the marketing spin. > > - Peter > > P.S. So far to day, I've spent about half the day developing in C# and > ASP.Net, and the other half developing in Java and JSP. I find them > about as productive as each other, and neither as productive as one > would ideally like. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- mfg Hans Sowa mailto:[EMAIL PROTECTED]
