anchor.diff:  
   === Deploying to Apache Tomcat
   
  -Servlet containers are not required to support Java EE services like
  +Servlet containers are not required to support Jakarta EE services like
   CDI. However, you can use CDI in a servlet container like Tomcat by
   embedding a standalone CDI implementation such as Weld.
   
   Weld comes with servlet integration extension which bootstraps the CDI
   environment and provides injection into servlets components. Basically,
  -it emulates some of the work done by the Java EE container, but you
  +it emulates some of the work done by the Jakarta EE container, but you
   don't get the enterprise features such as session beans and
   container-managed transactions.
   
  
positive.code: for more info).
  
  Let's give the Weld servlet extension a spin on Apache Tomcat. First,
  you'll need to download Tomcat 9.0.11 or later from
  http://tomcat.apache.org/download-90.cgi[tomcat.apache.org] and extract
  it.
  
  [source, console]
  ---------------------------------
  $> unzip apache-tomcat-9.0.11.zip
  ---------------------------------
  
  The Maven plugin communicates with Tomcat over HTTP, so it doesn't care
  
negative.code: a web (war) example containing only non-transactional managed beans.
  This example can be run on a wide range of servers, including WildFly,
  GlassFish, Apache Tomcat, Jetty, and any compliant
  Jakarta EE 10 container. Translator is an enterprise (ear) example that
  contains session beans. This example must be run on WildFly 27 or better,
  GlassFish 7 or better, or any compliant Jakarta EE 10 container.
  
  Both examples use JSF 4.0.0 as the web framework and, as such, can be
  found in the `examples/jsf` directory of the Weld distribution.
  
  === Prerequisites
  