This page has been automatically generated by Cargo's build. Do not edit it directly as it'll be overwritten next time it's generated again.

Jetty 12.x onwards support various versions of Jakarta EE, by adapting the JettyPropertySet.MODULES and JettyPropertySet.DEPLOYER_EE_VERSION configuration properties accordingly.

Users of the Jakarta EE 9 and above versions should be aware that, as a result of the move from Java EE to Jakarta EE as part of the transfer of Java EE to the Eclipse Foundation, the primary package for all implemented APIs has changed from javax.* to jakarta.*. This will almost certainly require code changes to enable applications to migrate to EE 9 and later.

In addition to the forementioned properties, this container configuration can also set up datasources and/or resources.

For more details, please read: DataSource and Resource Support.

Since the Jetty 12.x jetty-plus modules are specific to EE versions, datasources and resources are deployed using each application's context.xml file, matching the EE version.

The below are hence pre-requisites to using datasources or resources in Jetty 12.x:

• JettyPropertySet.DEPLOYER_CREATE_CONTEXT_XML must must be set to true.
• JettyPropertySet.MODULES must contain the right jetty-plus modules for the application(s) in scope.
• JettyPropertySet.DEPLOYER_EE_VERSION must be set aligned with the jetty-plus module EE version mentioned above.

Jetty 9.x and above can be configured to run under a Java Security Manager.

For further information on how to achieve this, please refer to the associated tip in the Maven 3 Plugin Tips page.