Adopt Spring Framework 6 and Jakarta EE 9
To avoid any complications with functional changes between Hibernate 5 and Hibernate 6, this uses the hibernate-core-jakarta v5 module rather than hibernate-core v6. This requires a specific dependency exclusion in spring-webflow.gradle to make sure that hibernate-entitymanager never causes both versions to be loaded. This can be simplified after eventual adoption of Hibernate 6. The Spring snapshot repository needs to be referenced in build.gradle for this early stage work on SWF 3.
This commit is contained in:
@@ -46,7 +46,7 @@ The following listing shows the configuration details:
|
||||
<!-- Just here so the JSF implementation can initialize. *Not* used at runtime. -->
|
||||
<servlet>
|
||||
<servlet-name>Faces Servlet</servlet-name>
|
||||
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
|
||||
<servlet-class>jakarta.faces.webapp.FacesServlet</servlet-class>
|
||||
<load-on-startup>1</load-on-startup>
|
||||
</servlet>
|
||||
|
||||
@@ -65,7 +65,7 @@ The use of Facelets instead of JSP typically requires the following element in `
|
||||
----
|
||||
!-- Use JSF view templates saved as *.xhtml, for use with Facelets -->
|
||||
<context-param>
|
||||
<param-name>javax.faces.DEFAULT_SUFFIX</param-name>
|
||||
<param-name>jakarta.faces.DEFAULT_SUFFIX</param-name>
|
||||
<param-value>.xhtml</param-value>
|
||||
</context-param>
|
||||
----
|
||||
@@ -617,7 +617,7 @@ Next, you need to register the taglib file (in the preceding listing) in `web.xm
|
||||
[source,xml]
|
||||
----
|
||||
<context-param>
|
||||
<param-name>javax.faces.FACELETS_LIBRARIES</param-name>
|
||||
<param-name>jakarta.faces.FACELETS_LIBRARIES</param-name>
|
||||
<param-value>/WEB-INF/springsecurity.taglib.xml</param-value>
|
||||
</context-param>
|
||||
----
|
||||
|
||||
@@ -524,7 +524,7 @@ To do that, it looks for matching inner types in the model or its parent.
|
||||
For example, given `org.example.MyModel` with inner types `Group1` and `Group2`, it is sufficient to supply the simple type names -- that is, `group1` and `group2`.
|
||||
You can also provide fully qualified type names.
|
||||
|
||||
A hint with a value of `default` has a special meaning and is translated to the default validation group in Bean Validation: `javax.validation.groups.Default`.
|
||||
A hint with a value of `default` has a special meaning and is translated to the default validation group in Bean Validation: `jakarta.validation.groups.Default`.
|
||||
|
||||
You can configure a custom `ValidationHintResolver`, if necessary, through the `validationHintResolver` property of the `flow-builder-services` element, as follows:
|
||||
|
||||
|
||||
@@ -202,7 +202,7 @@ Note that partial state saving is only supported with Sun Mojarra 2.0.3 or later
|
||||
It is not yet supported with Apache MyFaces.
|
||||
This is due to the fact MyFaces was not as easy to customize with regards to how component state is stored.
|
||||
We will work with Apache MyFaces to provide this support.
|
||||
In the meantime, you need to use the `javax.faces.PARTIAL_STATE_SAVING` context parameter in `web.xml` to disable partial state saving with Apache MyFaces.
|
||||
In the meantime, you need to use the `jakarta.faces.PARTIAL_STATE_SAVING` context parameter in `web.xml` to disable partial state saving with Apache MyFaces.
|
||||
|
||||
===== Travel Sample With the PrimeFaces Components
|
||||
|
||||
|
||||
Reference in New Issue
Block a user