Other servlet containers will behave similarly.
其他servlet容器的表现与之类似。
All J2EE-compliant servlet containers accept WAR files and can deploy them.
所有遵从j2ee的servlet容器都接受WAR文件，并且可以部署这些文件。
All servlet containers must provide a readline method on their input streams.
所有的servlet容器必须在它们的输入流上提供readline方法。
The redeployment features of most servlet containers, application servers and OSGi implementations each work along the same lines.
大多数servlet容器、应用服务器和OSGi的重部署特性实现思路都类似。
The tag is like an extensibility mechanism that allows applications running inside servlet containers to do processing in conjunction with certain events.
标记就像一种可扩展性机制，允许在servlet容器内部运行的应用程序协同某些事件进行处理。
WAR files are simply JAR files with a bit of extra configuration information, built in a way that all servlet containers can deploy the application inside.
WAR文件只是JAR文件和一些额外的配置信息，以一种所有Servlet容器都能在里面部署应用程序的方式构建。
In addition, through projects such as WADI, session replication can be added to servlet containers such as Tomcat or Jetty through the servlet filtering mechanism.
此外，通过像WADI这样的项目，可以用servlet过滤机制将会话复制添加到像Tomcat或者Jetty这样的servlet容器中。
Servlet containers, such as Apache Jakarta Tomcat, implement the Servlet API, letting you build dynamic content into pages on the server that can then be sent to a Web browser.
Servlet容器（例如ApacheJakartaTomcat）实现了 ServletAPI，使您可以将动态内容建立到服务器页面中，该页面随后会被发送到Web 浏览器。
Servlet containers maintain no affinity between threads and sessions; the next request to come in on a given session will likely be serviced by a different thread than the current request.
Servlet容器没有保持线程与会话之间的联系；某个会话的下一个请求很可能由另一个不同的线程来处理。
Many servlet containers place a limit on the amount of memory that can be used across all sessions, and when that limit is reached, will serialize the least recently used session and write it to disk.
许多servlet容器对可以跨所有会话使用的内存的数量有一个限制，达到这个限制时，会序列化最先使用的会话并将它写到磁盘上。
This means that application developers who wish to use sessions are no longer forced to use Servlet or EJB containers if they don’t need them otherwise.
这意味着，那些希望使用会话的应用开发者，不必被迫使用Servlet或EJB容器了。
Whilst asynchronous support was available in Tomcat 6 through a non-standard API, standarisation means that the Servlet 3 version is portable between containers.
虽然异步支持在Tomcat6里就有了，但那是通过一个非标准的API实现的，标准化意味着Servlet3版本可移植到不同容器中。
Or, if using these containers, developers now have the option of using a unified and consistent session API in any tier, instead of servlet or EJB-specific mechanisms.
或者，如果正在使用这些容器，开发者现在也可以选择使用在任何层统一一致的会话api，取代Servlet或EJB机制。
The RestServlet servlet can run in a non-JAX-RS-aware servlet container, thereby supporting easy deployment of JAX-RS services to non-JAX-RS-aware containers.
RestServletservlet可以在“无jax -RS感知”的servlet容器中运行，从而支持将JAX - RS服务轻松部署到“无jax - RS感知”的容器中。
Sometimes there is a need to separate the servlet and EJB containers, such as for application security.
有时，需要分离servlet和ejb容器，比如出于应用程序安全性考虑。
Sometimes there is a need to separate the servlet and EJB containers, such as for application security.
有时，需要分离servlet和ejb容器，比如出于应用程序安全性考虑。
应用推荐