The servlets discussed in this chapter are primarily Dynamo servlets, meaning they are servlets that are created exclusively for use within Nucleus. For example, servlets that implement the PipelinableServlet or the DispatcherPipelineableServlet interface are Dynamo servlets.
Dynamo servlets should not be confused with J2EE servlets, which are servlets that run in a J2EE Web container and follow the standards defined by the J2EE specifications. J2EE servlets and filters can interact with the request in much the same way that Dynamo servlets can. Here are some key differences between them:
Dynamo servlets exist in the servlet pipeline, which is executed before the request reaches the J2EE Web container. J2EE servlets are executed by the Web container.
Dynamo servlets themselves determine their ordering, which also determines the circumstances in which they are called. J2EE servlets are defined in a central Web application deployment descriptor (called
web.xml), which is responsible for describing their order and the circumstances that cause their execution.
Use the type of resources that best suit your preferences. You may find J2EE servlets and filters a more portable and familiar technology in comparison to Dynamo 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.
