The servlets discussed in this chapter are primarily ATG servlets created for use only in Nucleus. ATG servlets are distinct from J2EE servlets, which run in a J2EE web container and follow the standards defined by the J2EE specifications. While J2EE servlets and filters can interact with requests much like ATG servlets, they differ in key respects:
ATG servlets exist in the servlet pipeline, which executes before the request reaches the J2EE web container. J2EE servlets are executed by the web container.
ATG servlets themselves determine the order in which they execute. The application deployment descriptor
web.xml
describes the order and conditions in which J2EE servlets execute.
Use the type of resources that best suit your preferences. You might find J2EE servlets and filters a more portable and familiar technology in comparison to ATG servlets.
The J2EE specifications describe how to create J2EE servlets and filters. For information on how to implement J2EE resources in the ATG platform, see Accessing Nucleus in a Web Application.