Jakarta EE 9 migration

Upgrades many dependency declarations; removes old EJB 2.x support and outdated Servlet-based integrations (Commons FileUpload, FreeMarker JSP support, Tiles).

Closes gh-22093
Closes gh-25354
Closes gh-26185
Closes gh-27423
See gh-27424
This commit is contained in:
Juergen Hoeller
2021-09-17 09:14:07 +02:00
parent 5822f1bf85
commit d84ca2ba90
1291 changed files with 4992 additions and 25322 deletions

View File

@@ -251,7 +251,7 @@
As of 5.0 this executor is also used when a controller returns a reactive type that does streaming
(e.g. "text/event-stream" or "application/x-ndjson") for the blocking writes to the
"javax.servlet.ServletOutputStream".
"jakarta.servlet.ServletOutputStream".
]]></xsd:documentation>
<xsd:appinfo>
@@ -1041,15 +1041,6 @@
]]></xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="tiles" type="urlViewResolverType">
<xsd:annotation>
<xsd:documentation><![CDATA[
Register a TilesViewResolver based on Tiles 3.x.
To configure Tiles you must also add a top-level <mvc:tiles-configurer> element
or declare a TilesConfigurer bean.
]]></xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="freemarker" type="urlViewResolverType">
<xsd:annotation>
<xsd:documentation><![CDATA[
@@ -1118,62 +1109,6 @@
</xsd:complexType>
</xsd:element>
<xsd:element name="tiles-configurer">
<xsd:annotation>
<xsd:documentation><![CDATA[
Configure Tiles 3.x by registering a TilesConfigurer bean.
This is a shortcut alternative to declaring a TilesConfigurer bean directly.
]]></xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="definitions" minOccurs="0" maxOccurs="unbounded">
<xsd:complexType>
<xsd:attribute name="location" type="xsd:string" use="required">
<xsd:annotation>
<xsd:documentation><![CDATA[
The location of a file containing Tiles definitions (or a Spring resource pattern).
If no Tiles definitions are registered, then "/WEB-INF/tiles.xml" is expected to exists.
]]></xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="check-refresh" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation><![CDATA[
Whether to check Tiles definition files for a refresh at runtime.
Default is "false".
]]></xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="validate-definitions" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation><![CDATA[
Whether to validate the Tiles XML definitions. Default is "true".
]]></xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="definitions-factory" type="xsd:string">
<xsd:annotation>
<xsd:documentation><![CDATA[
The Tiles DefinitionsFactory class to use. Default is Tiles' default.
]]></xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="preparer-factory" type="xsd:string">
<xsd:annotation>
<xsd:documentation><![CDATA[
The Tiles PreparerFactory class to use. Default is Tiles' default.
Consider "org.springframework.web.servlet.view.tiles3.SimpleSpringPreparerFactory" or
"org.springframework.web.servlet.view.tiles3.SpringBeanPreparerFactory" (see javadoc).
]]></xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="freemarker-configurer">
<xsd:annotation>
<xsd:documentation><![CDATA[