Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ public Class<?> getContextClass() {
}

/**
* The string form of the expression that failed to evaluate against an instance of the the context class.
* The string form of the expression that failed to evaluate against an instance of the context class.
* @return the expression string
*/
public String getExpressionString() {
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ public FlowDefinitionRegistryBuilder(ApplicationContext appContext, FlowBuilderS
/**
* Configure the base path where flow definitions are found. When specified, all
* flow locations are relative to this path. Also when specified, by default flows
* are assigned an id equal to the the path segment between their base path and
* are assigned an id equal to the path segment between their base path and
* file name.
* <p>
* For example, if a flow definition is located at
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -102,7 +102,7 @@ its parent registry will be queried.
<xsd:documentation>
<![CDATA[
The base path where flow definitions are found. When specified, all flow locations are relative to this path.
Also when specified, by default flows are assigned ids equal to the the path segment between their base path and file name.
Also when specified, by default flows are assigned ids equal to the path segment between their base path and file name.
For example, if a flow definition is located at '/WEB-INF/hotels/booking/booking-flow.xml' and the base path is '/WEB-INF',
the remaining path to this flow is 'hotels/booking' which then becomes the flow id.
If a flow definition is found directly on the base path, the file name minus its extension is used as the flow id.
Expand Down
2 changes: 1 addition & 1 deletion src/docs/asciidoc/spring-faces.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -541,7 +541,7 @@ Spring Web Flow has been tested with file upload components from PrimeFaces.
Check the documentation of your JSF component library for other providers to see how to configure file upload.

Generally, you'll need to enable multipart support in the Servlet container,
either by adding a "multipart-config" element to the the `DispatcherServlet` declaration in web.xml,
either by adding a "multipart-config" element to the `DispatcherServlet` declaration in web.xml,
or by using a `jakarta.servlet.MultipartConfigElement` in programmatic servlet registration

[[_spring_faces_security_taglib]]
Expand Down
2 changes: 1 addition & 1 deletion src/docs/asciidoc/system-setup.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -250,7 +250,7 @@ return getFlowDefinitionRegistryBuilder()
====

With a base path defined, the algorithm that assigns flow identifiers changes slightly.
Flows are now assigned registry identifiers equal to the the path segment between their base path and their file name.
Flows are now assigned registry identifiers equal to the path segment between their base path and their file name.
For example, if a flow definition is located at `/WEB-INF/hotels/booking/booking-flow.xml` and the base path is `/WEB-INF`, the remaining path to this flow is `hotels/booking`, which becomes the flow ID.

.A directory for each flow definition
Expand Down