I have heard of J2EE compliance for EJB servers. What does J2EE complaince means for applications that don't use EJB but use other technologies such as JMS, JNDI, JDBC, Servlets & JSP. Is J2EE compliance a nice way of saying "we are you using an expensive app server?"
Is J2EE compliance a nice way of saying "we are you using an expensive app server?" Sounds about right Keep in mind that J2EE merely tells you that you have a certain minimum environment to work with: EJB, JSP, Servlets, JavaMail, JDBC, JNDI, etc. A J2EE compliant application can use all or part of these APIs as appropriate to do its job. I don't think there is a law which dictates certain parts you have to use. If it runs correctly inside any J2EE compliant server, it's a J2EE compliant application. (In fact there are quite a few glitzy, supposedly-bleeding-edge J2EE gizmos out there which really are very crude applications using Model 1 JSP and plain JDBC). - Peter
[This message has been edited by Peter den Haan (edited May 08, 2001).]
subject: How can an application be J2EE complaint?