Void Framework

Annotation	Description
`@BindClass`	Indicates that an annotated class is a “Bindable”
`@Controller`	Indicates that an annotated class is a “Controller”
`@Repository`	Indicates that an annotated class is a “Repository”
`@Service`	Indicates that an annotated class is a “Service”

+Void Framework – Cache engine : In-memory

Getting Started

Requirements

Creating a new application

Core

Class scanning

Life cycle

Type conversion

Databases

Data source

Hibernate ORM

Cache

Using cache

Cache engine : In-memory

Cache engine : In-memory

This implementation of the cache engine is the default if no configuration is specified. It is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation

<dependency>
+Release notes

Getting Started

Requirements

Creating a new application

Core

Class scanning

Life cycle

Type conversion

Databases

Data source

Hibernate ORM

Cache

Using cache

Cache engine : In-memory

`Cache engine : In-memory`

This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.


Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
     <version>1.0.0</version>
diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index 324044e..24b7f7d 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -1,8 +1,8 @@
 Void Framework – Using cache
+If no CacheEngine implementation is specified, the cache will not be ac">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
+Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
If no CacheEngine implementation is specified, the cache will not be active.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
 
     @CacheResult
diff --git a/doc/index.xml b/doc/index.xml
index a2ece15..013b340 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,6 +1,6 @@
 Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioData sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is the default if no configuration is specified. It is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.0.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
@@ -12,7 +12,7 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
+If no CacheEngine implementation is specified, the cache will not be active.
 Using Cache with annotations The cache can be used with the following annotations:
 @CacheRemove Indicates that the cache must be evicted.
-The annotation accepts the following parameters:
-key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position).
\ No newline at end of file
+The annotation accepts the following parameters:
\ No newline at end of file
diff --git a/index.xml b/index.xml
index c76e714..cce360a 100644
--- a/index.xml
+++ b/index.xml
@@ -1,6 +1,6 @@
 Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioData sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is the default if no configuration is specified. It is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.0.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
@@ -13,7 +13,7 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
+If no CacheEngine implementation is specified, the cache will not be active.
 Using Cache with annotations The cache can be used with the following annotations:
 @CacheRemove Indicates that the cache must be evicted.
-The annotation accepts the following parameters:
-key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position).
\ No newline at end of file
+The annotation accepts the following parameters:
\ No newline at end of file

From eb2a5a982c2e01ed25026833f620b5b562a67312 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Sun, 10 Jul 2022 09:55:57 +0200
Subject: [PATCH 04/75] Automated website build

---
 css/site.css                                  |  6 ++
 doc/cache/in-memory-cache/index.html          |  4 +-
 doc/cache/index.html                          |  2 +-
 doc/cache/using-cache/index.html              |  6 +-
 doc/core/boot-sequence/index.html             |  9 +++
 doc/core/class-scanning/index.html            |  2 +-
 doc/core/index.html                           |  2 +-
 doc/core/life-cycle/index.html                |  2 +-
 doc/core/type-conversion/index.html           |  2 +-
 doc/databases/datasource/index.html           |  6 +-
 doc/databases/index.html                      |  2 +-
 .../persistence-hibernate/index.html          |  4 +-
 doc/getting-started/index.html                |  2 +-
 .../new-application/index.html                |  6 +-
 doc/getting-started/requirements/index.html   |  2 +-
 doc/i18n/index.html                           |  8 +++
 doc/index.html                                |  2 +-
 doc/index.xml                                 | 12 ++--
 .../using-i18n/index.html                     | 58 +++++++++++++++++++
 index.xml                                     | 17 +++---
 releasenotes/index.html                       | 11 ++--
 sitemap.xml                                   |  2 +-
 22 files changed, 125 insertions(+), 42 deletions(-)
 create mode 100644 doc/core/boot-sequence/index.html
 create mode 100644 doc/i18n/index.html
 create mode 100644 doc/internationalization/using-i18n/index.html

diff --git a/css/site.css b/css/site.css
index 5914346..9bd5ea2 100644
--- a/css/site.css
+++ b/css/site.css
@@ -17,3 +17,9 @@
 .nav-pills > li + li {
     margin-left: 0 !important;
 }
+
+.goat {
+    max-width: 650px;
+    margin-left: auto;
+    margin-right: auto;
+}
diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 9dfa864..cfa13e9 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,10 +2,10 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.0.0</version>
+    <version>1.0.1</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/index.html b/doc/cache/index.html
index ba3cc20..7978e8f 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Cache

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Cache

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index 24b7f7d..fdeffb3 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -1,8 +1,10 @@
 Void Framework – Using cache
+&nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
If no CacheEngine implementation is specified, the cache will not be active.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+If no CacheEngine implementation was specified, the cache will not be active.
 
+Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
 
     @CacheResult
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
new file mode 100644
index 0000000..a799479
--- /dev/null
+++ b/doc/core/boot-sequence/index.html
@@ -0,0 +1,9 @@
+Void Framework – Boot sequence
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index ace8fd6..7897a9e 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,7 +2,7 @@
 Bindable classes (see below) classes implementing the TypeConverter interface classes which e">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
 3 types of elements are recognised during the scan:
Bindable classes (see below)
classes implementing the TypeConverter interface
classes which extend AbstractModule (Guice)

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@BindClass Indicates that an annotated class is a “Bindable”
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
diff --git a/doc/core/index.html b/doc/core/index.html
index 98bf18f..a01cf64 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Core

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Core

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index f663eee..8e32740 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority allows you to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index 9e6e1e0..264403c 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/databases/datasource/index.html b/doc/databases/datasource/index.html
index 870534b..b7d83fc 100644
--- a/doc/databases/datasource/index.html
+++ b/doc/databases/datasource/index.html
@@ -1,16 +1,16 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.0.0</version>
+    <version>1.0.1</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.0.0</version>
+    <version>1.0.1</version>
 </dependency>
 
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/databases/index.html b/doc/databases/index.html
index b6480d3..0bc57de 100644
--- a/doc/databases/index.html
+++ b/doc/databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/databases/persistence-hibernate/index.html b/doc/databases/persistence-hibernate/index.html
index a52aaff..234c232 100644
--- a/doc/databases/persistence-hibernate/index.html
+++ b/doc/databases/persistence-hibernate/index.html
@@ -2,11 +2,11 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.0.0</version>
+    <version>1.0.1</version>
 </dependency>
 

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
 Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

Exemple
@Entity
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index f4c88b9..71341f0 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Getting Started

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Getting Started

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index f55b629..a9f573e 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,15 +2,15 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.0.0</version>
+    <version>1.0.1</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.0.0</version>
+    <version>1.0.1</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf.
voidframework {
     core {
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index 725b6b7..fbb482b 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
new file mode 100644
index 0000000..ad7a9f5
--- /dev/null
+++ b/doc/i18n/index.html
@@ -0,0 +1,8 @@
+Void Framework – Internationalization
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Internationalization

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/index.html b/doc/index.html
index 405251c..b81c2d2 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory

Documentation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Documentation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 013b340..87bcd8b 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,7 +1,8 @@
 Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioData sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.0.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.0.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
@@ -12,7 +13,6 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
-If no CacheEngine implementation is specified, the cache will not be active.
-Using Cache with annotations The cache can be used with the following annotations:
-@CacheRemove Indicates that the cache must be evicted.
-The annotation accepts the following parameters:
\ No newline at end of file
+&nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Using Cache with annotations The cache can be used with the following annotations:Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.0.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
new file mode 100644
index 0000000..12a154a
--- /dev/null
+++ b/doc/internationalization/using-i18n/index.html
@@ -0,0 +1,58 @@
+Void Framework – Using internationalization
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+    <groupId>dev.voidframework</groupId>
+    <artifactId>voidframework-i18n</artifactId>
+    <version>1.0.1</version>
+</dependency>
+

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
+
resources/messages_en.properties
lang.fr=French
+

Retrieving messages
The retrieval of translated messages is done through the use of the Internationalization service.
Example
public final class InternationalizationExample {
+
+    private final Internationalization i18n;
+
+    @Inject
+    public InternationalizationExample(final Internationalization i18n) {
+        this.i18n = i18n;
+    }
+
+    public void i18n() {
+        // Output: Français
+        i18n.getMessage(Locale.FRENCH, "lang.fr");
+
+        // Output: French
+        i18n.getMessage(Locale.ENGLISH, "lang.fr");
+    }
+}        
+

Plural forms
The plural form can be handled in two ways, the first uses ChoiceFormat which allows via an advanced syntax to add some intelligence to the translation messages. The second, more simple, is based on the use of new keys with special naming.
 
+Read more about ChoiceFormat on official
+Java documentation.
Example (ChoiceFormat)
key=This element contains {0,choice,0#no comments|1#one comment|1<{0,number,000} comments}
+
public void i18n() {
+    // Output: This element contains 0 comments
+    i18n.getMessage(Locale.ENGLISH, "key", 0);
+
+    // Output: This element contains 1 comment
+    i18n.getMessage(Locale.ENGLISH, "key", 1);
+
+    // Output: This element contains 1337 comments
+    i18n.getMessage(Locale.ENGLISH, "key", 1337);
+}
+
Example (New key)
inbox.0=Inbox "{0}" contains no messages
+inbox.1=Inbox "{0}" contains one message
+inbox.2=Inbox "{0}" contains {1} messages
+
public void i18n() {
+    // Output: Inbox "Unread" contains no messages
+    i18n.getMessage(Locale.ENGLISH, 0, "inbox", "Unread", 0);
+
+    // Output: Inbox "Unread" contains one message
+    i18n.getMessage(Locale.ENGLISH, 1,"inbox", "Unread", 1);
+
+    // Output: Inbox "Unread" contains 42 messages
+    i18n.getMessage(Locale.ENGLISH, 42, "inbox", "Unread", 42);
+}
+

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/index.xml b/index.xml
index cce360a..63e50fe 100644
--- a/index.xml
+++ b/index.xml
@@ -1,19 +1,20 @@
 Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioData sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.0.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.0.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
-priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.0.0 2022-07-02
-New Initial releaseRequirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
+priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.0.1 2022-07-08
+New Ability to retrieve XML body content as Java object Improved Cache management : rename the annotation Cache to CacheResult and add CacheRemove Fixed Removed I18N reference from Hibernate module Fixed Transactional annotation : rollback not occur on unchecked exception Fixed Routes are randomly sorted 1.0.0 2022-07-02
+Initial releaseRequirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
-If no CacheEngine implementation is specified, the cache will not be active.
-Using Cache with annotations The cache can be used with the following annotations:
-@CacheRemove Indicates that the cache must be evicted.
-The annotation accepts the following parameters:
\ No newline at end of file
+&nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Using Cache with annotations The cache can be used with the following annotations:Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.0.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 7399f87..7e15ea8 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,11 +1,10 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.0.0

-2022-07-02
New
-Initial release

© 2022 Void Framework

+Release notes
1.0.1

+2022-07-08
New Ability to retrieve XML body content as Java object
Improved Cache management : rename the annotation Cache to CacheResult and add CacheRemove
Fixed Removed I18N reference from Hibernate module
Fixed Transactional annotation : rollback not occur on unchecked exception
Fixed Routes are randomly sorted

1.0.0

+2022-07-02
Initial release

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/sitemap.xml b/sitemap.xml
index 25da66a..b495daa 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file

From d44fee23b00aeb9d939b0601823b96eaa0ddbe9c Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Sat, 16 Jul 2022 18:00:54 +0000
Subject: [PATCH 05/75] Automated website build

---
 doc/databases/datasource/index.html | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/doc/databases/datasource/index.html b/doc/databases/datasource/index.html
index b7d83fc..0b59873 100644
--- a/doc/databases/datasource/index.html
+++ b/doc/databases/datasource/index.html
@@ -16,22 +16,28 @@
 voidframework.datasource.default.driver the driver to be used to communicate with the database.required
 voidframework.datasource.default.url the JDBC format URL to be used to reach the database.
required
 voidframework.datasource.default.username the username to be provided durint the authentication step.
required
-voidframework.datasource.default.password the password to be provided durint the authentication step.
C3P0 only
-optional
+voidframework.datasource.default.password the password to be provided durint the authentication step.
optional
+C3P0 only
 voidframework.datasource.default.statementCacheNumDeferredCloseThreads defines the number of threads to track when Connections are in use, and only destroy Statements when their parent Connections are not otherwise in use.
optional
+HikariCP only
 voidframework.datasource.default.cachePrepStmts enable or disable the prepared statements cache.
optional
 voidframework.datasource.default.prepStmtCacheSize the number of prepared statements cache to keep in the cache.
optional
+HikariCP only
 voidframework.datasource.default.prepStmtCacheSqlLimit the size of the largest SQL query for which the parsing result will be keep in the cache.
optional
 voidframework.datasource.default.autoCommit enable or disable the auto commit behavior when the connection goes back into the pool.
optional
+HikariCP only
 voidframework.datasource.default.connectionInitSql the SQL statement that will be executed after every new connection.
optional
+HikariCP only
 voidframework.datasource.default.connectionTestQuery the SQL statement that will be executed to test if the connection is still valid.
optional
 voidframework.datasource.default.connectionTimeout the milliseconds to wait before timing out during the connection.
optional
 voidframework.datasource.default.idleTimeout the milliseconds to wait before closing an unused connection.
optional
+HikariCP only
 voidframework.datasource.default.keepaliveTime the milliseconds to wait before attempting to keep the connection alive.
optional
 voidframework.datasource.default.minimumIdle the minimum number of alive connections in the pool.
optional
-voidframework.datasource.default.maximumPoolSize the maximum number of connections allowed in the pool.
C3P0 only
-optional
-voidframework.datasource.default.acquireIncrement determines how many connections at a time C3P0 will try to acquire when the pool is exhausted.
 
+voidframework.datasource.default.maximumPoolSize the maximum number of connections allowed in the pool.optional
+C3P0 only
+voidframework.datasource.default.acquireIncrement determines how many connections at a time C3P0 will try to acquire when the pool is exhausted.
optional
+voidframework.datasource.default.maxConnectionAge the milliseconds to wait before closing a connection.
 
 The third segment named "default" represents the name of the data source. Any name can be used as long as it does not contain spaces or special characters.

Usage
@Service
 public class ExampleDataSourceService {
 

From 5c3e4d4cc6462801983a6c8dd277a7582c32963e Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Tue, 26 Jul 2022 07:26:53 +0200
Subject: [PATCH 06/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  4 ++--
 doc/cache/index.html                          |  2 +-
 doc/cache/redis-cache/index.html              | 14 +++++++++++
 doc/cache/using-cache/index.html              |  4 ++--
 doc/core/boot-sequence/index.html             |  2 +-
 doc/core/class-scanning/index.html            |  2 +-
 doc/core/index.html                           |  2 +-
 doc/core/life-cycle/index.html                |  2 +-
 doc/core/type-conversion/index.html           |  2 +-
 doc/databases/datasource/index.html           |  6 ++---
 doc/databases/index.html                      |  2 +-
 .../persistence-hibernate/index.html          |  4 ++--
 doc/getting-started/index.html                |  2 +-
 .../new-application/index.html                | 19 +++++++++------
 doc/getting-started/requirements/index.html   |  2 +-
 .../upgrading-from-old-version/index.html     |  9 ++++++++
 doc/i18n/index.html                           |  2 +-
 doc/index.html                                |  2 +-
 doc/index.xml                                 | 17 ++++++++------
 .../using-i18n/index.html                     |  4 ++--
 doc/web/controller/index.html                 | 17 ++++++++++++++
 doc/web/index.html                            |  8 +++++++
 index.xml                                     | 23 +++++++++++--------
 releasenotes/index.html                       |  9 +++++---
 sitemap.xml                                   |  2 +-
 25 files changed, 112 insertions(+), 50 deletions(-)
 create mode 100644 doc/cache/redis-cache/index.html
 create mode 100644 doc/getting-started/upgrading-from-old-version/index.html
 create mode 100644 doc/web/controller/index.html
 create mode 100644 doc/web/index.html

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index cfa13e9..fc0afd6 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,10 +2,10 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.0.1</version>
+    <version>1.1.1</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/index.html b/doc/cache/index.html
index 7978e8f..1f67719 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Cache

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Cache

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
new file mode 100644
index 0000000..852af8c
--- /dev/null
+++ b/doc/cache/redis-cache/index.html
@@ -0,0 +1,14 @@
+Void Framework – Cache engine : Redis
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+    <groupId>dev.voidframework</groupId>
+    <artifactId>voidframework-cache-redis</artifactId>
+    <version>1.1.1</version>
+</dependency>
+
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index fdeffb3..b63d5eb 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,9 +2,9 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
-Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
+Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
 
     @CacheResult
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index a799479..c855a0f 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n . c c e f b e o i o n g o m v ( u t o e S r s d r t a t u t a t r">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index 7897a9e..e175787 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,7 +2,7 @@
 Bindable classes (see below) classes implementing the TypeConverter interface classes which e">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
 3 types of elements are recognised during the scan:
Bindable classes (see below)
classes implementing the TypeConverter interface
classes which extend AbstractModule (Guice)

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@BindClass Indicates that an annotated class is a “Bindable”
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
diff --git a/doc/core/index.html b/doc/core/index.html
index a01cf64..9baebc1 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Core

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Core

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index 8e32740..c3d343b 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority allows you to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index 264403c..aa2c96d 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/databases/datasource/index.html b/doc/databases/datasource/index.html
index 0b59873..8a11d95 100644
--- a/doc/databases/datasource/index.html
+++ b/doc/databases/datasource/index.html
@@ -1,16 +1,16 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.0.1</version>
+    <version>1.1.1</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.0.1</version>
+    <version>1.1.1</version>
 </dependency>
 
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/databases/index.html b/doc/databases/index.html
index 0bc57de..35c9d6b 100644
--- a/doc/databases/index.html
+++ b/doc/databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/databases/persistence-hibernate/index.html b/doc/databases/persistence-hibernate/index.html
index 234c232..eaecc5d 100644
--- a/doc/databases/persistence-hibernate/index.html
+++ b/doc/databases/persistence-hibernate/index.html
@@ -2,11 +2,11 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.0.1</version>
+    <version>1.1.1</version>
 </dependency>
 

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
 Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

Exemple
@Entity
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index 71341f0..37a4b9a 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Getting Started

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Getting Started

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index a9f573e..56452e4 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,20 +2,26 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.0.1</version>
+    <version>1.1.1</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.0.1</version>
+    <version>1.1.1</version>
 </dependency>
-

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf.
voidframework {
+

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
         acceptedScanPaths += "controller"
     }
+
+    web {
+        session {
+            signatureKey = "BUXpcQ6OAXMGR45sV9bjeq161raMoIrNiJw3z18leM4TRIBVUHsZsrTlK58fX2JD"
+        }
+    }
 }
 
 
 If one of the specified paths does not exist, the application will continue to the next one without halting.

Web controller
Add the following controller to the controller package or any package that will be considered by the acceptedScanPaths configuration.
package controller;
@@ -31,12 +37,11 @@
 
     @RequestRoute(method = HttpMethod.GET, route = "/")
     public Result sayHello() {
-
         return Result.ok("Hello World!");
     }
 }
-

Application launcher
To start the application, you have to instantiate ApplicationLauncher and then call the launch method.
final ApplicationLauncher applicationLauncher = new ApplicationLauncher();
-applicationLauncher.launch();
+

Application launcher
To start the application, you have to instantiate ApplicationLauncher and then call the launch method.
final VoidApplication app = new VoidApplication();
+app.launch();
 

Run your application
You can now start your application and go to the URL http://127.0.0.1:9000 in your favourite web browser.

© 2022 Void Framework

 Void Framework is released under the MIT License

 
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index fbb482b..062de90 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
new file mode 100644
index 0000000..ce73449
--- /dev/null
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -0,0 +1,9 @@
+Void Framework – Upgrading from old version
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index ad7a9f5..d55bb99 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Internationalization

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Internationalization

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index b81c2d2..7904f74 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Documentation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Documentation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 87bcd8b..cf332ef 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,10 +1,12 @@
 Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioData sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.0.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
-Configuration The following configuration key can be used in the configuration file of your application.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
+A simple controller @Singleton @WebController public class ExampleController { @RequestRoute public Result homepage() { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
@@ -12,7 +14,8 @@ priority is used to define when the method will be called in relation to the oth
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
-Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
-&nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Using Cache with annotations The cache can be used with the following annotations:Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Upgrading from old versionhttps://voidframework.dev/doc/getting-started/upgrading-from-old-version/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/upgrading-from-old-version/Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.
+1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now requiredUsing cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
+&nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.0.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 12a154a..dbfab1e 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,10 +1,10 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Internationalization
Using internationalization

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.0.1</version>
+    <version>1.1.1</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
new file mode 100644
index 0000000..7289924
--- /dev/null
+++ b/doc/web/controller/index.html
@@ -0,0 +1,17 @@
+Void Framework – Controller
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

A simple controller
@Singleton
+@WebController
+public class ExampleController {
+
+    @RequestRoute
+    public Result homepage() {
+        return Result.ok("Hello World");
+    }
+}
+

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/web/index.html b/doc/web/index.html
new file mode 100644
index 0000000..51f8bd5
--- /dev/null
+++ b/doc/web/index.html
@@ -0,0 +1,8 @@
+Void Framework – Web
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Web

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/index.xml b/index.xml
index 63e50fe..722e499 100644
--- a/index.xml
+++ b/index.xml
@@ -1,20 +1,23 @@
 Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioData sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.0.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
-Configuration The following configuration key can be used in the configuration file of your application.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
+A simple controller @Singleton @WebController public class ExampleController { @RequestRoute public Result homepage() { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
-priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.0.1 2022-07-08
-New Ability to retrieve XML body content as Java object Improved Cache management : rename the annotation Cache to CacheResult and add CacheRemove Fixed Removed I18N reference from Hibernate module Fixed Transactional annotation : rollback not occur on unchecked exception Fixed Routes are randomly sorted 1.0.0 2022-07-02
-Initial releaseRequirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
+priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.1.1 2022-07-24
+Improved Change CSRF signature algorithm to HMACSHA256 Fixed Error 500 CSRF when POST request render template 1.1.0 2022-07-22
+New Methods on Reflection util class: getAnnotatedField(Object, Class<? extends Annotation>) and getAnnotatedField(Class, Class<? extends Annotation>) New Configuration keys to define number of I/O and Worker threads (Web) New Redis (base + cache + healthcheck) New CSRF token Improved No longer necessary for HealthChecker to be Singleton Improved Add cache abstraction helper Improved Session signature key configuration is now required Improved Rename ApplicationLauncher to VoidApplication Improved Updated version of all dependencies Fixed Cookie revocation not working Fixed C3P0/HikariCP settings Fixed Issue on routes sorting when regex and capture regex are used Fixed Assets not found when devMode=false Fixed Hibernate : Models not found when application is compiled 1.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
-Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
-&nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Using Cache with annotations The cache can be used with the following annotations:Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Upgrading from old versionhttps://voidframework.dev/doc/getting-started/upgrading-from-old-version/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/upgrading-from-old-version/Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.
+1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now requiredUsing cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
+&nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.0.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 7e15ea8..08a9900 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,8 +1,11 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.0.1

+Release notes
1.1.1

+2022-07-24
Improved Change CSRF signature algorithm to HMACSHA256
Fixed Error 500 CSRF when POST request render template

1.1.0

+2022-07-22
New Methods on Reflection util class: getAnnotatedField(Object, Class) and getAnnotatedField(Class, Class)
New Configuration keys to define number of I/O and Worker threads (Web)
New Redis (base + cache + healthcheck)
New CSRF token
Improved No longer necessary for HealthChecker to be Singleton
Improved Add cache abstraction helper
Improved Session signature key configuration is now required
Improved Rename ApplicationLauncher to VoidApplication
Improved Updated version of all dependencies
Fixed Cookie revocation not working
Fixed C3P0/HikariCP settings
Fixed Issue on routes sorting when regex and capture regex are used
Fixed Assets not found when devMode=false
Fixed Hibernate : Models not found when application is compiled

1.0.1

 2022-07-08
New Ability to retrieve XML body content as Java object
Improved Cache management : rename the annotation Cache to CacheResult and add CacheRemove
Fixed Removed I18N reference from Hibernate module
Fixed Transactional annotation : rollback not occur on unchecked exception
Fixed Routes are randomly sorted

1.0.0

 2022-07-02
Initial release

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/sitemap.xml b/sitemap.xml
index b495daa..0b895ec 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file

From e1a40313e58c4d0d72169c1ded904159a3ded3c5 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Tue, 26 Jul 2022 19:06:00 +0000
Subject: [PATCH 07/75] Automated website build

---
 doc/index.xml                 |  3 ++-
 doc/web/controller/index.html | 19 +++++++++++++------
 index.xml                     |  3 ++-
 3 files changed, 17 insertions(+), 8 deletions(-)

diff --git a/doc/index.xml b/doc/index.xml
index cf332ef..8ff152f 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -6,7 +6,8 @@ Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
-A simple controller @Singleton @WebController public class ExampleController { @RequestRoute public Result homepage() { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
+Example
+@Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index 7289924..8b5488d 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,16 +1,23 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

A simple controller
@Singleton
-@WebController
-public class ExampleController {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+@WebController(prefixRoute = "/account")
+public class AccountController {
 
-    @RequestRoute
-    public Result homepage() {
+    @RequestRoute(route = "/(?<accountId>[a-f0-9]+)")
+    public Result showAccount(@RequestPath("accountId") final String accountId) {
+        return Result.ok("Hello World");
+    }
+
+    @RequestRoute(method = HttpMethod.POST, route = "/(?<accountId>[a-f0-9]+)")
+    public Result updateAccount(@RequestPath("accountId") final String accountId,
+                                @RequestBody final ProfileForm form,
+                                final Context context) {
         return Result.ok("Hello World");
     }
 }
-

© 2022 Void Framework

+

Defining a route
A route is defined by two components, firstly @WebController defines the prefix that will be applied to all methods of the controller and by the @RequestRoute annotation providing various options. The latter tells the Void Framework that the method is an entry point.

Retrieving parameters
To work, a controller will probably need some incoming data. To do this, the @RequestPath, @RequestVariable and @RequestBody annotations make it easy to retrieve information from the request. It is also possible to retrieve information from the Context.

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/index.xml b/index.xml
index 722e499..0adec69 100644
--- a/index.xml
+++ b/index.xml
@@ -6,7 +6,8 @@ Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
-A simple controller @Singleton @WebController public class ExampleController { @RequestRoute public Result homepage() { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
+Example
+@Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:

From 0188a420165324b30abdd920261c11809f481667 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 28 Jul 2022 19:23:29 +0000
Subject: [PATCH 08/75] Automated website build

---
 doc/cache/in-memory-cache/index.html                     | 2 +-
 doc/cache/index.html                                     | 2 +-
 doc/cache/redis-cache/index.html                         | 2 +-
 doc/cache/using-cache/index.html                         | 2 +-
 doc/core/boot-sequence/index.html                        | 2 +-
 doc/core/class-scanning/index.html                       | 2 +-
 doc/core/configuration/index.html                        | 9 +++++++++
 doc/core/index.html                                      | 2 +-
 doc/core/life-cycle/index.html                           | 2 +-
 doc/core/type-conversion/index.html                      | 2 +-
 doc/databases/datasource/index.html                      | 2 +-
 doc/databases/index.html                                 | 2 +-
 doc/databases/persistence-hibernate/index.html           | 2 +-
 doc/getting-started/index.html                           | 2 +-
 doc/getting-started/new-application/index.html           | 4 ++--
 doc/getting-started/requirements/index.html              | 2 +-
 .../upgrading-from-old-version/index.html                | 2 +-
 doc/i18n/index.html                                      | 2 +-
 doc/index.html                                           | 2 +-
 doc/index.xml                                            | 2 +-
 doc/internationalization/using-i18n/index.html           | 2 +-
 doc/web/controller/index.html                            | 4 ++--
 doc/web/index.html                                       | 2 +-
 index.xml                                                | 2 +-
 releasenotes/index.html                                  | 2 +-
 sitemap.xml                                              | 2 +-
 26 files changed, 36 insertions(+), 27 deletions(-)
 create mode 100644 doc/core/configuration/index.html

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index fc0afd6..7d17433 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,7 +2,7 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
     <version>1.1.1</version>
diff --git a/doc/cache/index.html b/doc/cache/index.html
index 1f67719..d9358ef 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Cache

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Cache

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 852af8c..f9e5faa 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
     <version>1.1.1</version>
diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index b63d5eb..f280746 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,7 +2,7 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
 Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index c855a0f..4ae5a0e 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n . c c e f b e o i o n g o m v ( u t o e S r s d r t a t u t a t r">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index e175787..9c1aef5 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,7 +2,7 @@
 Bindable classes (see below) classes implementing the TypeConverter interface classes which e">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
 3 types of elements are recognised during the scan:
Bindable classes (see below)
classes implementing the TypeConverter interface
classes which extend AbstractModule (Guice)

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@BindClass Indicates that an annotated class is a “Bindable”
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
new file mode 100644
index 0000000..228c5e4
--- /dev/null
+++ b/doc/core/configuration/index.html
@@ -0,0 +1,9 @@
+Void Framework – Configuration
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

Custom configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/core/index.html b/doc/core/index.html
index 9baebc1..37e85e7 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Core

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Core

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index c3d343b..36bfeeb 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority allows you to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index aa2c96d..d37d1a4 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/databases/datasource/index.html b/doc/databases/datasource/index.html
index 8a11d95..2f40053 100644
--- a/doc/databases/datasource/index.html
+++ b/doc/databases/datasource/index.html
@@ -1,7 +1,7 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
diff --git a/doc/databases/index.html b/doc/databases/index.html
index 35c9d6b..4c9b2fe 100644
--- a/doc/databases/index.html
+++ b/doc/databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/databases/persistence-hibernate/index.html b/doc/databases/persistence-hibernate/index.html
index eaecc5d..a0fa7fe 100644
--- a/doc/databases/persistence-hibernate/index.html
+++ b/doc/databases/persistence-hibernate/index.html
@@ -2,7 +2,7 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index 37a4b9a..1ec7440 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Getting Started

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Getting Started

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 56452e4..4e8651d 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,7 +2,7 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
     <version>1.1.1</version>
@@ -12,7 +12,7 @@
     <artifactId>voidframework-web</artifactId>
     <version>1.1.1</version>
 </dependency>
-

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
+

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
         acceptedScanPaths += "controller"
     }
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index 062de90..7319641 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index ce73449..1e84e6b 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.1.0 ApplicationLa">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index d55bb99..9edf864 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Internationalization

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Internationalization

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index 7904f74..8e657eb 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Documentation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Documentation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 8ff152f..39df164 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -5,7 +5,7 @@ S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
+Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index dbfab1e..1b081b3 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
     <version>1.1.1</version>
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index 8b5488d..f13eeb0 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
@@ -17,7 +17,7 @@
         return Result.ok("Hello World");
     }
 }
-

Defining a route
A route is defined by two components, firstly @WebController defines the prefix that will be applied to all methods of the controller and by the @RequestRoute annotation providing various options. The latter tells the Void Framework that the method is an entry point.

Retrieving parameters
To work, a controller will probably need some incoming data. To do this, the @RequestPath, @RequestVariable and @RequestBody annotations make it easy to retrieve information from the request. It is also possible to retrieve information from the Context.

© 2022 Void Framework

+

Defining a route
A route is defined by two components, firstly @WebController defines the prefix that will be applied to all methods of the controller and by the @RequestRoute annotation providing various options. The latter tells the Void Framework that the method is an entry point.
@WebController
This annotation is based on the @Controller annotation. It simply allows the class to be better specified and provides additional options. This annotation can only be used at class level.
The annotation accepts the following parameter:
prefixRoute allows you to define a prefix to be used on all endpoints in the class. By default, the value is empty.
@RequestRoute
This annotation allows you to configure an entry point that will process an incoming request. This annotation can only be used at method level.
The annotation accepts the following parameters:
method allows you to define the HTTP method. The default value is HttpMethod.GET.
route allows you to define a route. The default value is /.
name allows you to define an alias name who can be used with the reverse routing. By default, the value is empty.

Retrieving parameters
To work, a controller will probably need some incoming data. To do this, the @RequestPath, @RequestVariable and @RequestBody annotations make it easy to retrieve information from the request. It is also possible to retrieve information from the Context itself.
@RequestPath
This annotation allows you to extract parameters named in the URL path.
The annotation accepts the following parameter:
value allows you to define the name of the parameter (correlated with the regexp used in the route definition) to extract.
@RequestVariable
This annotation allows you to extract query string value from the URI.
The annotation accepts the following parameter:
value allows you to define the name of the query string value to extract.
@RequestBody
This annotation allows you to retrieve the contents of the request (i.e. from a POST query) as a Java object. If something goes wrong, the extracted value will be null.

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/index.html b/doc/web/index.html
index 51f8bd5..d8927d2 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Web

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Web

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/index.xml b/index.xml
index 0adec69..16b1d80 100644
--- a/index.xml
+++ b/index.xml
@@ -5,7 +5,7 @@ S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
+Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 08a9900..18dd61c 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -4,7 +4,7 @@
 Void Framework
Documentation
    
 Release notes
1.1.1

-2022-07-24
Improved Change CSRF signature algorithm to HMACSHA256
Fixed Error 500 CSRF when POST request render template

1.1.0

+2022-07-24
Improved Change CSRF signature algorithm to HMACSHA256
Fixed Error 500 CSRF when POST request render template

1.1.0

 2022-07-22
New Methods on Reflection util class: getAnnotatedField(Object, Class) and getAnnotatedField(Class, Class)
New Configuration keys to define number of I/O and Worker threads (Web)
New Redis (base + cache + healthcheck)
New CSRF token
Improved No longer necessary for HealthChecker to be Singleton
Improved Add cache abstraction helper
Improved Session signature key configuration is now required
Improved Rename ApplicationLauncher to VoidApplication
Improved Updated version of all dependencies
Fixed Cookie revocation not working
Fixed C3P0/HikariCP settings
Fixed Issue on routes sorting when regex and capture regex are used
Fixed Assets not found when devMode=false
Fixed Hibernate : Models not found when application is compiled

1.0.1

 2022-07-08
New Ability to retrieve XML body content as Java object
Improved Cache management : rename the annotation Cache to CacheResult and add CacheRemove
Fixed Removed I18N reference from Hibernate module
Fixed Transactional annotation : rollback not occur on unchecked exception
Fixed Routes are randomly sorted

1.0.0

 2022-07-02
Initial release

© 2022 Void Framework

diff --git a/sitemap.xml b/sitemap.xml
index 0b895ec..8f04f01 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file

From edcc9fd1c7aff30314a59fa64061c2e53c8fb9f1 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 28 Jul 2022 19:27:39 +0000
Subject: [PATCH 09/75] Automated website build

---
 doc/cache/using-cache/index.html | 2 +-
 doc/core/life-cycle/index.html   | 2 +-
 doc/web/controller/index.html    | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index f280746..21e81a0 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -4,7 +4,7 @@
    
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
-Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key allows you to define the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
+Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
 
     @CacheResult
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index 36bfeeb..53ef3e1 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -3,7 +3,7 @@
 Void Framework
Documentation
    
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
-It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority allows you to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
+It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
 
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index f13eeb0..88a614f 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -17,7 +17,7 @@
         return Result.ok("Hello World");
     }
 }
-

Defining a route
A route is defined by two components, firstly @WebController defines the prefix that will be applied to all methods of the controller and by the @RequestRoute annotation providing various options. The latter tells the Void Framework that the method is an entry point.
@WebController
This annotation is based on the @Controller annotation. It simply allows the class to be better specified and provides additional options. This annotation can only be used at class level.
The annotation accepts the following parameter:
prefixRoute allows you to define a prefix to be used on all endpoints in the class. By default, the value is empty.
@RequestRoute
This annotation allows you to configure an entry point that will process an incoming request. This annotation can only be used at method level.
The annotation accepts the following parameters:
method allows you to define the HTTP method. The default value is HttpMethod.GET.
route allows you to define a route. The default value is /.
name allows you to define an alias name who can be used with the reverse routing. By default, the value is empty.

Retrieving parameters
To work, a controller will probably need some incoming data. To do this, the @RequestPath, @RequestVariable and @RequestBody annotations make it easy to retrieve information from the request. It is also possible to retrieve information from the Context itself.
@RequestPath
This annotation allows you to extract parameters named in the URL path.
The annotation accepts the following parameter:
value allows you to define the name of the parameter (correlated with the regexp used in the route definition) to extract.
@RequestVariable
This annotation allows you to extract query string value from the URI.
The annotation accepts the following parameter:
value allows you to define the name of the query string value to extract.
@RequestBody
This annotation allows you to retrieve the contents of the request (i.e. from a POST query) as a Java object. If something goes wrong, the extracted value will be null.

© 2022 Void Framework

+

Defining a route
A route is defined by two components, firstly @WebController defines the prefix that will be applied to all methods of the controller and by the @RequestRoute annotation providing various options. The latter tells the Void Framework that the method is an entry point.
@WebController
This annotation is based on the @Controller annotation. It simply allows the class to be better specified and provides additional options. This annotation can only be used at class level.
The annotation accepts the following parameter:
prefixRoute defines a prefix to be used on all endpoints in the class. By default, the value is empty.
@RequestRoute
This annotation allows you to configure an entry point that will process an incoming request. This annotation can only be used at method level.
The annotation accepts the following parameters:
method defines the HTTP method. The default value is HttpMethod.GET.
route defines a route. Regular expression with named capturing group can be used. The default value is /.
name defines an alias name who can be used with the reverse routing. By default, the value is empty.

Retrieving parameters
To work, a controller will probably need some incoming data. To do this, the @RequestPath, @RequestVariable and @RequestBody annotations make it easy to retrieve information from the request. It is also possible to retrieve information from the Context itself.
@RequestPath
This annotation allows you to extract parameters named in the URL path.
The annotation accepts the following parameter:
value defines the name of the parameter (correlated with the regexp used in the route definition) to extract.
@RequestVariable
This annotation allows you to extract query string value from the URI.
The annotation accepts the following parameter:
value defines the name of the query string value to extract.
@RequestBody
This annotation allows you to retrieve the contents of the request (i.e. from a POST query) as a Java object. If something goes wrong, the extracted value will be null.

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 

From cda26a4cbde87a548ef0968a51820f469d572c8b Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Fri, 29 Jul 2022 18:33:36 +0000
Subject: [PATCH 10/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/index.html                          |  2 +-
 doc/cache/redis-cache/index.html              |  2 +-
 doc/cache/using-cache/index.html              |  2 +-
 doc/core/boot-sequence/index.html             |  2 +-
 doc/core/class-scanning/index.html            |  2 +-
 doc/core/configuration/index.html             |  2 +-
 doc/core/index.html                           |  2 +-
 doc/core/life-cycle/index.html                |  2 +-
 doc/core/type-conversion/index.html           |  2 +-
 doc/databases/datasource/index.html           |  2 +-
 doc/databases/index.html                      |  2 +-
 .../persistence-hibernate/index.html          |  2 +-
 doc/getting-started/index.html                |  2 +-
 .../new-application/index.html                |  2 +-
 doc/getting-started/requirements/index.html   |  2 +-
 .../upgrading-from-old-version/index.html     |  2 +-
 doc/i18n/index.html                           |  2 +-
 doc/index.html                                |  2 +-
 doc/index.xml                                 |  4 +-
 .../using-i18n/index.html                     |  2 +-
 doc/web/controller/index.html                 |  2 +-
 doc/web/filters/index.html                    | 38 +++++++++++++++++++
 doc/web/index.html                            |  2 +-
 index.xml                                     |  4 +-
 sitemap.xml                                   |  2 +-
 26 files changed, 67 insertions(+), 25 deletions(-)
 create mode 100644 doc/web/filters/index.html

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 7d17433..06f9ed4 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,7 +2,7 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
     <version>1.1.1</version>
diff --git a/doc/cache/index.html b/doc/cache/index.html
index d9358ef..58f64ef 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Cache

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Cache

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index f9e5faa..7331163 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
     <version>1.1.1</version>
diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index 21e81a0..3529346 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,7 +2,7 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
 Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index 4ae5a0e..e788510 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n . c c e f b e o i o n g o m v ( u t o e S r s d r t a t u t a t r">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index 9c1aef5..3a8e75f 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,7 +2,7 @@
 Bindable classes (see below) classes implementing the TypeConverter interface classes which e">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
 3 types of elements are recognised during the scan:
Bindable classes (see below)
classes implementing the TypeConverter interface
classes which extend AbstractModule (Guice)

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@BindClass Indicates that an annotated class is a “Bindable”
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index 228c5e4..a8ef2bb 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -1,7 +1,7 @@
 Void Framework – Configuration
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

Custom configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

Custom configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
 

© 2022 Void Framework

 Void Framework is released under the MIT License

 
diff --git a/doc/core/index.html b/doc/core/index.html
index 37e85e7..63b5eb9 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Core

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Core

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index 53ef3e1..8debf82 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index d37d1a4..50db050 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/databases/datasource/index.html b/doc/databases/datasource/index.html
index 2f40053..603f8c1 100644
--- a/doc/databases/datasource/index.html
+++ b/doc/databases/datasource/index.html
@@ -1,7 +1,7 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
diff --git a/doc/databases/index.html b/doc/databases/index.html
index 4c9b2fe..c63d4ec 100644
--- a/doc/databases/index.html
+++ b/doc/databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/databases/persistence-hibernate/index.html b/doc/databases/persistence-hibernate/index.html
index a0fa7fe..836a18e 100644
--- a/doc/databases/persistence-hibernate/index.html
+++ b/doc/databases/persistence-hibernate/index.html
@@ -2,7 +2,7 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index 1ec7440..f249f6d 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Getting Started

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Getting Started

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 4e8651d..a7ee5b1 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,7 +2,7 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
     <version>1.1.1</version>
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index 7319641..81d22e2 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index 1e84e6b..57e1863 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.1.0 ApplicationLa">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index 9edf864..5f1a547 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Internationalization

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Internationalization

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index 8e657eb..e6a96b1 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Documentation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Documentation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 39df164..9ca7987 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -8,7 +8,9 @@ Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
-Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
+Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
+@FilterWith({FirstFilter.java, SecondFilter.java}) @Singleton @WebController public class Controller { @FilterWith({ThirdFiter.java}) @RequestRouting public Result showHomePage() { return Result.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 1b081b3..9dffc6b 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
     <version>1.1.1</version>
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index 88a614f..d03e89d 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
new file mode 100644
index 0000000..1be0e57
--- /dev/null
+++ b/doc/web/filters/index.html
@@ -0,0 +1,38 @@
+Void Framework – Filters
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
+@Singleton
+@WebController
+public class Controller {
+
+    @FilterWith({ThirdFiter.java})
+    @RequestRouting
+    public Result showHomePage() {
+        return Result.of("Hello World!");
+    }
+}
+

Global filters
In case the filter have to be enabled globally (it will be used for all requests), it must be declared in the application configuration file with the configuration key voidframework.web.globalFilters :
voidframework {
+    web {
+        globalFilters += "dev.voidframework.web.csrf.CSRFFilter"
+    }
+}
+

Passing attributes
If you need to pass values which should not be passed through the session from one filter to another, or simply from a filter to a controller, you can use Context attributes. This is a simple way of passing values while maintaining their type.
@Singleton
+public class ExampleFilter implements Filter {
+
+    private static final TypedMap.Key<UUID> USER_ID = TypedMap.Key.of("USER_ID");
+
+    @Override
+    public Result apply(final Context context, final FilterChain filterChain) {
+        context.getAttributes().put(USER_ID, UUID.randomUUID());
+        
+        return filterChain.applyNext(context);
+    }
+}
+
 
+Note that the use of dependencies direct injection is possible in filters.

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/web/index.html b/doc/web/index.html
index d8927d2..6779086 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller

Web

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Web

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/index.xml b/index.xml
index 16b1d80..99dce54 100644
--- a/index.xml
+++ b/index.xml
@@ -8,7 +8,9 @@ Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
-Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
+Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
+@FilterWith({FirstFilter.java, SecondFilter.java}) @Singleton @WebController public class Controller { @FilterWith({ThirdFiter.java}) @RequestRouting public Result showHomePage() { return Result.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.1.1 2022-07-24
diff --git a/sitemap.xml b/sitemap.xml
index 8f04f01..b9009f9 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file

From 4085765411500e45b598c552a3e40f59355662da Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Sat, 30 Jul 2022 06:39:33 +0000
Subject: [PATCH 11/75] Automated website build

---
 doc/index.xml              | 4 ++--
 doc/web/filters/index.html | 8 ++++----
 index.xml                  | 4 ++--
 3 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/doc/index.xml b/doc/index.xml
index 9ca7987..0e04051 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -9,8 +9,8 @@ Bindable classes (see below) classes implementing the TypeConverter interface cl
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
-Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
-@FilterWith({FirstFilter.java, SecondFilter.java}) @Singleton @WebController public class Controller { @FilterWith({ThirdFiter.java}) @RequestRouting public Result showHomePage() { return Result.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+&nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
+@FilterWith({FirstFilter.java, SecondFilter.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index 1be0e57..9fcac7f 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -1,8 +1,9 @@
 Void Framework – Filters
+&nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the">Void Framework – Filters
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
+Note that the use of dependencies direct injection is possible in filters.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
 @Singleton
 @WebController
 public class Controller {
@@ -30,8 +31,7 @@
         return filterChain.applyNext(context);
     }
 }
-
 
-Note that the use of dependencies direct injection is possible in filters.

© 2022 Void Framework

+

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/index.xml b/index.xml
index 99dce54..bb57ea8 100644
--- a/index.xml
+++ b/index.xml
@@ -9,8 +9,8 @@ Bindable classes (see below) classes implementing the TypeConverter interface cl
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
-Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
-@FilterWith({FirstFilter.java, SecondFilter.java}) @Singleton @WebController public class Controller { @FilterWith({ThirdFiter.java}) @RequestRouting public Result showHomePage() { return Result.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+&nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
+@FilterWith({FirstFilter.java, SecondFilter.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.1.1 2022-07-24

From a7fa13c850d69ed7511b9ddf90014720561cf251 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Sun, 31 Jul 2022 07:31:28 +0000
Subject: [PATCH 12/75] Automated website build

---
 doc/index.xml | 26 ++++++++++++++++++++++++--
 index.xml     | 30 +++++++++++++++++++++++++++---
 sitemap.xml   |  2 +-
 3 files changed, 52 insertions(+), 6 deletions(-)

diff --git a/doc/index.xml b/doc/index.xml
index 0e04051..3360463 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,24 +1,46 @@
 Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioData sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
+Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Data sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
+Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
+Example
+@Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
+Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
+@FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
+&nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
+priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+&nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
+The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
+openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
+Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
+#&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
+Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Upgrading from old versionhttps://voidframework.dev/doc/getting-started/upgrading-from-old-version/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/upgrading-from-old-version/Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.
 1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now requiredUsing cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
+&nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+To enable this module, just add following lines to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
diff --git a/index.xml b/index.xml
index bb57ea8..97667b3 100644
--- a/index.xml
+++ b/index.xml
@@ -1,26 +1,50 @@
 Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioData sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
+Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Data sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
+Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
+Example
+@Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
-Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
+Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
+Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
+&nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
+@FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
+priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+&nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
+The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.1.1 2022-07-24
 Improved Change CSRF signature algorithm to HMACSHA256 Fixed Error 500 CSRF when POST request render template 1.1.0 2022-07-22
+New Methods on Reflection util class: getAnnotatedField(Object, Class<? extends Annotation>) and getAnnotatedField(Class, Class<? extends Annotation>) New Configuration keys to define number of I/O and Worker threads (Web) New Redis (base + cache + healthcheck) New CSRF token Improved No longer necessary for HealthChecker to be Singleton Improved Add cache abstraction helper Improved Session signature key configuration is now required Improved Rename ApplicationLauncher to VoidApplication Improved Updated version of all dependencies Fixed Cookie revocation not working Fixed C3P0/HikariCP settings Fixed Issue on routes sorting when regex and capture regex are used Fixed Assets not found when devMode=false Fixed Hibernate : Models not found when application is compiled 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.1.1 2022-07-24
+Improved Change CSRF signature algorithm to HMACSHA256 Fixed Error 500 CSRF when POST request render template 1.1.0 2022-07-22
 New Methods on Reflection util class: getAnnotatedField(Object, Class<? extends Annotation>) and getAnnotatedField(Class, Class<? extends Annotation>) New Configuration keys to define number of I/O and Worker threads (Web) New Redis (base + cache + healthcheck) New CSRF token Improved No longer necessary for HealthChecker to be Singleton Improved Add cache abstraction helper Improved Session signature key configuration is now required Improved Rename ApplicationLauncher to VoidApplication Improved Updated version of all dependencies Fixed Cookie revocation not working Fixed C3P0/HikariCP settings Fixed Issue on routes sorting when regex and capture regex are used Fixed Assets not found when devMode=false Fixed Hibernate : Models not found when application is compiled 1.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
+openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
+Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
+#&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
+Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Upgrading from old versionhttps://voidframework.dev/doc/getting-started/upgrading-from-old-version/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/upgrading-from-old-version/Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.
 1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now requiredUsing cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
+&nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+To enable this module, just add following lines to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
diff --git a/sitemap.xml b/sitemap.xml
index b9009f9..69a585b 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file

From ac2840bc62655919bc10b9810f7ebffda4b50c90 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Mon, 1 Aug 2022 18:09:41 +0000
Subject: [PATCH 13/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/index.html                          |  2 +-
 doc/cache/redis-cache/index.html              |  2 +-
 doc/cache/using-cache/index.html              |  2 +-
 doc/core/boot-sequence/index.html             |  2 +-
 doc/core/class-scanning/index.html            |  2 +-
 doc/core/configuration/index.html             |  2 +-
 doc/core/index.html                           |  2 +-
 doc/core/life-cycle/index.html                |  2 +-
 doc/core/type-conversion/index.html           |  2 +-
 doc/databases/datasource/index.html           |  2 +-
 doc/databases/index.html                      |  2 +-
 .../persistence-hibernate/index.html          |  2 +-
 doc/getting-started/index.html                |  2 +-
 .../new-application/index.html                |  2 +-
 doc/getting-started/requirements/index.html   |  2 +-
 .../upgrading-from-old-version/index.html     |  2 +-
 doc/i18n/index.html                           |  2 +-
 doc/index.html                                |  2 +-
 doc/index.xml                                 |  4 ++-
 .../using-i18n/index.html                     |  2 +-
 doc/web/controller/index.html                 |  2 +-
 doc/web/filters/index.html                    |  4 +--
 doc/web/index.html                            |  2 +-
 doc/web/session/index.html                    | 30 +++++++++++++++++++
 index.xml                                     |  4 ++-
 sitemap.xml                                   |  2 +-
 27 files changed, 61 insertions(+), 27 deletions(-)
 create mode 100644 doc/web/session/index.html

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 06f9ed4..2e49bd1 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,7 +2,7 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
     <version>1.1.1</version>
diff --git a/doc/cache/index.html b/doc/cache/index.html
index 58f64ef..2a4bf93 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Cache

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Cache

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 7331163..073bf10 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
     <version>1.1.1</version>
diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index 3529346..19a0cb0 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,7 +2,7 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
 Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index e788510..a2e082d 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n . c c e f b e o i o n g o m v ( u t o e S r s d r t a t u t a t r">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index 3a8e75f..80d01be 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,7 +2,7 @@
 Bindable classes (see below) classes implementing the TypeConverter interface classes which e">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
 3 types of elements are recognised during the scan:
Bindable classes (see below)
classes implementing the TypeConverter interface
classes which extend AbstractModule (Guice)

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@BindClass Indicates that an annotated class is a “Bindable”
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index a8ef2bb..00504bf 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -1,7 +1,7 @@
 Void Framework – Configuration
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

Custom configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

Custom configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
 

© 2022 Void Framework

 Void Framework is released under the MIT License

 
diff --git a/doc/core/index.html b/doc/core/index.html
index 63b5eb9..5f4c9ce 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Core

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Core

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index 8debf82..3da959d 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index 50db050..3e9dd21 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/databases/datasource/index.html b/doc/databases/datasource/index.html
index 603f8c1..3d02a25 100644
--- a/doc/databases/datasource/index.html
+++ b/doc/databases/datasource/index.html
@@ -1,7 +1,7 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
diff --git a/doc/databases/index.html b/doc/databases/index.html
index c63d4ec..c4d2131 100644
--- a/doc/databases/index.html
+++ b/doc/databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/databases/persistence-hibernate/index.html b/doc/databases/persistence-hibernate/index.html
index 836a18e..195f681 100644
--- a/doc/databases/persistence-hibernate/index.html
+++ b/doc/databases/persistence-hibernate/index.html
@@ -2,7 +2,7 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index f249f6d..ab60aa8 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Getting Started

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Getting Started

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index a7ee5b1..ba5a7ee 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,7 +2,7 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
     <version>1.1.1</version>
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index 81d22e2..28558a9 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index 57e1863..458f6bf 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.1.0 ApplicationLa">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index 5f1a547..fffa628 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Internationalization

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Internationalization

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index e6a96b1..a6bf4df 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Documentation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Documentation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 3360463..898f130 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -34,7 +34,9 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
-openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
+openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+&nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+&nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Upgrading from old versionhttps://voidframework.dev/doc/getting-started/upgrading-from-old-version/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/upgrading-from-old-version/Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.
 1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now requiredUsing cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 9dffc6b..9c3aa60 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
     <version>1.1.1</version>
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index d03e89d..55a04a8 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index 9fcac7f..9e6ed6f 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -2,13 +2,13 @@
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the">Void Framework – Filters
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
 Note that the use of dependencies direct injection is possible in filters.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
 @Singleton
 @WebController
 public class Controller {
 
-    @FilterWith({ThirdFiter.java})
+    @FilterWith({ThirdFilter.java})
     @RequestRouting
     public Result showHomePage() {
         return Result.of("Hello World!");
diff --git a/doc/web/index.html b/doc/web/index.html
index 6779086..f35cbe9 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters

Web

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Web

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/session/index.html b/doc/web/session/index.html
new file mode 100644
index 0000000..dceb108
--- /dev/null
+++ b/doc/web/session/index.html
@@ -0,0 +1,30 @@
+Void Framework – Session
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
+Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie.

Because session is implemented using cookies, there are some implications.The data size is limited to 4 KiB
Only string can be stored

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.

Read value
You can access the session data via the Context. Methods get or getOrDefault can be used.
@Singleton
+@WebController
+public class Controller {
+
+    @RequestRouting
+    public Result sessionExample(final Context ctx) {
+        final String userId = ctx.getSession().get("USER_ID");
+        return Result.of(userId);
+    }
+}
+

Store value
To store value(s), methods put, putAll and putIfAbsent can be used.
@Singleton
+@WebController
+public class Controller {
+
+    @RequestRouting
+    public Result sessionExample(final Context ctx) {
+        final String userId = ctx.getSession().put("USER_ID", "e90b88d4-3c15-4397-b774-d63a0ad89c74");
+        return Result.of(userId);
+    }
+}
+

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/index.xml b/index.xml
index 97667b3..0644326 100644
--- a/index.xml
+++ b/index.xml
@@ -38,7 +38,9 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
-openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
+openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+&nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+&nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Upgrading from old versionhttps://voidframework.dev/doc/getting-started/upgrading-from-old-version/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/upgrading-from-old-version/Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.
 1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now requiredUsing cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
diff --git a/sitemap.xml b/sitemap.xml
index 69a585b..bbebba9 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file

From 689bbb1e085ff77687533328f1629d8a6fd7564c Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Tue, 2 Aug 2022 19:15:24 +0000
Subject: [PATCH 14/75] Automated website build

---
 doc/cache/in-memory-cache/index.html           |  2 +-
 doc/cache/redis-cache/index.html               |  2 +-
 doc/databases/datasource/index.html            |  4 ++--
 doc/databases/persistence-hibernate/index.html |  4 ++--
 doc/getting-started/new-application/index.html |  4 ++--
 doc/index.xml                                  | 12 ++++++------
 doc/internationalization/using-i18n/index.html |  2 +-
 index.xml                                      | 18 ++++++++++--------
 releasenotes/index.html                        |  8 +++++---
 9 files changed, 30 insertions(+), 26 deletions(-)

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 2e49bd1..6c5e494 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.1.1</version>
+    <version>1.1.2</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 073bf10..4b7df54 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.1.1</version>
+    <version>1.1.2</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/databases/datasource/index.html b/doc/databases/datasource/index.html
index 3d02a25..03b0757 100644
--- a/doc/databases/datasource/index.html
+++ b/doc/databases/datasource/index.html
@@ -5,12 +5,12 @@
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.1.1</version>
+    <version>1.1.2</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.1.1</version>
+    <version>1.1.2</version>
 </dependency>
 
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/databases/persistence-hibernate/index.html b/doc/databases/persistence-hibernate/index.html
index 195f681..6e2e598 100644
--- a/doc/databases/persistence-hibernate/index.html
+++ b/doc/databases/persistence-hibernate/index.html
@@ -6,7 +6,7 @@
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.1.1</version>
+    <version>1.1.2</version>
 </dependency>
 

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
 Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

Exemple
@Entity
@@ -74,7 +74,7 @@
 
         return conversion.convert(newsModelList, NewsModel.class, News.class);
     }
-

© 2022 Void Framework

+

Speed-up PersistenceEntityFactory initialization time
By default, Void Framework tells the PersistenceEntityFactory to scan all JARs of the application’s and dependencies. This scan is necessary to detect models. If you want to greatly improve this initialization time, it is advisable to set the voidframework.persistence.modelsJarUrlPattern configuration key to indicate which JARs to keep. The could be null, a regular expression, or auto (default value).
If the configuration is set to null, only the current JAR / classpath (when started in IDE) will be used. auto is like using the regular expression (.*).

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index ba5a7ee..ffccfdb 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.1.1</version>
+    <version>1.1.2</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.1.1</version>
+    <version>1.1.2</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/index.xml b/doc/index.xml
index 898f130..48fc392 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -5,12 +5,12 @@ Configuration Void Framework offers different implementations, depending on the
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
@@ -43,6 +43,6 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 9c3aa60..18f809c 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.1.1</version>
+    <version>1.1.2</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/index.xml b/index.xml
index 0644326..98b48b9 100644
--- a/index.xml
+++ b/index.xml
@@ -5,12 +5,12 @@ Configuration Void Framework offers different implementations, depending on the
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
@@ -28,9 +28,11 @@ The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
-priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.1.1 2022-07-24
+priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.1.2 2022-08-02
+Fixed EntityManagerFactory don't find models on multiple-jars project 1.1.1 2022-07-24
 Improved Change CSRF signature algorithm to HMACSHA256 Fixed Error 500 CSRF when POST request render template 1.1.0 2022-07-22
-New Methods on Reflection util class: getAnnotatedField(Object, Class<? extends Annotation>) and getAnnotatedField(Class, Class<? extends Annotation>) New Configuration keys to define number of I/O and Worker threads (Web) New Redis (base + cache + healthcheck) New CSRF token Improved No longer necessary for HealthChecker to be Singleton Improved Add cache abstraction helper Improved Session signature key configuration is now required Improved Rename ApplicationLauncher to VoidApplication Improved Updated version of all dependencies Fixed Cookie revocation not working Fixed C3P0/HikariCP settings Fixed Issue on routes sorting when regex and capture regex are used Fixed Assets not found when devMode=false Fixed Hibernate : Models not found when application is compiled 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.1.1 2022-07-24
+New Methods on Reflection util class: getAnnotatedField(Object, Class<? extends Annotation>) and getAnnotatedField(Class, Class<? extends Annotation>) New Configuration keys to define number of I/O and Worker threads (Web) New Redis (base + cache + healthcheck) New CSRF token Improved No longer necessary for HealthChecker to be Singleton Improved Add cache abstraction helper Improved Session signature key configuration is now required Improved Rename ApplicationLauncher to VoidApplication Improved Updated version of all dependencies Fixed Cookie revocation not working Fixed C3P0/HikariCP settings Fixed Issue on routes sorting when regex and capture regex are used Fixed Assets not found when devMode=false Fixed Hibernate : Models not found when application is compiled 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.1.2 2022-08-02
+Fixed EntityManagerFactory don't find models on multiple-jars project 1.1.1 2022-07-24
 Improved Change CSRF signature algorithm to HMACSHA256 Fixed Error 500 CSRF when POST request render template 1.1.0 2022-07-22
 New Methods on Reflection util class: getAnnotatedField(Object, Class<? extends Annotation>) and getAnnotatedField(Class, Class<? extends Annotation>) New Configuration keys to define number of I/O and Worker threads (Web) New Redis (base + cache + healthcheck) New CSRF token Improved No longer necessary for HealthChecker to be Singleton Improved Add cache abstraction helper Improved Session signature key configuration is now required Improved Rename ApplicationLauncher to VoidApplication Improved Updated version of all dependencies Fixed Cookie revocation not working Fixed C3P0/HikariCP settings Fixed Issue on routes sorting when regex and capture regex are used Fixed Assets not found when devMode=false Fixed Hibernate : Models not found when application is compiled 1.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
@@ -47,6 +49,6 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 18dd61c..f9c073d 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,9 +1,11 @@
-Void Framework – Release notes
+New Methods on Refl">Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.1.1

+Release notes
1.1.2

+2022-08-02
Fixed EntityManagerFactory don't find models on multiple-jars project
1.1.1

 2022-07-24
Improved Change CSRF signature algorithm to HMACSHA256
Fixed Error 500 CSRF when POST request render template

1.1.0

 2022-07-22
New Methods on Reflection util class: getAnnotatedField(Object, Class) and getAnnotatedField(Class, Class)
New Configuration keys to define number of I/O and Worker threads (Web)
New Redis (base + cache + healthcheck)
New CSRF token
Improved No longer necessary for HealthChecker to be Singleton
Improved Add cache abstraction helper
Improved Session signature key configuration is now required
Improved Rename ApplicationLauncher to VoidApplication
Improved Updated version of all dependencies
Fixed Cookie revocation not working
Fixed C3P0/HikariCP settings
Fixed Issue on routes sorting when regex and capture regex are used
Fixed Assets not found when devMode=false
Fixed Hibernate : Models not found when application is compiled

1.0.1

 2022-07-08
New Ability to retrieve XML body content as Java object
Improved Cache management : rename the annotation Cache to CacheResult and add CacheRemove
Fixed Removed I18N reference from Hibernate module
Fixed Transactional annotation : rollback not occur on unchecked exception
Fixed Routes are randomly sorted

1.0.0


From 981101f39d4c6626637953876b15f08d17e6b070 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Tue, 2 Aug 2022 19:18:24 +0000
Subject: [PATCH 15/75] Automated website build

---
 releasenotes/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/releasenotes/index.html b/releasenotes/index.html
index f9c073d..d4a2287 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -5,7 +5,7 @@
 Void Framework
Documentation
    
 Release notes
1.1.2

-2022-08-02
Fixed EntityManagerFactory don't find models on multiple-jars project
1.1.1

+2022-08-02
Fixed EntityManagerFactory don't find models on multiple-jars project

1.1.1

 2022-07-24
Improved Change CSRF signature algorithm to HMACSHA256
Fixed Error 500 CSRF when POST request render template

1.1.0

 2022-07-22
New Methods on Reflection util class: getAnnotatedField(Object, Class) and getAnnotatedField(Class, Class)
New Configuration keys to define number of I/O and Worker threads (Web)
New Redis (base + cache + healthcheck)
New CSRF token
Improved No longer necessary for HealthChecker to be Singleton
Improved Add cache abstraction helper
Improved Session signature key configuration is now required
Improved Rename ApplicationLauncher to VoidApplication
Improved Updated version of all dependencies
Fixed Cookie revocation not working
Fixed C3P0/HikariCP settings
Fixed Issue on routes sorting when regex and capture regex are used
Fixed Assets not found when devMode=false
Fixed Hibernate : Models not found when application is compiled

1.0.1

 2022-07-08
New Ability to retrieve XML body content as Java object
Improved Cache management : rename the annotation Cache to CacheResult and add CacheRemove
Fixed Removed I18N reference from Hibernate module
Fixed Transactional annotation : rollback not occur on unchecked exception
Fixed Routes are randomly sorted

1.0.0


From abe716a60cab0d32a4eb08a96f09f62f90a66cc1 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Wed, 3 Aug 2022 09:31:17 +0000
Subject: [PATCH 16/75] Automated website build

---
 releasenotes/index.html | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/releasenotes/index.html b/releasenotes/index.html
index d4a2287..5a21b37 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -5,10 +5,10 @@
 Void Framework
Documentation
    
 Release notes
1.1.2

-2022-08-02
Fixed EntityManagerFactory don't find models on multiple-jars project

1.1.1

-2022-07-24
Improved Change CSRF signature algorithm to HMACSHA256
Fixed Error 500 CSRF when POST request render template

1.1.0

-2022-07-22
New Methods on Reflection util class: getAnnotatedField(Object, Class) and getAnnotatedField(Class, Class)
New Configuration keys to define number of I/O and Worker threads (Web)
New Redis (base + cache + healthcheck)
New CSRF token
Improved No longer necessary for HealthChecker to be Singleton
Improved Add cache abstraction helper
Improved Session signature key configuration is now required
Improved Rename ApplicationLauncher to VoidApplication
Improved Updated version of all dependencies
Fixed Cookie revocation not working
Fixed C3P0/HikariCP settings
Fixed Issue on routes sorting when regex and capture regex are used
Fixed Assets not found when devMode=false
Fixed Hibernate : Models not found when application is compiled

1.0.1

-2022-07-08
New Ability to retrieve XML body content as Java object
Improved Cache management : rename the annotation Cache to CacheResult and add CacheRemove
Fixed Removed I18N reference from Hibernate module
Fixed Transactional annotation : rollback not occur on unchecked exception
Fixed Routes are randomly sorted

1.0.0

+2022-08-02
Fixed EntityManagerFactory don't find models on multiple-jars project

1.1.1

+2022-07-24
Improved Change CSRF signature algorithm to HMACSHA256
Fixed Error 500 CSRF when POST request render template

1.1.0

+2022-07-22
New Methods on Reflection util class: getAnnotatedField(Object, Class) and getAnnotatedField(Class, Class)
New Configuration keys to define number of I/O and Worker threads (Web)
New Redis (base + cache + healthcheck)
New CSRF token
Improved No longer necessary for HealthChecker to be Singleton
Improved Add cache abstraction helper
Improved Session signature key configuration is now required
Improved Rename ApplicationLauncher to VoidApplication
Improved Updated version of all dependencies
Fixed Cookie revocation not working
Fixed C3P0/HikariCP settings
Fixed Issue on routes sorting when regex and capture regex are used
Fixed Assets not found when devMode=false
Fixed Hibernate : Models not found when application is compiled

1.0.1

+2022-07-08
New Ability to retrieve XML body content as Java object
Improved Cache management : rename the annotation Cache to CacheResult and add CacheRemove
Fixed Removed I18N reference from Hibernate module
Fixed Transactional annotation : rollback not occur on unchecked exception
Fixed Routes are randomly sorted

1.0.0

 2022-07-02
Initial release

© 2022 Void Framework

 Void Framework is released under the MIT License

 

From 428358e2d7de1139a13ff66526b4ea349ece16f6 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 4 Aug 2022 17:45:59 +0000
Subject: [PATCH 17/75] Automated website build

---
 doc/cache/in-memory-cache/index.html             |  2 +-
 doc/cache/index.html                             |  2 +-
 doc/cache/redis-cache/index.html                 |  2 +-
 doc/cache/using-cache/index.html                 |  2 +-
 doc/core/boot-sequence/index.html                |  2 +-
 doc/core/class-scanning/index.html               |  2 +-
 doc/core/configuration/index.html                |  2 +-
 doc/core/index.html                              |  2 +-
 doc/core/life-cycle/index.html                   |  2 +-
 doc/core/type-conversion/index.html              |  2 +-
 doc/databases/datasource/index.html              |  2 +-
 doc/databases/index.html                         |  2 +-
 doc/databases/persistence-hibernate/index.html   |  2 +-
 doc/getting-started/index.html                   |  2 +-
 doc/getting-started/new-application/index.html   |  2 +-
 doc/getting-started/requirements/index.html      |  2 +-
 .../upgrading-from-old-version/index.html        |  2 +-
 doc/i18n/index.html                              |  2 +-
 doc/index.html                                   |  2 +-
 doc/index.xml                                    |  3 ++-
 doc/internationalization/using-i18n/index.html   |  2 +-
 doc/web/controller/index.html                    |  2 +-
 doc/web/filters/index.html                       |  2 +-
 doc/web/index.html                               |  2 +-
 doc/web/security-csrf/index.html                 | 16 ++++++++++++++++
 doc/web/session/index.html                       |  2 +-
 index.xml                                        |  3 ++-
 sitemap.xml                                      |  2 +-
 28 files changed, 45 insertions(+), 27 deletions(-)
 create mode 100644 doc/web/security-csrf/index.html

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 6c5e494..329ec3c 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,7 +2,7 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
     <version>1.1.2</version>
diff --git a/doc/cache/index.html b/doc/cache/index.html
index 2a4bf93..8fcee88 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Cache

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Cache

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 4b7df54..2bb6642 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
     <version>1.1.2</version>
diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index 19a0cb0..05b9ddf 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,7 +2,7 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
 Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index a2e082d..2eee2a5 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n . c c e f b e o i o n g o m v ( u t o e S r s d r t a t u t a t r">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index 80d01be..7792503 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,7 +2,7 @@
 Bindable classes (see below) classes implementing the TypeConverter interface classes which e">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
 3 types of elements are recognised during the scan:
Bindable classes (see below)
classes implementing the TypeConverter interface
classes which extend AbstractModule (Guice)

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@BindClass Indicates that an annotated class is a “Bindable”
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index 00504bf..29f64a8 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -1,7 +1,7 @@
 Void Framework – Configuration
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

Custom configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

Custom configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
 

© 2022 Void Framework

 Void Framework is released under the MIT License

 
diff --git a/doc/core/index.html b/doc/core/index.html
index 5f4c9ce..7886197 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Core

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Core

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index 3da959d..2e6bd04 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index 3e9dd21..ffa48cd 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/databases/datasource/index.html b/doc/databases/datasource/index.html
index 03b0757..e9a0951 100644
--- a/doc/databases/datasource/index.html
+++ b/doc/databases/datasource/index.html
@@ -1,7 +1,7 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
diff --git a/doc/databases/index.html b/doc/databases/index.html
index c4d2131..420c50c 100644
--- a/doc/databases/index.html
+++ b/doc/databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/databases/persistence-hibernate/index.html b/doc/databases/persistence-hibernate/index.html
index 6e2e598..fbdad1e 100644
--- a/doc/databases/persistence-hibernate/index.html
+++ b/doc/databases/persistence-hibernate/index.html
@@ -2,7 +2,7 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index ab60aa8..c273923 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Getting Started

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Getting Started

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index ffccfdb..fbdb2a1 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,7 +2,7 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
     <version>1.1.2</version>
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index 28558a9..e18e40a 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index 458f6bf..148d075 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.1.0 ApplicationLa">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index fffa628..2de031a 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Internationalization

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Internationalization

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index a6bf4df..462f539 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Documentation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Documentation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 48fc392..fd84b77 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -18,7 +18,8 @@ Example
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
-Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
+Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.CSRFhttps://voidframework.dev/doc/web/security-csrf/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-csrf/Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
+&nbsp; It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP. Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 18f809c..8ba2039 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
     <version>1.1.2</version>
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index 55a04a8..9d13f52 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index 9e6ed6f..44df7d5 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the">Void Framework – Filters
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
 Note that the use of dependencies direct injection is possible in filters.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
 @Singleton
 @WebController
diff --git a/doc/web/index.html b/doc/web/index.html
index f35cbe9..797ff2a 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Web

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Web

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/security-csrf/index.html b/doc/web/security-csrf/index.html
new file mode 100644
index 0000000..d80d546
--- /dev/null
+++ b/doc/web/security-csrf/index.html
@@ -0,0 +1,16 @@
+Void Framework – CSRF
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
+It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP.
Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
+
+    web {
+        globalFilters += "dev.voidframework.web.csrf.CSRFFilter"
+    }
+}
+

@NoCSRF
Although you have enabled the CSRF filter, you may need to disable CSRF protection on a specific endpoint. To do this, you can use the @NoCSRF annotation which will indicate that the CSRF token does not need to be checked.

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/web/session/index.html b/doc/web/session/index.html
index dceb108..39efb32 100644
--- a/doc/web/session/index.html
+++ b/doc/web/session/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the session is not stored on the server side, but on the client side v">Void Framework – Session
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Filters
Session

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
 Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie.

Because session is implemented using cookies, there are some implications.The data size is limited to 4 KiB
Only string can be stored

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.

Read value
You can access the session data via the Context. Methods get or getOrDefault can be used.
@Singleton
 @WebController
 public class Controller {
diff --git a/index.xml b/index.xml
index 98b48b9..67a3a83 100644
--- a/index.xml
+++ b/index.xml
@@ -18,7 +18,8 @@ Example
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
-Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
+Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.CSRFhttps://voidframework.dev/doc/web/security-csrf/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-csrf/Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
+&nbsp; It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP. Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
diff --git a/sitemap.xml b/sitemap.xml
index bbebba9..35d17f1 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file

From 9da1c40bee583603b3ff05c3e63e8e6c68ccf25e Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Sun, 7 Aug 2022 17:25:03 +0000
Subject: [PATCH 18/75] Automated website build

---
 doc/cache/in-memory-cache/index.html             |  2 +-
 doc/cache/index.html                             |  2 +-
 doc/cache/redis-cache/index.html                 |  2 +-
 doc/cache/using-cache/index.html                 |  2 +-
 doc/core/boot-sequence/index.html                |  2 +-
 doc/core/class-scanning/index.html               |  2 +-
 doc/core/configuration/index.html                |  2 +-
 doc/core/index.html                              |  2 +-
 doc/core/life-cycle/index.html                   |  2 +-
 doc/core/type-conversion/index.html              |  2 +-
 doc/databases/datasource/index.html              |  2 +-
 doc/databases/index.html                         |  2 +-
 doc/databases/persistence-hibernate/index.html   |  2 +-
 doc/getting-started/index.html                   |  2 +-
 doc/getting-started/new-application/index.html   |  2 +-
 doc/getting-started/requirements/index.html      |  2 +-
 .../upgrading-from-old-version/index.html        |  2 +-
 doc/i18n/index.html                              |  2 +-
 doc/index.html                                   |  2 +-
 doc/index.xml                                    |  6 ++++--
 doc/internationalization/using-i18n/index.html   |  2 +-
 doc/web/controller/index.html                    |  2 +-
 doc/web/filters/index.html                       |  2 +-
 doc/web/index.html                               |  2 +-
 doc/web/security-csrf/index.html                 |  2 +-
 doc/web/security-headers/index.html              | 16 ++++++++++++++++
 doc/web/session/index.html                       |  2 +-
 index.xml                                        | 14 +++++++++-----
 releasenotes/index.html                          | 14 +++++++-------
 sitemap.xml                                      |  2 +-
 30 files changed, 62 insertions(+), 40 deletions(-)
 create mode 100644 doc/web/security-headers/index.html

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 329ec3c..6f2a7d5 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,7 +2,7 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
     <version>1.1.2</version>
diff --git a/doc/cache/index.html b/doc/cache/index.html
index 8fcee88..7116724 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Cache

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Cache

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 2bb6642..53636ae 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
     <version>1.1.2</version>
diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index 05b9ddf..8508c84 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,7 +2,7 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
 Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index 2eee2a5..fe51d1a 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n . c c e f b e o i o n g o m v ( u t o e S r s d r t a t u t a t r">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index 7792503..a59f5d7 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,7 +2,7 @@
 Bindable classes (see below) classes implementing the TypeConverter interface classes which e">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
 3 types of elements are recognised during the scan:
Bindable classes (see below)
classes implementing the TypeConverter interface
classes which extend AbstractModule (Guice)

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@BindClass Indicates that an annotated class is a “Bindable”
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index 29f64a8..bed1b6d 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -1,7 +1,7 @@
 Void Framework – Configuration
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

Custom configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

Custom configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
 

© 2022 Void Framework

 Void Framework is released under the MIT License

 
diff --git a/doc/core/index.html b/doc/core/index.html
index 7886197..9b2f525 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Core

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Core

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index 2e6bd04..36c9d12 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index ffa48cd..7fb0b3d 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/databases/datasource/index.html b/doc/databases/datasource/index.html
index e9a0951..e2f6f6c 100644
--- a/doc/databases/datasource/index.html
+++ b/doc/databases/datasource/index.html
@@ -1,7 +1,7 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
diff --git a/doc/databases/index.html b/doc/databases/index.html
index 420c50c..b07c875 100644
--- a/doc/databases/index.html
+++ b/doc/databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/databases/persistence-hibernate/index.html b/doc/databases/persistence-hibernate/index.html
index fbdad1e..72c5da8 100644
--- a/doc/databases/persistence-hibernate/index.html
+++ b/doc/databases/persistence-hibernate/index.html
@@ -2,7 +2,7 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index c273923..eafcadc 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Getting Started

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Getting Started

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index fbdb2a1..8e0691a 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,7 +2,7 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
     <version>1.1.2</version>
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index e18e40a..4ea04d0 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index 148d075..46c12a7 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.1.0 ApplicationLa">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index 2de031a..4b03a3e 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Internationalization

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Internationalization

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index 462f539..ab76109 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Documentation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Documentation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index fd84b77..1fe53c1 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -35,12 +35,14 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
-openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
+Configuration The following configuration keys can be used in the configuration file of your application.
+voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Upgrading from old versionhttps://voidframework.dev/doc/getting-started/upgrading-from-old-version/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/upgrading-from-old-version/Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.
-1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now requiredUsing cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
+1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now required 1.2.0 The CSRF filter has been moved to the dev.voidframework.web.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 8ba2039..199b19d 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
     <version>1.1.2</version>
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index 9d13f52..85678b2 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index 44df7d5..7c2857f 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the">Void Framework – Filters
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
 Note that the use of dependencies direct injection is possible in filters.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
 @Singleton
 @WebController
diff --git a/doc/web/index.html b/doc/web/index.html
index 797ff2a..31a7556 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Web

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Web

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/security-csrf/index.html b/doc/web/security-csrf/index.html
index d80d546..433430c 100644
--- a/doc/web/security-csrf/index.html
+++ b/doc/web/security-csrf/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is recommended tha">Void Framework – CSRF
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
 It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP.
Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/security-headers/index.html b/doc/web/security-headers/index.html
new file mode 100644
index 0000000..102df81
--- /dev/null
+++ b/doc/web/security-headers/index.html
@@ -0,0 +1,16 @@
+Void Framework – Security headers
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
+You can disable one of the headers by assigning the value null. The header will then not be sent.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
+
+    web {
+        globalFilters += "dev.voidframework.web.filter.security.SecurityHeadersFilter"
+    }
+}
+

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/web/session/index.html b/doc/web/session/index.html
index 39efb32..a43e3c5 100644
--- a/doc/web/session/index.html
+++ b/doc/web/session/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the session is not stored on the server side, but on the client side v">Void Framework – Session
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
 Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie.

Because session is implemented using cookies, there are some implications.The data size is limited to 4 KiB
Only string can be stored

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.

Read value
You can access the session data via the Context. Methods get or getOrDefault can be used.
@Singleton
 @WebController
 public class Controller {
diff --git a/index.xml b/index.xml
index 67a3a83..8470631 100644
--- a/index.xml
+++ b/index.xml
@@ -29,24 +29,28 @@ The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
-priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.1.2 2022-08-02
+priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.2.0 2022-xx-xx
+New Add SecurityHeadersFilter Improved Force EntityManagerFactory initialization during boot sequence Improved Add new Result methods to handle empty content easily Improved Updated version of all dependencies 1.1.2 2022-08-02
 Fixed EntityManagerFactory don't find models on multiple-jars project 1.1.1 2022-07-24
 Improved Change CSRF signature algorithm to HMACSHA256 Fixed Error 500 CSRF when POST request render template 1.1.0 2022-07-22
-New Methods on Reflection util class: getAnnotatedField(Object, Class<? extends Annotation>) and getAnnotatedField(Class, Class<? extends Annotation>) New Configuration keys to define number of I/O and Worker threads (Web) New Redis (base + cache + healthcheck) New CSRF token Improved No longer necessary for HealthChecker to be Singleton Improved Add cache abstraction helper Improved Session signature key configuration is now required Improved Rename ApplicationLauncher to VoidApplication Improved Updated version of all dependencies Fixed Cookie revocation not working Fixed C3P0/HikariCP settings Fixed Issue on routes sorting when regex and capture regex are used Fixed Assets not found when devMode=false Fixed Hibernate : Models not found when application is compiled 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.1.2 2022-08-02
+New Methods on Reflection util class: getAnnotatedField(Object, Class<? extends Annotation>) and getAnnotatedField(Class, Class<?Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.2.0 2022-xx-xx
+New Add SecurityHeadersFilter Improved Force EntityManagerFactory initialization during boot sequence Improved Add new Result methods to handle empty content easily Improved Updated version of all dependencies 1.1.2 2022-08-02
 Fixed EntityManagerFactory don't find models on multiple-jars project 1.1.1 2022-07-24
 Improved Change CSRF signature algorithm to HMACSHA256 Fixed Error 500 CSRF when POST request render template 1.1.0 2022-07-22
-New Methods on Reflection util class: getAnnotatedField(Object, Class<? extends Annotation>) and getAnnotatedField(Class, Class<? extends Annotation>) New Configuration keys to define number of I/O and Worker threads (Web) New Redis (base + cache + healthcheck) New CSRF token Improved No longer necessary for HealthChecker to be Singleton Improved Add cache abstraction helper Improved Session signature key configuration is now required Improved Rename ApplicationLauncher to VoidApplication Improved Updated version of all dependencies Fixed Cookie revocation not working Fixed C3P0/HikariCP settings Fixed Issue on routes sorting when regex and capture regex are used Fixed Assets not found when devMode=false Fixed Hibernate : Models not found when application is compiled 1.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
+New Methods on Reflection util class: getAnnotatedField(Object, Class<? extends Annotation>) and getAnnotatedField(Class, Class<?Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
-openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
+Configuration The following configuration keys can be used in the configuration file of your application.
+voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Upgrading from old versionhttps://voidframework.dev/doc/getting-started/upgrading-from-old-version/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/upgrading-from-old-version/Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.
-1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now requiredUsing cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
+1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now required 1.2.0 The CSRF filter has been moved to the dev.voidframework.web.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 5a21b37..d0e7d53 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,14 +1,14 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.1.2

+Release notes
1.2.0

+2022-xx-xx
New Add SecurityHeadersFilter
Improved Force EntityManagerFactory initialization during boot sequence
Improved Add new Result methods to handle empty content easily
Improved Updated version of all dependencies

1.1.2

 2022-08-02
Fixed EntityManagerFactory don't find models on multiple-jars project

1.1.1

 2022-07-24
Improved Change CSRF signature algorithm to HMACSHA256
Fixed Error 500 CSRF when POST request render template

1.1.0

-2022-07-22
New Methods on Reflection util class: getAnnotatedField(Object, Class) and getAnnotatedField(Class, Class)
New Configuration keys to define number of I/O and Worker threads (Web)
New Redis (base + cache + healthcheck)
New CSRF token
Improved No longer necessary for HealthChecker to be Singleton
Improved Add cache abstraction helper
Improved Session signature key configuration is now required
Improved Rename ApplicationLauncher to VoidApplication
Improved Updated version of all dependencies
Fixed Cookie revocation not working
Fixed C3P0/HikariCP settings
Fixed Issue on routes sorting when regex and capture regex are used
Fixed Assets not found when devMode=false
Fixed Hibernate : Models not found when application is compiled

1.0.1

-2022-07-08
New Ability to retrieve XML body content as Java object
Improved Cache management : rename the annotation Cache to CacheResult and add CacheRemove
Fixed Removed I18N reference from Hibernate module
Fixed Transactional annotation : rollback not occur on unchecked exception
Fixed Routes are randomly sorted

1.0.0

+2022-07-22
New Methods on Reflection util class: getAnnotatedField(Object, Class) and getAnnotatedField(Class, Class)
New Configuration keys to define number of I/O and Worker threads (Web)
New Redis (base + cache + healthcheck)
New CSRF token
Improved No longer necessary for HealthChecker to be Singleton
Improved Add cache abstraction helper
Improved Session signature key configuration is now required
Improved Rename ApplicationLauncher to VoidApplication
Improved Updated version of all dependencies
Fixed Cookie revocation not working
Fixed C3P0/HikariCP settings
Fixed Issue on routes sorting when regex and capture regex are used
Fixed Assets not found when devMode=false
Fixed Hibernate : Models not found when application is compiled

1.0.1

+2022-07-08
New Ability to retrieve XML body content as Java object
Improved Cache management : rename the annotation Cache to CacheResult and add CacheRemove
Fixed Removed I18N reference from Hibernate module
Fixed Transactional annotation : rollback not occur on unchecked exception
Fixed Routes are randomly sorted

1.0.0

 2022-07-02
Initial release

© 2022 Void Framework

 Void Framework is released under the MIT License

 
diff --git a/sitemap.xml b/sitemap.xml
index 35d17f1..b2da983 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file

From e706d4f3a211e6a6f1113ceb09ad0b9e080dbb57 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Mon, 5 Sep 2022 19:29:21 +0000
Subject: [PATCH 19/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  4 +-
 doc/cache/index.html                          |  2 +-
 doc/cache/redis-cache/index.html              |  6 +-
 doc/cache/using-cache/index.html              |  2 +-
 doc/core/boot-sequence/index.html             |  4 +-
 doc/core/class-scanning/index.html            |  2 +-
 doc/core/configuration/index.html             | 73 ++++++++++++++++++-
 doc/core/index.html                           |  2 +-
 doc/core/life-cycle/index.html                |  2 +-
 doc/core/type-conversion/index.html           |  2 +-
 doc/databases/datasource/index.html           |  6 +-
 doc/databases/index.html                      |  2 +-
 .../persistence-hibernate/index.html          |  4 +-
 doc/getting-started/index.html                |  2 +-
 .../new-application/index.html                |  6 +-
 doc/getting-started/requirements/index.html   |  2 +-
 .../upgrading-from-old-version/index.html     |  2 +-
 doc/i18n/index.html                           |  2 +-
 doc/index.html                                |  2 +-
 doc/index.xml                                 | 30 +++++---
 .../using-i18n/index.html                     |  4 +-
 doc/template/freemarker/index.html            | 16 ++++
 doc/template/index.html                       |  8 ++
 doc/web/controller/index.html                 |  2 +-
 doc/web/filters/index.html                    |  4 +-
 doc/web/index.html                            |  2 +-
 doc/web/render-template/index.html            | 25 +++++++
 doc/web/security-csrf/index.html              |  4 +-
 doc/web/security-headers/index.html           |  4 +-
 doc/web/session/index.html                    |  4 +-
 index.xml                                     | 38 +++++-----
 releasenotes/index.html                       |  5 +-
 sitemap.xml                                   |  2 +-
 33 files changed, 199 insertions(+), 76 deletions(-)
 create mode 100644 doc/template/freemarker/index.html
 create mode 100644 doc/template/index.html
 create mode 100644 doc/web/render-template/index.html

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 6f2a7d5..86d2dca 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,10 +2,10 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.1.2</version>
+    <version>1.2.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/index.html b/doc/cache/index.html
index 7116724..b088ecb 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Cache

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Cache

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 53636ae..134e274 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -1,11 +1,11 @@
 Void Framework – Cache engine : Redis
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.1.2</version>
+    <version>1.2.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index 8508c84..7b704b4 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,7 +2,7 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
 Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index fe51d1a..31160c9 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -1,8 +1,8 @@
 Void Framework – Boot sequence
+S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c . t u r c a h i l l P . c c e r b e o c o o n o v o m v">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index a59f5d7..ebdde37 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,7 +2,7 @@
 Bindable classes (see below) classes implementing the TypeConverter interface classes which e">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
 3 types of elements are recognised during the scan:
Bindable classes (see below)
classes implementing the TypeConverter interface
classes which extend AbstractModule (Guice)

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@BindClass Indicates that an annotated class is a “Bindable”
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index bed1b6d..afce41a 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -1,8 +1,77 @@
 Void Framework – Configuration
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

Custom configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
-

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+

Remote configuration
Once packaged, you will probably need to modulate the configuration of the application depending on the environment (ie: development, integration, production). The typical example is the configuration of the data source, you cannot define this information directly in the configuration file included in the Jars files. Void Framework allows you to load configurations that will be stored elsewhere, such as on etcd or vault.
To enable remote configuration loading, you must declare one or more providers to be used via the configuration key voidframework.core.remoteConfiguration.providers.
 
+If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
+  <groupId>dev.voidframework</groupId>
+  <artifactId>voidframework-remoteconf-etcd</artifactId>
+  <version>1.2.0</version>
+</dependency>
+
voidframework {
+    code {
+        remoteConfiguration {
+            providers = "dev.voidframework.remoteconfiguration.provider.EtcdRemoteConfigurationProvider"
+
+            # Configuration of the remote configuration provider "etcd"
+            etcd {
+
+                # API endpoint. HTTPS endpoint could be used,
+                # but the SSL certificate must be valid
+                endpoint = "http://127.0.0.1:2379/"
+                endpoint = ${?VOID_REMOTECONF_ETCD_ENDPOINT}
+
+                # Authentication username
+                username = ""
+                username = ${?VOID_REMOTECONF_ETCD_USERNAME}
+
+                # Authentication password
+                password = ""
+                password = ${?VOID_REMOTECONF_ETCD_PASSWORD}
+
+                # Prefix. Get only values with key beginning
+                # with the configured prefix. With etcd, it
+                # must be a directory.
+                prefix = "/"
+                prefix = ${?VOID_REMOTECONF_ETCD_PREFIX}
+            }
+        }
+    }
+}
+
Provider “http”
<dependency>
+  <groupId>dev.voidframework</groupId>
+  <artifactId>voidframework-remoteconf-http</artifactId>
+  <version>1.2.0</version>
+</dependency>
+
voidframework {
+    code {
+        remoteConfiguration {
+            providers = "dev.voidframework.remoteconfiguration.provider.HttpRemoteConfigurationProvider"
+
+            # Configuration of the remote configuration provider "http"
+            http {
+
+                # Endpoint. HTTPS endpoint could be used,
+                # but the SSL certificate must be valid
+                endpoint = "http://127.0.0.1:2379/"
+                endpoint = ${?VOID_REMOTECONF_HTTP_ENDPOINT}
+
+                # Method to use (ie: GET, POST, ...)
+                method = "GET"
+                method = ${?VOID_REMOTECONF_HTTP_METHOD}
+
+                # Authentication username
+                username = null
+                username = ${?VOID_REMOTECONF_HTTP_USERNAME}
+
+                # Authentication password
+                password = null
+                password = ${?VOID_REMOTECONF_HTTP_PASSWORD}
+            }
+        }
+    }
+}
+

Creating a Remote configuration provider
Creating a new provider is very easy. Simply implement the RemoteConfigurationProvider interface or extend the AbstractRemoteConfigurationProvider abstract class.

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/index.html b/doc/core/index.html
index 9b2f525..cb9432f 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Core

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Core

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index 36c9d12..3fbbef8 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index 7fb0b3d..9760151 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/databases/datasource/index.html b/doc/databases/datasource/index.html
index e2f6f6c..b59a2e4 100644
--- a/doc/databases/datasource/index.html
+++ b/doc/databases/datasource/index.html
@@ -1,16 +1,16 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.1.2</version>
+    <version>1.2.0</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.1.2</version>
+    <version>1.2.0</version>
 </dependency>
 
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/databases/index.html b/doc/databases/index.html
index b07c875..57a539b 100644
--- a/doc/databases/index.html
+++ b/doc/databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/databases/persistence-hibernate/index.html b/doc/databases/persistence-hibernate/index.html
index 72c5da8..c80bc3a 100644
--- a/doc/databases/persistence-hibernate/index.html
+++ b/doc/databases/persistence-hibernate/index.html
@@ -2,11 +2,11 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.1.2</version>
+    <version>1.2.0</version>
 </dependency>
 

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
 Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

Exemple
@Entity
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index eafcadc..45d6bd1 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Getting Started

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Getting Started

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 8e0691a..2b43c3e 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,15 +2,15 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.1.2</version>
+    <version>1.2.0</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.1.2</version>
+    <version>1.2.0</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index 4ea04d0..eea2c8b 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index 46c12a7..2868631 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.1.0 ApplicationLa">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index 4b03a3e..b539f4b 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Internationalization

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Internationalization

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index ab76109..bb3a8f5 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Documentation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Documentation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 1fe53c1..43e878e 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -2,15 +2,15 @@
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Data sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
-S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
-S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
@@ -23,13 +23,19 @@ Maven The very first dependency to include in your pom.xml is voidframework-core
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
-@FilterWith({FirstFilter.java, SecondFilter.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+@FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
+Method Description config Retrieves a value from the configuration displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, &hellip;) i18n / _ Translates a message urlfor Retrieves an URL from the router (reverse router) Variable Description isDevMode Indicates whether the application is in dev mode lang Contains the current language languages Contains all available languages voidFrameworkVersion Contains the current Void Framework version &nbsp; FreeMarker provides a lot of other built-in methods & variables.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
+Method Description config Retrieves a value from the configuration displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, &hellip;) i18n / _ Translates a message urlfor Retrieves an URL from the router (reverse router) Variable Description isDevMode Indicates whether the application is in dev mode lang Contains the current language languages Contains all available languages voidFrameworkVersion Contains the current Void Framework version &nbsp; FreeMarker provides a lot of other built-in methods & variables.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
-priority is used to define when the method will be called in relation to the others.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
+priority is used to define when the method will be called in relation to the others.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
+Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
@@ -42,10 +48,10 @@ voidframework.web.securityHeaders.contentTypeOptions the value for the header &a
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Upgrading from old versionhttps://voidframework.dev/doc/getting-started/upgrading-from-old-version/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/upgrading-from-old-version/Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.
-1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now required 1.2.0 The CSRF filter has been moved to the dev.voidframework.web.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
+1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now required 1.2.0 The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 199b19d..7cbe5b9 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,10 +1,10 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.1.2</version>
+    <version>1.2.0</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
new file mode 100644
index 0000000..a390874
--- /dev/null
+++ b/doc/template/freemarker/index.html
@@ -0,0 +1,16 @@
+Void Framework – FreeMarker
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
+    <groupId>dev.voidframework</groupId>
+    <artifactId>voidframework-template-freemarker</artifactId>
+    <version>1.2.0</version>
+</dependency>
+

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
+FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
+on the official website.

Templates location
Templates should be placed in the resources/views directory.

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/template/index.html b/doc/template/index.html
new file mode 100644
index 0000000..6be0766
--- /dev/null
+++ b/doc/template/index.html
@@ -0,0 +1,8 @@
+Void Framework – Template
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Template

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index 85678b2..633312e 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index 7c2857f..d792976 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the">Void Framework – Filters
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
 Note that the use of dependencies direct injection is possible in filters.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
 @Singleton
 @WebController
@@ -16,7 +16,7 @@
 }
 

Global filters
In case the filter have to be enabled globally (it will be used for all requests), it must be declared in the application configuration file with the configuration key voidframework.web.globalFilters :
voidframework {
     web {
-        globalFilters += "dev.voidframework.web.csrf.CSRFFilter"
+        globalFilters += "dev.voidframework.web.http.filter.csrf.CSRFFilter"
     }
 }
 

Passing attributes
If you need to pass values which should not be passed through the session from one filter to another, or simply from a filter to a controller, you can use Context attributes. This is a simple way of passing values while maintaining their type.
@Singleton
diff --git a/doc/web/index.html b/doc/web/index.html
index 31a7556..87e1369 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Web

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Web

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/render-template/index.html b/doc/web/render-template/index.html
new file mode 100644
index 0000000..d7a21d3
--- /dev/null
+++ b/doc/web/render-template/index.html
@@ -0,0 +1,25 @@
+Void Framework – Render template
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Example
controller/HomeController.java
@Singleton
+@WebController
+public class HomeController {
+
+    @RequestRouting
+    public Result homepage(final Context ctx) {
+        return Result.ok(
+            TemplateResult.of("homepage.ftl", Map.of("greating", "Hello World")));
+    }
+}
+
resources/views/homepage.ftl
<!DOCTYPE html>
+<html lang="${lang!}">
+    <body>
+      <h1>${greating}</h1>
+    </body>
+</html>
+

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/web/security-csrf/index.html b/doc/web/security-csrf/index.html
index 433430c..b9de58d 100644
--- a/doc/web/security-csrf/index.html
+++ b/doc/web/security-csrf/index.html
@@ -2,11 +2,11 @@
 &nbsp; It is recommended tha">Void Framework – CSRF
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
 It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP.
Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
-        globalFilters += "dev.voidframework.web.csrf.CSRFFilter"
+        globalFilters += "dev.voidframework.web.http.filter.csrf.CSRFFilter"
     }
 }
 

@NoCSRF
Although you have enabled the CSRF filter, you may need to disable CSRF protection on a specific endpoint. To do this, you can use the @NoCSRF annotation which will indicate that the CSRF token does not need to be checked.

© 2022 Void Framework

diff --git a/doc/web/security-headers/index.html b/doc/web/security-headers/index.html
index 102df81..09dac59 100644
--- a/doc/web/security-headers/index.html
+++ b/doc/web/security-headers/index.html
@@ -2,11 +2,11 @@
 Configuration The following configuration keys can be used in the configuration">Void Framework – Security headers
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
 You can disable one of the headers by assigning the value null. The header will then not be sent.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
-        globalFilters += "dev.voidframework.web.filter.security.SecurityHeadersFilter"
+        globalFilters += "dev.voidframework.web.http.filter.security.SecurityHeadersFilter"
     }
 }
 

© 2022 Void Framework

diff --git a/doc/web/session/index.html b/doc/web/session/index.html
index a43e3c5..7d9152c 100644
--- a/doc/web/session/index.html
+++ b/doc/web/session/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the session is not stored on the server side, but on the client side v">Void Framework – Session
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Web
Controller
Session
Filters
CSRF
Security headers

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
 Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie.

Because session is implemented using cookies, there are some implications.The data size is limited to 4 KiB
Only string can be stored

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.

Read value
You can access the session data via the Context. Methods get or getOrDefault can be used.
@Singleton
 @WebController
 public class Controller {
@@ -19,7 +19,7 @@
 
     @RequestRouting
     public Result sessionExample(final Context ctx) {
-        final String userId = ctx.getSession().put("USER_ID", "e90b88d4-3c15-4397-b774-d63a0ad89c74");
+        final String userId = ctx.getSession().put("USER_ID", "e90b88d4-3c15");
         return Result.of(userId);
     }
 }
diff --git a/index.xml b/index.xml
index 8470631..90f3f92 100644
--- a/index.xml
+++ b/index.xml
@@ -2,15 +2,15 @@
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Data sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
-S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
-S c a n C l N a O s s p a t h s c R l L e L L a o g i o s ( a i f a s 2 d s e d p a t C a ) G e y c t u r c o h i l n .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
@@ -23,21 +23,21 @@ Maven The very first dependency to include in your pom.xml is voidframework-core
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
-@FilterWith({FirstFilter.java, SecondFilter.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+@FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
+Method Description config Retrieves a value from the configuration displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, &hellip;) i18n / _ Translates a message urlfor Retrieves an URL from the router (reverse router) Variable Description isDevMode Indicates whether the application is in dev mode lang Contains the current language languages Contains all available languages voidFrameworkVersion Contains the current Void Framework version &nbsp; FreeMarker provides a lot of other built-in methods & variables.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
+Method Description config Retrieves a value from the configuration displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, &hellip;) i18n / _ Translates a message urlfor Retrieves an URL from the router (reverse router) Variable Description isDevMode Indicates whether the application is in dev mode lang Contains the current language languages Contains all available languages voidFrameworkVersion Contains the current Void Framework version &nbsp; FreeMarker provides a lot of other built-in methods & variables.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.2.0 2022-xx-xx
-New Add SecurityHeadersFilter Improved Force EntityManagerFactory initialization during boot sequence Improved Add new Result methods to handle empty content easily Improved Updated version of all dependencies 1.1.2 2022-08-02
-Fixed EntityManagerFactory don't find models on multiple-jars project 1.1.1 2022-07-24
-Improved Change CSRF signature algorithm to HMACSHA256 Fixed Error 500 CSRF when POST request render template 1.1.0 2022-07-22
-New Methods on Reflection util class: getAnnotatedField(Object, Class<? extends Annotation>) and getAnnotatedField(Class, Class<?Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.2.0 2022-xx-xx
-New Add SecurityHeadersFilter Improved Force EntityManagerFactory initialization during boot sequence Improved Add new Result methods to handle empty content easily Improved Updated version of all dependencies 1.1.2 2022-08-02
-Fixed EntityManagerFactory don't find models on multiple-jars project 1.1.1 2022-07-24
-Improved Change CSRF signature algorithm to HMACSHA256 Fixed Error 500 CSRF when POST request render template 1.1.0 2022-07-22
-New Methods on Reflection util class: getAnnotatedField(Object, Class<? extends Annotation>) and getAnnotatedField(Class, Class<?Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
+Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053) New Add SecurityHeadersFilter New Add unit test JUnit extension and annotation New Add ability to fetch remote configuration provider & "etcd" remote configuration provider New Add "http" remote configuration provider New Add CharConstants & StringConstants classes Improved Force EntityManagerFactory initialization during boot sequence Improved Add new Result methods to handle empty content easily Improved Validation constraints can be grouped Improved Clean code Improved Better boolean support (Freemarker / config) Improved Refactoring module "Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.2.0 2022-xx-xx
+Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053) New Add SecurityHeadersFilter New Add unit test JUnit extension and annotation New Add ability to fetch remote configuration provider & "etcd" remote configuration provider New Add "http" remote configuration provider New Add CharConstants & StringConstants classes Improved Force EntityManagerFactory initialization during boot sequence Improved Add new Result methods to handle empty content easily Improved Validation constraints can be grouped Improved Clean code Improved Better boolean support (Freemarker / config) Improved Refactoring module "Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
+Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
@@ -50,10 +50,10 @@ voidframework.web.securityHeaders.contentTypeOptions the value for the header &a
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Upgrading from old versionhttps://voidframework.dev/doc/getting-started/upgrading-from-old-version/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/upgrading-from-old-version/Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.
-1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now required 1.2.0 The CSRF filter has been moved to the dev.voidframework.web.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
+1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now required 1.2.0 The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.1.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index d0e7d53..0e17786 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,10 +1,9 @@
 Void Framework – Release notes
+Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053) New Add SecurityHeadersFilter New Add unit test JUnit extension and annotation New Add ability to fetch remote configuration provider & "etcd" remote configuration provider ">Void Framework – Release notes
 Void Framework
Documentation
    
 Release notes1.2.0

-2022-xx-xx
New Add SecurityHeadersFilter
Improved Force EntityManagerFactory initialization during boot sequence
Improved Add new Result methods to handle empty content easily
Improved Updated version of all dependencies

1.1.2

+2022-xx-xx
Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053)
New Add SecurityHeadersFilter
New Add unit test JUnit extension and annotation
New Add ability to fetch remote configuration provider & "etcd" remote configuration provider
New Add "http" remote configuration provider
New Add CharConstants & StringConstants classes
Improved Force EntityManagerFactory initialization during boot sequence
Improved Add new Result methods to handle empty content easily
Improved Validation constraints can be grouped
Improved Clean code
Improved Better boolean support (Freemarker / config)
Improved Refactoring module "web" (move files, new constant values, unit tests)
Improved Updated version of all dependencies

1.1.2

 2022-08-02
Fixed EntityManagerFactory don't find models on multiple-jars project

1.1.1

 2022-07-24
Improved Change CSRF signature algorithm to HMACSHA256
Fixed Error 500 CSRF when POST request render template

1.1.0

 2022-07-22
New Methods on Reflection util class: getAnnotatedField(Object, Class) and getAnnotatedField(Class, Class)
New Configuration keys to define number of I/O and Worker threads (Web)
New Redis (base + cache + healthcheck)
New CSRF token
Improved No longer necessary for HealthChecker to be Singleton
Improved Add cache abstraction helper
Improved Session signature key configuration is now required
Improved Rename ApplicationLauncher to VoidApplication
Improved Updated version of all dependencies
Fixed Cookie revocation not working
Fixed C3P0/HikariCP settings
Fixed Issue on routes sorting when regex and capture regex are used
Fixed Assets not found when devMode=false
Fixed Hibernate : Models not found when application is compiled

1.0.1

diff --git a/sitemap.xml b/sitemap.xml
index b2da983..e55b653 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/template/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file

From ec95f79e506695a95e028ec4103b16b91e4b2990 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Mon, 5 Sep 2022 19:31:25 +0000
Subject: [PATCH 20/75] Automated website build

---
 index.xml               | 4 ++--
 releasenotes/index.html | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/index.xml b/index.xml
index 90f3f92..ea6e944 100644
--- a/index.xml
+++ b/index.xml
@@ -33,8 +33,8 @@ The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
-priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.2.0 2022-xx-xx
-Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053) New Add SecurityHeadersFilter New Add unit test JUnit extension and annotation New Add ability to fetch remote configuration provider & "etcd" remote configuration provider New Add "http" remote configuration provider New Add CharConstants & StringConstants classes Improved Force EntityManagerFactory initialization during boot sequence Improved Add new Result methods to handle empty content easily Improved Validation constraints can be grouped Improved Clean code Improved Better boolean support (Freemarker / config) Improved Refactoring module "Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.2.0 2022-xx-xx
+priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.2.0 2022-09-05
+Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053) New Add SecurityHeadersFilter New Add unit test JUnit extension and annotation New Add ability to fetch remote configuration provider & "etcd" remote configuration provider New Add "http" remote configuration provider New Add CharConstants & StringConstants classes Improved Force EntityManagerFactory initialization during boot sequence Improved Add new Result methods to handle empty content easily Improved Validation constraints can be grouped Improved Clean code Improved Better boolean support (Freemarker / config) Improved Refactoring module "Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.2.0 2022-09-05
 Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053) New Add SecurityHeadersFilter New Add unit test JUnit extension and annotation New Add ability to fetch remote configuration provider & "etcd" remote configuration provider New Add "http" remote configuration provider New Add CharConstants & StringConstants classes Improved Force EntityManagerFactory initialization during boot sequence Improved Add new Result methods to handle empty content easily Improved Validation constraints can be grouped Improved Clean code Improved Better boolean support (Freemarker / config) Improved Refactoring module "Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 0e17786..cc58364 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,9 +1,9 @@
-Void Framework – Release notes
 Void Framework
Documentation
    
 Release notes
1.2.0

-2022-xx-xx
Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053)
New Add SecurityHeadersFilter
New Add unit test JUnit extension and annotation
New Add ability to fetch remote configuration provider & "etcd" remote configuration provider
New Add "http" remote configuration provider
New Add CharConstants & StringConstants classes
Improved Force EntityManagerFactory initialization during boot sequence
Improved Add new Result methods to handle empty content easily
Improved Validation constraints can be grouped
Improved Clean code
Improved Better boolean support (Freemarker / config)
Improved Refactoring module "web" (move files, new constant values, unit tests)
Improved Updated version of all dependencies

1.1.2

+2022-09-05
Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053)
New Add SecurityHeadersFilter
New Add unit test JUnit extension and annotation
New Add ability to fetch remote configuration provider & "etcd" remote configuration provider
New Add "http" remote configuration provider
New Add CharConstants & StringConstants classes
Improved Force EntityManagerFactory initialization during boot sequence
Improved Add new Result methods to handle empty content easily
Improved Validation constraints can be grouped
Improved Clean code
Improved Better boolean support (Freemarker / config)
Improved Refactoring module "web" (move files, new constant values, unit tests)
Improved Updated version of all dependencies

1.1.2

 2022-08-02
Fixed EntityManagerFactory don't find models on multiple-jars project

1.1.1

 2022-07-24
Improved Change CSRF signature algorithm to HMACSHA256
Fixed Error 500 CSRF when POST request render template

1.1.0

 2022-07-22
New Methods on Reflection util class: getAnnotatedField(Object, Class) and getAnnotatedField(Class, Class)
New Configuration keys to define number of I/O and Worker threads (Web)
New Redis (base + cache + healthcheck)
New CSRF token
Improved No longer necessary for HealthChecker to be Singleton
Improved Add cache abstraction helper
Improved Session signature key configuration is now required
Improved Rename ApplicationLauncher to VoidApplication
Improved Updated version of all dependencies
Fixed Cookie revocation not working
Fixed C3P0/HikariCP settings
Fixed Issue on routes sorting when regex and capture regex are used
Fixed Assets not found when devMode=false
Fixed Hibernate : Models not found when application is compiled

1.0.1


From a3b664aefaae71587e6ac0a4014ad070b708a794 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Mon, 12 Sep 2022 19:28:18 +0000
Subject: [PATCH 21/75] Automated website build

---
 doc/web/controller/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index 633312e..df388a8 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -17,7 +17,7 @@
         return Result.ok("Hello World");
     }
 }
-

Defining a route
A route is defined by two components, firstly @WebController defines the prefix that will be applied to all methods of the controller and by the @RequestRoute annotation providing various options. The latter tells the Void Framework that the method is an entry point.
@WebController
This annotation is based on the @Controller annotation. It simply allows the class to be better specified and provides additional options. This annotation can only be used at class level.
The annotation accepts the following parameter:
prefixRoute defines a prefix to be used on all endpoints in the class. By default, the value is empty.
@RequestRoute
This annotation allows you to configure an entry point that will process an incoming request. This annotation can only be used at method level.
The annotation accepts the following parameters:
method defines the HTTP method. The default value is HttpMethod.GET.
route defines a route. Regular expression with named capturing group can be used. The default value is /.
name defines an alias name who can be used with the reverse routing. By default, the value is empty.

Retrieving parameters
To work, a controller will probably need some incoming data. To do this, the @RequestPath, @RequestVariable and @RequestBody annotations make it easy to retrieve information from the request. It is also possible to retrieve information from the Context itself.
@RequestPath
This annotation allows you to extract parameters named in the URL path.
The annotation accepts the following parameter:
value defines the name of the parameter (correlated with the regexp used in the route definition) to extract.
@RequestVariable
This annotation allows you to extract query string value from the URI.
The annotation accepts the following parameter:
value defines the name of the query string value to extract.
@RequestBody
This annotation allows you to retrieve the contents of the request (i.e. from a POST query) as a Java object. If something goes wrong, the extracted value will be null.

© 2022 Void Framework

+

Defining a route
A route is defined by two components, firstly @WebController defines the prefix that will be applied to all methods of the controller and by the @RequestRoute annotation providing various options. The latter tells the Void Framework that the method is an entry point.
@WebController
This annotation is based on the @Controller annotation. It simply allows the class to be better specified and provides additional options. This annotation can only be used at class level.
The annotation accepts the following parameter:
prefixRoute defines a prefix to be used on all endpoints in the class. By default, the value is empty.
@RequestRoute
This annotation allows you to configure an entry point that will process an incoming request. This annotation can only be used at method level.
The annotation accepts the following parameters:
method defines the HTTP method. The default value is HttpMethod.GET.
route defines a route. Regular expression with named capturing group can be used. The default value is /.
name defines an alias name who can be used with the reverse routing. By default, the value is empty.

Retrieving parameters
To work, a controller will probably need some incoming data. To do this, the @RequestPath, @RequestVariable and @RequestBody annotations make it easy to retrieve information from the request. It is also possible to retrieve information from the Context itself.
@RequestPath
This annotation allows you to extract parameters named in the URL path.
The annotation accepts the following parameter:
value defines the name of the parameter (correlated with the regexp used in the route definition) to extract.
@RequestVariable
This annotation allows you to extract query string value from the URI.
The annotation accepts the following parameter:
value defines the name of the query string value to extract.
@RequestBody
This annotation allows you to retrieve the contents of the request (i.e. from a POST query) as a Java object. If something goes wrong, the extracted value will be null.

Parameter types
It is sure that you will have to retrieve the parameters with their respective type (e.g. int, boolean, …). For this, Void Framework uses the converter mechanism to allow conversion from a String. By default, the following types are handled:
Boolean
Byte
Character
Double
Float
Integer
Locale
Long
Short
String
UUID

Handle custom types
To handle a new type, you simply have to implement a new converter. For more information, read the Type conversion chapter.

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 

From e3b63a23945097e5d83c8a91fc2c9b7bda1b3d60 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 15 Sep 2022 17:46:58 +0000
Subject: [PATCH 22/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/redis-cache/index.html              |  2 +-
 doc/core/configuration/index.html             |  4 ++--
 doc/databases/datasource/index.html           |  4 ++--
 .../persistence-hibernate/index.html          |  2 +-
 .../new-application/index.html                |  4 ++--
 doc/index.xml                                 | 16 ++++++-------
 .../using-i18n/index.html                     |  2 +-
 doc/template/freemarker/index.html            |  2 +-
 index.xml                                     | 24 ++++++++++---------
 releasenotes/index.html                       |  7 +++---
 11 files changed, 36 insertions(+), 33 deletions(-)

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 86d2dca..dbd381c 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.2.0</version>
+    <version>1.2.1</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 134e274..1595968 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.2.0</version>
+    <version>1.2.1</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index afce41a..e9d50ce 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -6,7 +6,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.2.0</version>
+  <version>1.2.1</version>
 </dependency>
 
voidframework {
     code {
@@ -41,7 +41,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.2.0</version>
+  <version>1.2.1</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/databases/datasource/index.html b/doc/databases/datasource/index.html
index b59a2e4..4fe0144 100644
--- a/doc/databases/datasource/index.html
+++ b/doc/databases/datasource/index.html
@@ -5,12 +5,12 @@
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.2.0</version>
+    <version>1.2.1</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.2.0</version>
+    <version>1.2.1</version>
 </dependency>
 
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/databases/persistence-hibernate/index.html b/doc/databases/persistence-hibernate/index.html
index c80bc3a..c79a469 100644
--- a/doc/databases/persistence-hibernate/index.html
+++ b/doc/databases/persistence-hibernate/index.html
@@ -6,7 +6,7 @@
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.2.0</version>
+    <version>1.2.1</version>
 </dependency>
 

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
 Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

Exemple
@Entity
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 2b43c3e..9863ec3 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.2.0</version>
+    <version>1.2.1</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.2.0</version>
+    <version>1.2.1</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/index.xml b/doc/index.xml
index 43e878e..6b44c28 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -5,12 +5,12 @@ Configuration Void Framework offers different implementations, depending on the
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
@@ -24,9 +24,9 @@ Maven The very first dependency to include in your pom.xml is voidframework-core
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
 Method Description config Retrieves a value from the configuration displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, &hellip;) i18n / _ Translates a message urlfor Retrieves an URL from the router (reverse router) Variable Description isDevMode Indicates whether the application is in dev mode lang Contains the current language languages Contains all available languages voidFrameworkVersion Contains the current Void Framework version &nbsp; FreeMarker provides a lot of other built-in methods & variables.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
 Method Description config Retrieves a value from the configuration displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, &hellip;) i18n / _ Translates a message urlfor Retrieves an URL from the router (reverse router) Variable Description isDevMode Indicates whether the application is in dev mode lang Contains the current language languages Contains all available languages voidFrameworkVersion Contains the current Void Framework version &nbsp; FreeMarker provides a lot of other built-in methods & variables.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
@@ -52,6 +52,6 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 7cbe5b9..4eeb914 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.2.0</version>
+    <version>1.2.1</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index a390874..e8ee769 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.2.0</version>
+    <version>1.2.1</version>
 </dependency>
 

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/index.xml b/index.xml
index ea6e944..0034f67 100644
--- a/index.xml
+++ b/index.xml
@@ -5,12 +5,12 @@ Configuration Void Framework offers different implementations, depending on the
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
@@ -24,18 +24,20 @@ Maven The very first dependency to include in your pom.xml is voidframework-core
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
 Method Description config Retrieves a value from the configuration displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, &hellip;) i18n / _ Translates a message urlfor Retrieves an URL from the router (reverse router) Variable Description isDevMode Indicates whether the application is in dev mode lang Contains the current language languages Contains all available languages voidFrameworkVersion Contains the current Void Framework version &nbsp; FreeMarker provides a lot of other built-in methods & variables.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
 Method Description config Retrieves a value from the configuration displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, &hellip;) i18n / _ Translates a message urlfor Retrieves an URL from the router (reverse router) Variable Description isDevMode Indicates whether the application is in dev mode lang Contains the current language languages Contains all available languages voidFrameworkVersion Contains the current Void Framework version &nbsp; FreeMarker provides a lot of other built-in methods & variables.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
-priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.2.0 2022-09-05
-Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053) New Add SecurityHeadersFilter New Add unit test JUnit extension and annotation New Add ability to fetch remote configuration provider & "etcd" remote configuration provider New Add "http" remote configuration provider New Add CharConstants & StringConstants classes Improved Force EntityManagerFactory initialization during boot sequence Improved Add new Result methods to handle empty content easily Improved Validation constraints can be grouped Improved Clean code Improved Better boolean support (Freemarker / config) Improved Refactoring module "Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.2.0 2022-09-05
-Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053) New Add SecurityHeadersFilter New Add unit test JUnit extension and annotation New Add ability to fetch remote configuration provider & "etcd" remote configuration provider New Add "http" remote configuration provider New Add CharConstants & StringConstants classes Improved Force EntityManagerFactory initialization during boot sequence Improved Add new Result methods to handle empty content easily Improved Validation constraints can be grouped Improved Clean code Improved Better boolean support (Freemarker / config) Improved Refactoring module "Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.2.1 2022-09-15
+Fix The "Modules loaded" log is displayed too early Fix Remove unused "GlobalFilterDefinition" interface Improved Add converter String to Locale (Web). Used to extract Locale from incoming request (route path or query parameter) 1.2.0 2022-09-05
+Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053) New Add SecurityHeadersFilter New Add unit test JUnit extension and annotation New Add ability to fetch remote configuration provider & "etcd" remote configuration provider New Add "Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.2.1 2022-09-15
+Fix The "Modules loaded" log is displayed too early Fix Remove unused "GlobalFilterDefinition" interface Improved Add converter String to Locale (Web). Used to extract Locale from incoming request (route path or query parameter) 1.2.0 2022-09-05
+Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053) New Add SecurityHeadersFilter New Add unit test JUnit extension and annotation New Add ability to fetch remote configuration provider & "etcd" remote configuration provider New Add "Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
@@ -54,6 +56,6 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index cc58364..d962ad8 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,8 +1,9 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.2.0

+Release notes
1.2.1

+2022-09-15
Fix The "Modules loaded" log is displayed too early
Fix Remove unused "GlobalFilterDefinition" interface
Improved Add converter String to Locale (Web). Used to extract Locale from incoming request (route path or query parameter)
1.2.0

 2022-09-05
Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053)
New Add SecurityHeadersFilter
New Add unit test JUnit extension and annotation
New Add ability to fetch remote configuration provider & "etcd" remote configuration provider
New Add "http" remote configuration provider
New Add CharConstants & StringConstants classes
Improved Force EntityManagerFactory initialization during boot sequence
Improved Add new Result methods to handle empty content easily
Improved Validation constraints can be grouped
Improved Clean code
Improved Better boolean support (Freemarker / config)
Improved Refactoring module "web" (move files, new constant values, unit tests)
Improved Updated version of all dependencies

1.1.2

 2022-08-02
Fixed EntityManagerFactory don't find models on multiple-jars project

1.1.1

 2022-07-24
Improved Change CSRF signature algorithm to HMACSHA256
Fixed Error 500 CSRF when POST request render template

1.1.0


From d95706888de050afa5a8d6fc5d562927f246b901 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 15 Sep 2022 20:05:57 +0000
Subject: [PATCH 23/75] Automated website build

---
 releasenotes/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/releasenotes/index.html b/releasenotes/index.html
index d962ad8..a2e93cb 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -3,7 +3,7 @@
 Void Framework
Documentation
    
 Release notes
1.2.1

-2022-09-15
Fix The "Modules loaded" log is displayed too early
Fix Remove unused "GlobalFilterDefinition" interface
Improved Add converter String to Locale (Web). Used to extract Locale from incoming request (route path or query parameter)
1.2.0

+2022-09-15
Fix The "Modules loaded" log is displayed too early
Fix Remove unused "GlobalFilterDefinition" interface
Improved Add converter String to Locale (Web). Used to extract Locale from incoming request (route path or query parameter)

1.2.0

 2022-09-05
Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053)
New Add SecurityHeadersFilter
New Add unit test JUnit extension and annotation
New Add ability to fetch remote configuration provider & "etcd" remote configuration provider
New Add "http" remote configuration provider
New Add CharConstants & StringConstants classes
Improved Force EntityManagerFactory initialization during boot sequence
Improved Add new Result methods to handle empty content easily
Improved Validation constraints can be grouped
Improved Clean code
Improved Better boolean support (Freemarker / config)
Improved Refactoring module "web" (move files, new constant values, unit tests)
Improved Updated version of all dependencies

1.1.2

 2022-08-02
Fixed EntityManagerFactory don't find models on multiple-jars project

1.1.1

 2022-07-24
Improved Change CSRF signature algorithm to HMACSHA256
Fixed Error 500 CSRF when POST request render template

1.1.0


From f5afc418c2de5dc1dcea9e9be105e1c169093d69 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Sun, 2 Oct 2022 08:02:04 +0000
Subject: [PATCH 24/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/index.html                          |  2 +-
 doc/cache/redis-cache/index.html              |  2 +-
 doc/cache/using-cache/index.html              |  2 +-
 doc/core/boot-sequence/index.html             |  2 +-
 doc/core/class-scanning/index.html            |  2 +-
 doc/core/configuration/index.html             |  2 +-
 doc/core/index.html                           |  2 +-
 doc/core/life-cycle/index.html                |  2 +-
 doc/core/type-conversion/index.html           |  2 +-
 doc/databases/datasource/index.html           |  2 +-
 doc/databases/index.html                      |  2 +-
 .../persistence-hibernate/index.html          |  2 +-
 doc/getting-started/index.html                |  2 +-
 .../new-application/index.html                |  2 +-
 doc/getting-started/requirements/index.html   |  2 +-
 .../upgrading-from-old-version/index.html     |  2 +-
 doc/i18n/index.html                           |  2 +-
 doc/index.html                                |  2 +-
 doc/index.xml                                 |  6 ++--
 .../using-i18n/index.html                     |  2 +-
 doc/scheduler/index.html                      |  8 ++++++
 doc/scheduler/scheduling-job-cron/index.html  | 28 +++++++++++++++++++
 doc/template/freemarker/index.html            |  2 +-
 doc/template/index.html                       |  2 +-
 doc/web/controller/index.html                 |  2 +-
 doc/web/filters/index.html                    |  2 +-
 doc/web/index.html                            |  2 +-
 doc/web/render-template/index.html            |  2 +-
 doc/web/security-csrf/index.html              |  2 +-
 doc/web/security-headers/index.html           |  2 +-
 doc/web/session/index.html                    |  2 +-
 index.xml                                     |  6 ++--
 sitemap.xml                                   |  2 +-
 34 files changed, 74 insertions(+), 34 deletions(-)
 create mode 100644 doc/scheduler/index.html
 create mode 100644 doc/scheduler/scheduling-job-cron/index.html

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index dbd381c..7ad4e33 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,7 +2,7 @@
 Insta">Void Framework – Cache engine : In-memory

 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
     <version>1.2.1</version>
diff --git a/doc/cache/index.html b/doc/cache/index.html
index b088ecb..21ba640 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Cache

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Cache

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 1595968..1e06ae3 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
     <version>1.2.1</version>
diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index 7b704b4..0fcd639 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,7 +2,7 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
 Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index 31160c9..9ef24d1 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c . t u r c a h i l l P . c c e r b e o c o o n o v o m v">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index ebdde37..e8a9a05 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,7 +2,7 @@
 Bindable classes (see below) classes implementing the TypeConverter interface classes which e">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
 3 types of elements are recognised during the scan:
Bindable classes (see below)
classes implementing the TypeConverter interface
classes which extend AbstractModule (Guice)

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@BindClass Indicates that an annotated class is a “Bindable”
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index e9d50ce..4bb4369 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -1,7 +1,7 @@
 Void Framework – Configuration
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
 

Remote configuration
Once packaged, you will probably need to modulate the configuration of the application depending on the environment (ie: development, integration, production). The typical example is the configuration of the data source, you cannot define this information directly in the configuration file included in the Jars files. Void Framework allows you to load configurations that will be stored elsewhere, such as on etcd or vault.
To enable remote configuration loading, you must declare one or more providers to be used via the configuration key voidframework.core.remoteConfiguration.providers.
 
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
diff --git a/doc/core/index.html b/doc/core/index.html
index cb9432f..1a11725 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Core

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Core

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index 3fbbef8..ffe6b06 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index 9760151..ef40dd9 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/databases/datasource/index.html b/doc/databases/datasource/index.html
index 4fe0144..0025188 100644
--- a/doc/databases/datasource/index.html
+++ b/doc/databases/datasource/index.html
@@ -1,7 +1,7 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
diff --git a/doc/databases/index.html b/doc/databases/index.html
index 57a539b..5e6ba0a 100644
--- a/doc/databases/index.html
+++ b/doc/databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/databases/persistence-hibernate/index.html b/doc/databases/persistence-hibernate/index.html
index c79a469..6d983ce 100644
--- a/doc/databases/persistence-hibernate/index.html
+++ b/doc/databases/persistence-hibernate/index.html
@@ -2,7 +2,7 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index 45d6bd1..4afab95 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Getting Started

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Getting Started

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 9863ec3..7c1abae 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,7 +2,7 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
     <version>1.2.1</version>
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index eea2c8b..c184df1 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index 2868631..9223d81 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.1.0 ApplicationLa">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index b539f4b..5ff3ae7 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Internationalization

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Internationalization

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index bb3a8f5..3398cde 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Documentation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Documentation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 6b44c28..0170f5b 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -2,7 +2,7 @@
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Data sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
@@ -41,7 +41,9 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
-openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
+openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
+Define a Job To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
+Define a Job To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 4eeb914..9f43650 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
     <version>1.2.1</version>
diff --git a/doc/scheduler/index.html b/doc/scheduler/index.html
new file mode 100644
index 0000000..d5e5b1b
--- /dev/null
+++ b/doc/scheduler/index.html
@@ -0,0 +1,8 @@
+Void Framework – Scheduler
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Scheduler

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
new file mode 100644
index 0000000..3242cae
--- /dev/null
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -0,0 +1,28 @@
+Void Framework – Scheduling a local job
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay defines the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate defines the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay defines the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron defines a CRON-like expression. The default value is empty (disabled).
cronZone defines the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEV
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
+public final class Ping {
+
+    private static final Logger LOGGER = LoggerFactory.getLogger(Ping.class);
+
+    @Scheduled(fixedDelay = 5000, initialDelay = 10000)
+    public void doPingEveryFiveSecondsAfter10Seconds() {
+        LOGGER.info("PING!!");
+    }
+
+    @Scheduled(cron = "0 */5 * * * *")
+    public void doPingEveryFiveMinutesUTC() {
+        LOGGER.info("PING!!");
+    }
+
+    @Scheduled(cron = "0 0 0 * * mon", cronZone = "Europe/Paris")
+    public void doPingEveryMondayAtMidnightEuropeParis() {
+        LOGGER.info("PING!!");
+    }
+}
+

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index e8ee769..1fb5f4b 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifact">Void Framework – FreeMarker
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
     <version>1.2.1</version>
diff --git a/doc/template/index.html b/doc/template/index.html
index 6be0766..17282bd 100644
--- a/doc/template/index.html
+++ b/doc/template/index.html
@@ -1,7 +1,7 @@
 Void Framework – Template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Template

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Template

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index df388a8..29a7f2b 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index d792976..0080a2e 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the">Void Framework – Filters
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
 Note that the use of dependencies direct injection is possible in filters.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
 @Singleton
 @WebController
diff --git a/doc/web/index.html b/doc/web/index.html
index 87e1369..39b1e45 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Web

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Web

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/render-template/index.html b/doc/web/render-template/index.html
index d7a21d3..c0117e7 100644
--- a/doc/web/render-template/index.html
+++ b/doc/web/render-template/index.html
@@ -2,7 +2,7 @@
 Although you can manually use the template engine, in most cases this would not be handy. Howev">Void Framework – Render template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Example
controller/HomeController.java
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Example
controller/HomeController.java
@Singleton
 @WebController
 public class HomeController {
 
diff --git a/doc/web/security-csrf/index.html b/doc/web/security-csrf/index.html
index b9de58d..06d8e9b 100644
--- a/doc/web/security-csrf/index.html
+++ b/doc/web/security-csrf/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is recommended tha">Void Framework – CSRF
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
 It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP.
Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/security-headers/index.html b/doc/web/security-headers/index.html
index 09dac59..a68aafb 100644
--- a/doc/web/security-headers/index.html
+++ b/doc/web/security-headers/index.html
@@ -2,7 +2,7 @@
 Configuration The following configuration keys can be used in the configuration">Void Framework – Security headers
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
 You can disable one of the headers by assigning the value null. The header will then not be sent.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/session/index.html b/doc/web/session/index.html
index 7d9152c..7a7eca7 100644
--- a/doc/web/session/index.html
+++ b/doc/web/session/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the session is not stored on the server side, but on the client side v">Void Framework – Session
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
 Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie.

Because session is implemented using cookies, there are some implications.The data size is limited to 4 KiB
Only string can be stored

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.

Read value
You can access the session data via the Context. Methods get or getOrDefault can be used.
@Singleton
 @WebController
 public class Controller {
diff --git a/index.xml b/index.xml
index 0034f67..dbed992 100644
--- a/index.xml
+++ b/index.xml
@@ -2,7 +2,7 @@
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Data sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
@@ -45,7 +45,9 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
-openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
+openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
+Define a Job To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
+Define a Job To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
diff --git a/sitemap.xml b/sitemap.xml
index e55b653..071f0ed 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/template/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/template/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file

From 8f7f3ec683395a5636a3e08ef6dec7097775db81 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Sun, 2 Oct 2022 08:06:03 +0000
Subject: [PATCH 25/75] Automated website build

---
 doc/scheduler/scheduling-job-cron/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index 3242cae..af3f82b 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduling a local job
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay defines the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate defines the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay defines the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron defines a CRON-like expression. The default value is empty (disabled).
cronZone defines the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEV
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay defines the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate defines the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay defines the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron defines a CRON-like expression. The default value is empty (disabled).
cronZone defines the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
 public final class Ping {
 
     private static final Logger LOGGER = LoggerFactory.getLogger(Ping.class);

From 0bf606d74cb199d2c1fdd0bdb7d69b8c958e3d2e Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Mon, 7 Nov 2022 18:53:50 +0000
Subject: [PATCH 26/75] Automated website build

---
 doc/advanced/advanced/index.html              |  8 +++
 doc/advanced/index.html                       |  8 +++
 doc/cache/in-memory-cache/index.html          |  4 +-
 doc/cache/index.html                          |  2 +-
 doc/cache/redis-cache/index.html              |  8 +--
 doc/cache/using-cache/index.html              |  2 +-
 doc/core/boot-sequence/index.html             |  2 +-
 doc/core/class-scanning/index.html            |  2 +-
 doc/core/configuration/index.html             | 25 +++++++-
 doc/core/index.html                           |  2 +-
 doc/core/life-cycle/index.html                |  2 +-
 doc/core/type-conversion/index.html           |  4 +-
 doc/databases/index.html                      |  8 ---
 doc/getting-started/index.html                |  2 +-
 .../new-application/index.html                |  6 +-
 doc/getting-started/requirements/index.html   |  2 +-
 .../upgrading-from-old-version/index.html     |  2 +-
 doc/i18n/index.html                           |  2 +-
 doc/index.html                                |  2 +-
 doc/index.xml                                 | 54 +++++++++++------
 .../using-i18n/index.html                     |  4 +-
 doc/nosql-databases/index.html                |  8 +++
 doc/nosql-databases/redis/index.html          | 33 ++++++++++
 .../datasource/index.html                     | 10 ++--
 doc/relational-databases/index.html           |  8 +++
 .../persistence-hibernate/index.html          | 15 +++--
 doc/scheduler/index.html                      |  2 +-
 doc/scheduler/scheduling-job-cron/index.html  |  2 +-
 doc/template/freemarker/index.html            |  8 +--
 doc/template/index.html                       |  2 +-
 doc/testing/index.html                        |  8 +++
 doc/testing/junit-extension/index.html        | 37 ++++++++++++
 doc/vfs/index.html                            |  8 +++
 doc/vfs/introduction/index.html               | 60 +++++++++++++++++++
 doc/web/controller/index.html                 | 18 +++++-
 doc/web/filters/index.html                    |  2 +-
 doc/web/index.html                            |  2 +-
 doc/web/render-template/index.html            |  2 +-
 doc/web/security-csrf/index.html              |  2 +-
 doc/web/security-headers/index.html           |  2 +-
 doc/web/session/index.html                    |  2 +-
 index.html                                    |  2 +-
 index.xml                                     | 60 ++++++++++++-------
 releasenotes/index.html                       | 17 +++---
 sitemap.xml                                   |  2 +-
 45 files changed, 355 insertions(+), 108 deletions(-)
 create mode 100644 doc/advanced/advanced/index.html
 create mode 100644 doc/advanced/index.html
 delete mode 100644 doc/databases/index.html
 create mode 100644 doc/nosql-databases/index.html
 create mode 100644 doc/nosql-databases/redis/index.html
 rename doc/{databases => relational-databases}/datasource/index.html (60%)
 create mode 100644 doc/relational-databases/index.html
 rename doc/{databases => relational-databases}/persistence-hibernate/index.html (65%)
 create mode 100644 doc/testing/index.html
 create mode 100644 doc/testing/junit-extension/index.html
 create mode 100644 doc/vfs/index.html
 create mode 100644 doc/vfs/introduction/index.html

diff --git a/doc/advanced/advanced/index.html b/doc/advanced/advanced/index.html
new file mode 100644
index 0000000..45c73a9
--- /dev/null
+++ b/doc/advanced/advanced/index.html
@@ -0,0 +1,8 @@
+Void Framework – reference.conf
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/advanced/index.html b/doc/advanced/index.html
new file mode 100644
index 0000000..0083980
--- /dev/null
+++ b/doc/advanced/index.html
@@ -0,0 +1,8 @@
+Void Framework – Advanced
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Advanced

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 7ad4e33..6fbfb08 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,10 +2,10 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.2.1</version>
+    <version>1.3.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/index.html b/doc/cache/index.html
index 21ba640..c1b1802 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Cache

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 1e06ae3..c0fde8f 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -1,13 +1,13 @@
 Void Framework – Cache engine : Redis
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.2.1</version>
+    <version>1.3.0</version>
 </dependency>
-
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.

© 2022 Void Framework

+
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index 0fcd639..3a1c7d0 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,7 +2,7 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
 Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index 9ef24d1..23e215d 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c . t u r c a h i l l P . c c e r b e o c o o n o v o m v">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index e8a9a05..7d32d64 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,7 +2,7 @@
 Bindable classes (see below) classes implementing the TypeConverter interface classes which e">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
 3 types of elements are recognised during the scan:
Bindable classes (see below)
classes implementing the TypeConverter interface
classes which extend AbstractModule (Guice)

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@BindClass Indicates that an annotated class is a “Bindable”
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index 4bb4369..ec0477f 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -1,12 +1,31 @@
 Void Framework – Configuration
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+

Retrieve configuration value from Java
@Service
+public class MyService {
+
+    private final Config configuration;
+
+    @Inject
+    public MyService(final Config configuration) {
+        this.configuration = configuration;
+    }
+
+    public void test() {
+        final boolean runInDevMode = configuration.getBoolean("voidframework.core.runInDevMode");
+        if (runInDevMode) {
+            // Do something
+        } else {
+            // Do something else
+        }
+    }
+}
 

Remote configuration
Once packaged, you will probably need to modulate the configuration of the application depending on the environment (ie: development, integration, production). The typical example is the configuration of the data source, you cannot define this information directly in the configuration file included in the Jars files. Void Framework allows you to load configurations that will be stored elsewhere, such as on etcd or vault.
To enable remote configuration loading, you must declare one or more providers to be used via the configuration key voidframework.core.remoteConfiguration.providers.
 
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.2.1</version>
+  <version>1.3.0</version>
 </dependency>
 
voidframework {
     code {
@@ -41,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.2.1</version>
+  <version>1.3.0</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/core/index.html b/doc/core/index.html
index 1a11725..106f178 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Core

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Core

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index ffe6b06..5555f4f 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index ef40dd9..f01c7d7 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,12 +1,12 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
     @Inject
-    public DummyService(final Conversion conversion) {
+    public ExampleConversionService(final Conversion conversion) {
         this.conversion = conversion;
     }
 
diff --git a/doc/databases/index.html b/doc/databases/index.html
deleted file mode 100644
index 5e6ba0a..0000000
--- a/doc/databases/index.html
+++ /dev/null
@@ -1,8 +0,0 @@
-Void Framework – Databases
-Void Framework
Documentation
-   
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Databases

© 2022 Void Framework

-Void Framework is released under the MIT License

-
-
-
\ No newline at end of file
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index 4afab95..c03bec0 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Getting Started

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Getting Started

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 7c1abae..cb4777b 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,15 +2,15 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.2.1</version>
+    <version>1.3.0</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.2.1</version>
+    <version>1.3.0</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index c184df1..2796e83 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index 9223d81..1d743f9 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.1.0 ApplicationLa">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index 5ff3ae7..39bd405 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Internationalization

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Internationalization

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index 3398cde..4627ecc 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Documentation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Documentation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 0170f5b..455d91e 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,16 +1,14 @@
-Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioData sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
-Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Data sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
-Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
@@ -19,21 +17,39 @@ Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.CSRFhttps://voidframework.dev/doc/web/security-csrf/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-csrf/Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
-&nbsp; It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP. Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
+&nbsp; It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP. Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.Data sourcehttps://voidframework.dev/doc/relational-databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
+Installation Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Data sourcehttps://voidframework.dev/doc/relational-databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
+Installation Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
-Method Description config Retrieves a value from the configuration displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, &hellip;) i18n / _ Translates a message urlfor Retrieves an URL from the router (reverse router) Variable Description isDevMode Indicates whether the application is in dev mode lang Contains the current language languages Contains all available languages voidFrameworkVersion Contains the current Void Framework version &nbsp; FreeMarker provides a lot of other built-in methods & variables.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
-Method Description config Retrieves a value from the configuration displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, &hellip;) i18n / _ Translates a message urlfor Retrieves an URL from the router (reverse router) Variable Description isDevMode Indicates whether the application is in dev mode lang Contains the current language languages Contains all available languages voidFrameworkVersion Contains the current Void Framework version &nbsp; FreeMarker provides a lot of other built-in methods & variables.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Configuration The following configuration keys can be used in the configuration file of your application:
+voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Configuration The following configuration keys can be used in the configuration file of your application:
+voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
-priority is used to define when the method will be called in relation to the others.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
@@ -54,6 +70,10 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 9f43650..fd76582 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,10 +1,10 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.2.1</version>
+    <version>1.3.0</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/index.html b/doc/nosql-databases/index.html
new file mode 100644
index 0000000..6f364d4
--- /dev/null
+++ b/doc/nosql-databases/index.html
@@ -0,0 +1,8 @@
+Void Framework – NoSQL Databases
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

NoSQL Databases

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
new file mode 100644
index 0000000..504e413
--- /dev/null
+++ b/doc/nosql-databases/redis/index.html
@@ -0,0 +1,33 @@
+Void Framework – Redis
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+    <groupId>dev.voidframework</groupId>
+    <artifactId>voidframework-redis</artifactId>
+    <version>1.3.0</version>
+</dependency>
+

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
+    <groupId>dev.voidframework</groupId>
+    <artifactId>voidframework-redis-healthcheck</artifactId>
+    <version>1.3.0</version>
+</dependency>
+

Example
@Service
+public final class ExampleService {
+
+    private final Redis redis;
+
+    @Inject
+    public ExampleService(final Redis redis) {
+        this.redis = redis;
+    }
+
+    public void example() {
+        final long nextValue = this.redis.increment("incr.key");
+    }
+}
+

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/databases/datasource/index.html b/doc/relational-databases/datasource/index.html
similarity index 60%
rename from doc/databases/datasource/index.html
rename to doc/relational-databases/datasource/index.html
index 0025188..499a6bc 100644
--- a/doc/databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -1,18 +1,18 @@
-Void Framework – Data source
+Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Configuration
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.2.1</version>
+    <version>1.3.0</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.2.1</version>
+    <version>1.3.0</version>
 </dependency>
-
The following configuration keys can be used in the configuration file of your application:required
+

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
 voidframework.datasource.default.url the JDBC format URL to be used to reach the database.
required
 voidframework.datasource.default.username the username to be provided durint the authentication step.
required
diff --git a/doc/relational-databases/index.html b/doc/relational-databases/index.html
new file mode 100644
index 0000000..bb10d00
--- /dev/null
+++ b/doc/relational-databases/index.html
@@ -0,0 +1,8 @@
+Void Framework – Relational Databases
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Relational Databases

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
similarity index 65%
rename from doc/databases/persistence-hibernate/index.html
rename to doc/relational-databases/persistence-hibernate/index.html
index 6d983ce..6a51473 100644
--- a/doc/databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -1,19 +1,24 @@
 Void Framework – Hibernate
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
-Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.2.1</version>
+    <version>1.3.0</version>
 </dependency>
 

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
-Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

Exemple
@Entity
+Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

Identifier generator
Identifier type Assignable to Identifier generator annotation
CUID CUID, String, byte[] @CuidGenerator
UUID UUID, String, byte[] @UuidGenerator

Exemple
@Entity
 @DynamicUpdate
 @Table(name = "NEWS")
 public class NewsModel extends Model {
 
+    @Id
+    @UuidGenerator
+    @Column(name = "ID", updatable = false, nullable = false)
+    private UUID id;
+
     @Column(name = "TITLE", nullable = false)
     private String title;
 
diff --git a/doc/scheduler/index.html b/doc/scheduler/index.html
index d5e5b1b..c2f6270 100644
--- a/doc/scheduler/index.html
+++ b/doc/scheduler/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduler
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Scheduler

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduler

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index af3f82b..3c6a962 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduling a local job
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay defines the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate defines the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay defines the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron defines a CRON-like expression. The default value is empty (disabled).
cronZone defines the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay defines the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate defines the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay defines the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron defines a CRON-like expression. The default value is empty (disabled).
cronZone defines the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
 public final class Ping {
 
     private static final Logger LOGGER = LoggerFactory.getLogger(Ping.class);
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index 1fb5f4b..54ba469 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -2,14 +2,14 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifact">Void Framework – FreeMarker
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.2.1</version>
+    <version>1.3.0</version>
 </dependency>
-

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version 
+

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
-on the official website.

Templates location
Templates should be placed in the resources/views directory.

© 2022 Void Framework

+on the official website.

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/template/index.html b/doc/template/index.html
index 17282bd..e2d96d3 100644
--- a/doc/template/index.html
+++ b/doc/template/index.html
@@ -1,7 +1,7 @@
 Void Framework – Template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Template

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Template

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/testing/index.html b/doc/testing/index.html
new file mode 100644
index 0000000..86b9a9e
--- /dev/null
+++ b/doc/testing/index.html
@@ -0,0 +1,8 @@
+Void Framework – Testing
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Testing

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
new file mode 100644
index 0000000..ce60a39
--- /dev/null
+++ b/doc/testing/junit-extension/index.html
@@ -0,0 +1,37 @@
+Void Framework – JUnit's extension
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+    <groupId>dev.voidframework</groupId>
+    <artifactId>voidframework-test</artifactId>
+    <version>1.3.0</version>
+</dependency>
+

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
+@ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
+final class MySimpleUnitTest {
+
+    @Mock
+    private MyRepository myRepository;
+
+    @InjectMock
+    @Spy
+    private MyService myService;
+
+    @Test
+    void myLittleTest() {
+        // Arrange
+        Mockito.when(myRepository.findAll()).thenReturn(Collections.emptyList());
+
+        // Act
+        myService.myMethod();
+
+        // Assert
+        Mockito.verify(myRepository, Mockito.times(1)).findAll();
+    }
+}
+

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/vfs/index.html b/doc/vfs/index.html
new file mode 100644
index 0000000..7513e23
--- /dev/null
+++ b/doc/vfs/index.html
@@ -0,0 +1,8 @@
+Void Framework – Virtual File Storage
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Virtual File Storage

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/vfs/introduction/index.html b/doc/vfs/introduction/index.html
new file mode 100644
index 0000000..ad580d9
--- /dev/null
+++ b/doc/vfs/introduction/index.html
@@ -0,0 +1,60 @@
+Void Framework – Using Virtual File Storage
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+    <groupId>dev.voidframework</groupId>
+    <artifactId>voidframework-vfs</artifactId>
+    <version>1.3.0</version>
+</dependency>
+

Configuration
Different VirtualFileStorage implementation must be configured in voidframework.vfs namespace. The following configuration key can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
+Note that each implementation can have extra configuration keys.

Example
voidframework {
+    vfs {
+
+        memory {
+            className = "dev.voidframework.vfs.engine.MemoryVirtualFileStorage"
+            default = true
+        }
+
+        disk1 {
+            className = "dev.voidframework.vfs.engine.DiskVirtualFileStorage"
+            default = false
+
+            basePath = /tmp/
+        }
+
+        disk2 {
+            className = "dev.voidframework.vfs.engine.DiskVirtualFileStorage"
+            default = false
+
+            basePath = /mount/netstorage/
+        }
+    }
+}
+

Usage
@Singleton
+@WebController(prefixRoute = "/upload")
+public class UploadController {
+
+    private final VirtualFileStorage vfs;
+
+    @Inject
+    public UploadController(final VirtualFileStorage vfs) {
+
+        this.vfs = vfs;
+    }
+
+    @RequestRoute(method = HttpMethod.POST, name = "uploadFile")
+    public Result uploadFile(final Context context) {
+
+        final FormItem formItem = context.getRequest().getBodyContent().asFormData().getFirst("formFile");
+        if (formItem != null && formItem.fileSize() > 0) {
+            this.vfs.get().storeFile("upload", HttpContentTypes.APPLICATION_OCTET_STREAM, formItem.inputStream());
+        }
+
+        return Result.noContent();
+    }
+}
+

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index 29a7f2b..cef8c4e 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
@@ -17,7 +17,21 @@
         return Result.ok("Hello World");
     }
 }
-

Defining a route
A route is defined by two components, firstly @WebController defines the prefix that will be applied to all methods of the controller and by the @RequestRoute annotation providing various options. The latter tells the Void Framework that the method is an entry point.
@WebController
This annotation is based on the @Controller annotation. It simply allows the class to be better specified and provides additional options. This annotation can only be used at class level.
The annotation accepts the following parameter:
prefixRoute defines a prefix to be used on all endpoints in the class. By default, the value is empty.
@RequestRoute
This annotation allows you to configure an entry point that will process an incoming request. This annotation can only be used at method level.
The annotation accepts the following parameters:
method defines the HTTP method. The default value is HttpMethod.GET.
route defines a route. Regular expression with named capturing group can be used. The default value is /.
name defines an alias name who can be used with the reverse routing. By default, the value is empty.

Retrieving parameters
To work, a controller will probably need some incoming data. To do this, the @RequestPath, @RequestVariable and @RequestBody annotations make it easy to retrieve information from the request. It is also possible to retrieve information from the Context itself.
@RequestPath
This annotation allows you to extract parameters named in the URL path.
The annotation accepts the following parameter:
value defines the name of the parameter (correlated with the regexp used in the route definition) to extract.
@RequestVariable
This annotation allows you to extract query string value from the URI.
The annotation accepts the following parameter:
value defines the name of the query string value to extract.
@RequestBody
This annotation allows you to retrieve the contents of the request (i.e. from a POST query) as a Java object. If something goes wrong, the extracted value will be null.

Parameter types
It is sure that you will have to retrieve the parameters with their respective type (e.g. int, boolean, …). For this, Void Framework uses the converter mechanism to allow conversion from a String. By default, the following types are handled:
Boolean
Byte
Character
Double
Float
Integer
Locale
Long
Short
String
UUID

Handle custom types
To handle a new type, you simply have to implement a new converter. For more information, read the Type conversion chapter.

© 2022 Void Framework

+

Defining a route
A route is defined by two components, firstly @WebController defines the prefix that will be applied to all methods of the controller and by the @RequestRoute annotation providing various options. The latter tells the Void Framework that the method is an entry point.
@WebController
This annotation is based on the @Controller annotation. It simply allows the class to be better specified and provides additional options. This annotation can only be used at class level.
The annotation accepts the following parameter:
prefixRoute defines a prefix to be used on all endpoints in the class. By default, the value is empty.
@RequestRoute
This annotation allows you to configure an entry point that will process an incoming request. This annotation can only be used at method level.
The annotation accepts the following parameters:
method defines the HTTP method. The default value is HttpMethod.GET.
route defines a route. Regular expression with named capturing group can be used. The default value is /.
name defines an alias name who can be used with the reverse routing. By default, the value is empty.

Retrieving parameters
To work, a controller will probably need some incoming data. To do this, the @RequestPath, @RequestVariable and @RequestBody annotations make it easy to retrieve information from the request. It is also possible to retrieve information from the Context itself.
@RequestPath
This annotation allows you to extract parameters named in the URL path.
The annotation accepts the following parameter:
value defines the name of the parameter (correlated with the regexp used in the route definition) to extract.
@RequestVariable
This annotation allows you to extract query string value (simple or array) from the URI.
The annotation accepts the following parameter:
value defines the name of the query string value to extract.
@RequestBody
This annotation allows you to retrieve the contents of the request (i.e. from a POST query) as a Java object. If something goes wrong, the extracted value will be null.

Parameter types
It is sure that you will have to retrieve the parameters with their respective type (e.g. int, boolean, …). For this, Void Framework uses the converter mechanism to allow conversion from a String. By default, the following types are handled:
Boolean
Byte
Character
CUID
Double
Float
Integer
Locale
Long
Short
String
UUID

Handle custom types
To handle a new type, you simply have to implement a new converter. For more information, read the Type conversion chapter.

Example
@Singleton
+@WebController
+public class ExampleController {
+
+    @RequestRoute(route = "/")
+    public Result retrieveArrayFromQueryString(@RequestVariable("year") final int[] yearArray) {
+        return Result.ok(Yaml.toString(yearArray));
+    }
+
+     @RequestRoute(method = HttpMethod.POST, route = "/")
+    public Result retrieveListFromBody(@RequestBody("year") final List<Integer> yearList) {
+        return Result.ok(Yaml.toString(yearList));
+    }
+}
+

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index 0080a2e..60052b5 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the">Void Framework – Filters
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
 Note that the use of dependencies direct injection is possible in filters.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
 @Singleton
 @WebController
diff --git a/doc/web/index.html b/doc/web/index.html
index 39b1e45..99e3362 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Web

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Web

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/render-template/index.html b/doc/web/render-template/index.html
index c0117e7..e86f7e7 100644
--- a/doc/web/render-template/index.html
+++ b/doc/web/render-template/index.html
@@ -2,7 +2,7 @@
 Although you can manually use the template engine, in most cases this would not be handy. Howev">Void Framework – Render template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Example
controller/HomeController.java
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Example
controller/HomeController.java
@Singleton
 @WebController
 public class HomeController {
 
diff --git a/doc/web/security-csrf/index.html b/doc/web/security-csrf/index.html
index 06d8e9b..edc6d0f 100644
--- a/doc/web/security-csrf/index.html
+++ b/doc/web/security-csrf/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is recommended tha">Void Framework – CSRF
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
 It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP.
Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/security-headers/index.html b/doc/web/security-headers/index.html
index a68aafb..c5ea74e 100644
--- a/doc/web/security-headers/index.html
+++ b/doc/web/security-headers/index.html
@@ -2,7 +2,7 @@
 Configuration The following configuration keys can be used in the configuration">Void Framework – Security headers
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
 You can disable one of the headers by assigning the value null. The header will then not be sent.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/session/index.html b/doc/web/session/index.html
index 7a7eca7..6e2b394 100644
--- a/doc/web/session/index.html
+++ b/doc/web/session/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the session is not stored on the server side, but on the client side v">Void Framework – Session
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Databases
Data source
Hibernate ORM
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Web
Controller
Session
Filters
CSRF
Security headers
Render template

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
 Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie.

Because session is implemented using cookies, there are some implications.The data size is limited to 4 KiB
Only string can be stored

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.

Read value
You can access the session data via the Context. Methods get or getOrDefault can be used.
@Singleton
 @WebController
 public class Controller {
diff --git a/index.html b/index.html
index aa490d3..a72d4e4 100644
--- a/index.html
+++ b/index.html
@@ -2,7 +2,7 @@
 Void Framework
Documentation
    
 Release notes
Light and modular Framework for Java
Stay focus on your business

Documentation
-Release notes

© 2022 Void Framework

+Release notes
Fork me on GitHub

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/index.xml b/index.xml
index dbed992..b2cd7c4 100644
--- a/index.xml
+++ b/index.xml
@@ -1,16 +1,14 @@
-Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioData sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
-Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Data sourcehttps://voidframework.dev/doc/databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
-Configuration Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Databaseshttps://voidframework.dev/doc/databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
@@ -19,25 +17,41 @@ Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.CSRFhttps://voidframework.dev/doc/web/security-csrf/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-csrf/Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
-&nbsp; It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP. Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
+&nbsp; It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP. Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.Data sourcehttps://voidframework.dev/doc/relational-databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
+Installation Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Data sourcehttps://voidframework.dev/doc/relational-databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
+Installation Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
-Method Description config Retrieves a value from the configuration displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, &hellip;) i18n / _ Translates a message urlfor Retrieves an URL from the router (reverse router) Variable Description isDevMode Indicates whether the application is in dev mode lang Contains the current language languages Contains all available languages voidFrameworkVersion Contains the current Void Framework version &nbsp; FreeMarker provides a lot of other built-in methods & variables.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
-Method Description config Retrieves a value from the configuration displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, &hellip;) i18n / _ Translates a message urlfor Retrieves an URL from the router (reverse router) Variable Description isDevMode Indicates whether the application is in dev mode lang Contains the current language languages Contains all available languages voidFrameworkVersion Contains the current Void Framework version &nbsp; FreeMarker provides a lot of other built-in methods & variables.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Configuration The following configuration keys can be used in the configuration file of your application:
+voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Configuration The following configuration keys can be used in the configuration file of your application:
+voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
-priority is used to define when the method will be called in relation to the others.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.2.1 2022-09-15
-Fix The "Modules loaded" log is displayed too early Fix Remove unused "GlobalFilterDefinition" interface Improved Add converter String to Locale (Web). Used to extract Locale from incoming request (route path or query parameter) 1.2.0 2022-09-05
-Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053) New Add SecurityHeadersFilter New Add unit test JUnit extension and annotation New Add ability to fetch remote configuration provider & "etcd" remote configuration provider New Add "Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.2.1 2022-09-15
-Fix The "Modules loaded" log is displayed too early Fix Remove unused "GlobalFilterDefinition" interface Improved Add converter String to Locale (Web). Used to extract Locale from incoming request (route path or query parameter) 1.2.0 2022-09-05
-Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053) New Add SecurityHeadersFilter New Add unit test JUnit extension and annotation New Add ability to fetch remote configuration provider & "etcd" remote configuration provider New Add "Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.3.0 2022-11-07
+Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003) New WebSocket support New Can configure temporary files location (voidframework.web.server.tempFileLocation) New Mockito annotation support New CUID: a Collision-resistant Unique ID New Add HttpHeaderNames class New Virtual File Storage New No HTTP request timeout (voidframework.web.server.idleTimeout) Fixed The abbreviation of "december" is now correct (scheduler) Fixed "Day of Week" and "Month" can't be zero (Scheduler) Fixed Redis methods addInList, getFromList and decrement now working correctly Fixed Force close all InputStream of uploaded files Fixed Can use template-freemarker without web Improved Configuration Key/Value from CLI JVM properties (-D flag) Improved Annotation @RequestVariable can now retrieve array Improved Move cache annotations to subpackage annotation Improved Use wrap/unwrap on Memory cache engine Improved Updated version of all dependencies Improved Redis parameter connectionTimeout is now a duration Improved Rename all utility classes Improved Add new redirection methods on Result Improved HttpRequestBodyContent::asRaw is now an InputStream Improved Redis::addInList now return the current list size Improved ValidationError is now a record 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.3.0 2022-11-07
+Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003) New WebSocket support New Can configure temporary files location (voidframework.web.server.tempFileLocation) New Mockito annotation support New CUID: a Collision-resistant Unique ID New Add HttpHeaderNames class New Virtual File Storage New No HTTP request timeout (voidframework.web.server.idleTimeout) Fixed The abbreviation of "december" is now correct (scheduler) Fixed "Day of Week" and "Month" can't be zero (Scheduler) Fixed Redis methods addInList, getFromList and decrement now working correctly Fixed Force close all InputStream of uploaded files Fixed Can use template-freemarker without web Improved Configuration Key/Value from CLI JVM properties (-D flag) Improved Annotation @RequestVariable can now retrieve array Improved Move cache annotations to subpackage annotation Improved Use wrap/unwrap on Memory cache engine Improved Updated version of all dependencies Improved Redis parameter connectionTimeout is now a duration Improved Rename all utility classes Improved Add new redirection methods on Result Improved HttpRequestBodyContent::asRaw is now an InputStream Improved Redis::addInList now return the current list size Improved ValidationError is now a record 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
@@ -58,6 +72,10 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index a2e93cb..3f5c733 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,14 +1,15 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.2.1

-2022-09-15
Fix The "Modules loaded" log is displayed too early
Fix Remove unused "GlobalFilterDefinition" interface
Improved Add converter String to Locale (Web). Used to extract Locale from incoming request (route path or query parameter)

1.2.0

-2022-09-05
Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053)
New Add SecurityHeadersFilter
New Add unit test JUnit extension and annotation
New Add ability to fetch remote configuration provider & "etcd" remote configuration provider
New Add "http" remote configuration provider
New Add CharConstants & StringConstants classes
Improved Force EntityManagerFactory initialization during boot sequence
Improved Add new Result methods to handle empty content easily
Improved Validation constraints can be grouped
Improved Clean code
Improved Better boolean support (Freemarker / config)
Improved Refactoring module "web" (move files, new constant values, unit tests)
Improved Updated version of all dependencies

1.1.2

+Release notes
1.3.0

+2022-11-07
Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003)
New WebSocket support
New Can configure temporary files location (voidframework.web.server.tempFileLocation)
New Mockito annotation support
New CUID: a Collision-resistant Unique ID
New Add HttpHeaderNames class
New Virtual File Storage
New No HTTP request timeout (voidframework.web.server.idleTimeout)
Fixed The abbreviation of "december" is now correct (scheduler)
Fixed "Day of Week" and "Month" can't be zero (Scheduler)
Fixed Redis methods addInList, getFromList and decrement now working correctly
Fixed Force close all InputStream of uploaded files
Fixed Can use template-freemarker without web
Improved Configuration Key/Value from CLI JVM properties (-D flag)
Improved Annotation @RequestVariable can now retrieve array
Improved Move cache annotations to subpackage annotation
Improved Use wrap/unwrap on Memory cache engine
Improved Updated version of all dependencies
Improved Redis parameter connectionTimeout is now a duration
Improved Rename all utility classes
Improved Add new redirection methods on Result
Improved HttpRequestBodyContent::asRaw is now an InputStream
Improved Redis::addInList now return the current list size
Improved ValidationError is now a record

1.2.1

+2022-09-15
Fixed The "Modules loaded" log is displayed too early
Fixed Remove unused "GlobalFilterDefinition" interface
Improved Add converter String to Locale (Web). Used to extract Locale from incoming request (route path or query parameter)

1.2.0

+2022-09-05
Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053)
New Add SecurityHeadersFilter
New Add unit test JUnit extension and annotation
New Add ability to fetch remote configuration provider & "etcd" remote configuration provider
New Add "http" remote configuration provider
New Add CharConstants & StringConstants classes
Improved Force EntityManagerFactory initialization during boot sequence
Improved Add new Result methods to handle empty content easily
Improved Validation constraints can be grouped
Improved Clean code
Improved Better boolean support (Freemarker / config)
Improved Refactoring module "web" (move files, new constant values, unit tests)
Improved Updated version of all dependencies

1.1.2

 2022-08-02
Fixed EntityManagerFactory don't find models on multiple-jars project

1.1.1

-2022-07-24
Improved Change CSRF signature algorithm to HMACSHA256
Fixed Error 500 CSRF when POST request render template

1.1.0

-2022-07-22
New Methods on Reflection util class: getAnnotatedField(Object, Class) and getAnnotatedField(Class, Class)
New Configuration keys to define number of I/O and Worker threads (Web)
New Redis (base + cache + healthcheck)
New CSRF token
Improved No longer necessary for HealthChecker to be Singleton
Improved Add cache abstraction helper
Improved Session signature key configuration is now required
Improved Rename ApplicationLauncher to VoidApplication
Improved Updated version of all dependencies
Fixed Cookie revocation not working
Fixed C3P0/HikariCP settings
Fixed Issue on routes sorting when regex and capture regex are used
Fixed Assets not found when devMode=false
Fixed Hibernate : Models not found when application is compiled

1.0.1

-2022-07-08
New Ability to retrieve XML body content as Java object
Improved Cache management : rename the annotation Cache to CacheResult and add CacheRemove
Fixed Removed I18N reference from Hibernate module
Fixed Transactional annotation : rollback not occur on unchecked exception
Fixed Routes are randomly sorted

1.0.0

+2022-07-24
Fixed Error 500 CSRF when POST request render template
Improved Change CSRF signature algorithm to HMACSHA256

1.1.0

+2022-07-22
New Methods on Reflection util class: getAnnotatedField(Object, Class) and getAnnotatedField(Class, Class)
New Configuration keys to define number of I/O and Worker threads (Web)
New Redis (base + cache + healthcheck)
New CSRF token
Fixed Cookie revocation not working
Fixed C3P0/HikariCP settings
Fixed Issue on routes sorting when regex and capture regex are used
Fixed Assets not found when devMode=false
Fixed Hibernate : Models not found when application is compiled
Improved No longer necessary for HealthChecker to be Singleton
Improved Add cache abstraction helper
Improved Session signature key configuration is now required
Improved Rename ApplicationLauncher to VoidApplication
Improved Updated version of all dependencies

1.0.1

+2022-07-08
New Ability to retrieve XML body content as Java object
Fixed Removed I18N reference from Hibernate module
Fixed Transactional annotation : rollback not occur on unchecked exception
Fixed Routes are randomly sorted
Improved Cache management : rename the annotation Cache to CacheResult and add CacheRemove

1.0.0

 2022-07-02
Initial release

© 2022 Void Framework

 Void Framework is released under the MIT License

 
diff --git a/sitemap.xml b/sitemap.xml
index 071f0ed..3ae5ca1 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/datasource/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/databases/persistence-hibernate/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/template/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/
\ No newline at end of file

From 488059d9ae4b62756bf32720efa050d6e36a307a Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Mon, 7 Nov 2022 19:45:26 +0000
Subject: [PATCH 27/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/redis-cache/index.html              |  2 +-
 doc/core/configuration/index.html             |  4 +--
 .../new-application/index.html                |  4 +--
 doc/index.xml                                 | 28 ++++++++--------
 .../using-i18n/index.html                     |  2 +-
 doc/nosql-databases/redis/index.html          |  4 +--
 .../datasource/index.html                     |  4 +--
 .../persistence-hibernate/index.html          |  2 +-
 doc/template/freemarker/index.html            |  2 +-
 doc/testing/junit-extension/index.html        |  2 +-
 doc/vfs/introduction/index.html               |  2 +-
 index.xml                                     | 32 +++++++++----------
 releasenotes/index.html                       |  7 ++--
 14 files changed, 49 insertions(+), 48 deletions(-)

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 6fbfb08..54c2182 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.3.0</version>
+    <version>1.3.1</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index c0fde8f..68763a5 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.3.0</version>
+    <version>1.3.1</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index ec0477f..a506764 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -25,7 +25,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.3.0</version>
+  <version>1.3.1</version>
 </dependency>
 
voidframework {
     code {
@@ -60,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.3.0</version>
+  <version>1.3.1</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index cb4777b..79b3fad 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.3.0</version>
+    <version>1.3.1</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.3.0</version>
+    <version>1.3.1</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/index.xml b/doc/index.xml
index 455d91e..c019fa2 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,13 +1,13 @@
 Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
@@ -24,18 +24,18 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
@@ -43,10 +43,10 @@ priority is used to define when the method will be called in relation to the oth
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -70,10 +70,10 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index fd76582..ff3da79 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.3.0</version>
+    <version>1.3.1</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index 504e413..be4ed8a 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
-    <version>1.3.0</version>
+    <version>1.3.1</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
-    <version>1.3.0</version>
+    <version>1.3.1</version>
 </dependency>
 

Example
@Service
 public final class ExampleService {
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index 499a6bc..0b0e9f0 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -5,12 +5,12 @@
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.3.0</version>
+    <version>1.3.1</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.3.0</version>
+    <version>1.3.1</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index 6a51473..52e86d1 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -6,7 +6,7 @@
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.3.0</version>
+    <version>1.3.1</version>
 </dependency>
 

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
 Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

Identifier generator
Identifier type Assignable to Identifier generator annotation
CUID CUID, String, byte[] @CuidGenerator
UUID UUID, String, byte[] @UuidGenerator

Exemple
@Entity
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index 54ba469..64ccab5 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.3.0</version>
+    <version>1.3.1</version>
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index ce60a39..c2d8d17 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
-    <version>1.3.0</version>
+    <version>1.3.1</version>
 </dependency>
 

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
 @ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
diff --git a/doc/vfs/introduction/index.html b/doc/vfs/introduction/index.html
index ad580d9..272d97e 100644
--- a/doc/vfs/introduction/index.html
+++ b/doc/vfs/introduction/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
-    <version>1.3.0</version>
+    <version>1.3.1</version>
 </dependency>
 

Configuration
Different VirtualFileStorage implementation must be configured in voidframework.vfs namespace. The following configuration key can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
 Note that each implementation can have extra configuration keys.

Example
voidframework {
diff --git a/index.xml b/index.xml
index b2cd7c4..7706d79 100644
--- a/index.xml
+++ b/index.xml
@@ -1,13 +1,13 @@
 Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
@@ -24,18 +24,18 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
@@ -43,14 +43,14 @@ priority is used to define when the method will be called in relation to the oth
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.3.0 2022-11-07
-Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003) New WebSocket support New Can configure temporary files location (voidframework.web.server.tempFileLocation) New Mockito annotation support New CUID: a Collision-resistant Unique ID New Add HttpHeaderNames class New Virtual File Storage New No HTTP request timeout (voidframework.web.server.idleTimeout) Fixed The abbreviation of "december" is now correct (scheduler) Fixed "Day of Week" and "Month" can't be zero (Scheduler) Fixed Redis methods addInList, getFromList and decrement now working correctly Fixed Force close all InputStream of uploaded files Fixed Can use template-freemarker without web Improved Configuration Key/Value from CLI JVM properties (-D flag) Improved Annotation @RequestVariable can now retrieve array Improved Move cache annotations to subpackage annotation Improved Use wrap/unwrap on Memory cache engine Improved Updated version of all dependencies Improved Redis parameter connectionTimeout is now a duration Improved Rename all utility classes Improved Add new redirection methods on Result Improved HttpRequestBodyContent::asRaw is now an InputStream Improved Redis::addInList now return the current list size Improved ValidationError is now a record 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.3.0 2022-11-07
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
+Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003) New WebSocket support New Can configure temporary files location (voidframework.web.server.tempFileLocation) New Mockito annotation support New CUID: a Collision-resistant Unique ID New Add HttpHeaderNames class New Virtual File Storage New No HTTP request timeout (voidframework.web.server.idleTimeout) Fixed The abbreviation of "december" is now correct (scheduler) Fixed "Day of Week" and "Month" can't be zero (Scheduler) Fixed Redis methods addInList, getFromList and decrement now working correctly Fixed Force close all InputStream of uploaded files Fixed Can use template-freemarker without web Improved Configuration Key/Value from CLI JVM properties (-D flag) Improved Annotation @RequestVariable can now retrieve array Improved Move cache annotations to subpackage annotation Improved Use wrap/unwrap on Memory cache engine Improved Updated version of all dependencies Improved Redis parameter connectionTimeout is now a duration Improved Rename all utility classes Improved Add new redirection methods on Result Improved HttpRequestBodyContent::asRaw is now an InputStream Improved Redis::addInList now return the current list size Improved ValidationError is now a record 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
 Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003) New WebSocket support New Can configure temporary files location (voidframework.web.server.tempFileLocation) New Mockito annotation support New CUID: a Collision-resistant Unique ID New Add HttpHeaderNames class New Virtual File Storage New No HTTP request timeout (voidframework.web.server.idleTimeout) Fixed The abbreviation of "december" is now correct (scheduler) Fixed "Day of Week" and "Month" can't be zero (Scheduler) Fixed Redis methods addInList, getFromList and decrement now working correctly Fixed Force close all InputStream of uploaded files Fixed Can use template-freemarker without web Improved Configuration Key/Value from CLI JVM properties (-D flag) Improved Annotation @RequestVariable can now retrieve array Improved Move cache annotations to subpackage annotation Improved Use wrap/unwrap on Memory cache engine Improved Updated version of all dependencies Improved Redis parameter connectionTimeout is now a duration Improved Rename all utility classes Improved Add new redirection methods on Result Improved HttpRequestBodyContent::asRaw is now an InputStream Improved Redis::addInList now return the current list size Improved ValidationError is now a record 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
@@ -72,10 +72,10 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 3f5c733..6818117 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,8 +1,9 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.3.0

+Release notes
1.3.1

+2022-11-07
Fixed NullPointerException if header Accept-Language not provided

1.3.0

 2022-11-07
Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003)
New WebSocket support
New Can configure temporary files location (voidframework.web.server.tempFileLocation)
New Mockito annotation support
New CUID: a Collision-resistant Unique ID
New Add HttpHeaderNames class
New Virtual File Storage
New No HTTP request timeout (voidframework.web.server.idleTimeout)
Fixed The abbreviation of "december" is now correct (scheduler)
Fixed "Day of Week" and "Month" can't be zero (Scheduler)
Fixed Redis methods addInList, getFromList and decrement now working correctly
Fixed Force close all InputStream of uploaded files
Fixed Can use template-freemarker without web
Improved Configuration Key/Value from CLI JVM properties (-D flag)
Improved Annotation @RequestVariable can now retrieve array
Improved Move cache annotations to subpackage annotation
Improved Use wrap/unwrap on Memory cache engine
Improved Updated version of all dependencies
Improved Redis parameter connectionTimeout is now a duration
Improved Rename all utility classes
Improved Add new redirection methods on Result
Improved HttpRequestBodyContent::asRaw is now an InputStream
Improved Redis::addInList now return the current list size
Improved ValidationError is now a record

1.2.1

 2022-09-15
Fixed The "Modules loaded" log is displayed too early
Fixed Remove unused "GlobalFilterDefinition" interface
Improved Add converter String to Locale (Web). Used to extract Locale from incoming request (route path or query parameter)

1.2.0

 2022-09-05
Security Upgrade Undertow version to 2.2.19 (CVE-2022-2053)
New Add SecurityHeadersFilter
New Add unit test JUnit extension and annotation
New Add ability to fetch remote configuration provider & "etcd" remote configuration provider
New Add "http" remote configuration provider
New Add CharConstants & StringConstants classes
Improved Force EntityManagerFactory initialization during boot sequence
Improved Add new Result methods to handle empty content easily
Improved Validation constraints can be grouped
Improved Clean code
Improved Better boolean support (Freemarker / config)
Improved Refactoring module "web" (move files, new constant values, unit tests)
Improved Updated version of all dependencies

1.1.2


From def5348567e3551eeccdbae913e7e2c5b8c79cf0 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 17 Nov 2022 18:13:05 +0000
Subject: [PATCH 28/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/redis-cache/index.html              |  2 +-
 doc/core/configuration/index.html             |  4 +--
 .../new-application/index.html                |  4 +--
 doc/index.xml                                 | 28 +++++++--------
 .../using-i18n/index.html                     |  2 +-
 doc/nosql-databases/redis/index.html          |  4 +--
 .../datasource/index.html                     |  4 +--
 .../persistence-hibernate/index.html          |  2 +-
 doc/template/freemarker/index.html            |  2 +-
 doc/testing/junit-extension/index.html        |  2 +-
 doc/vfs/introduction/index.html               |  2 +-
 index.xml                                     | 34 +++++++++----------
 releasenotes/index.html                       |  7 ++--
 14 files changed, 50 insertions(+), 49 deletions(-)

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 54c2182..c225f80 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.3.1</version>
+    <version>1.3.2</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 68763a5..561645a 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.3.1</version>
+    <version>1.3.2</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index a506764..3a6c5b3 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -25,7 +25,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.3.1</version>
+  <version>1.3.2</version>
 </dependency>
 
voidframework {
     code {
@@ -60,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.3.1</version>
+  <version>1.3.2</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 79b3fad..5032b23 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.3.1</version>
+    <version>1.3.2</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.3.1</version>
+    <version>1.3.2</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/index.xml b/doc/index.xml
index c019fa2..2912c74 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,13 +1,13 @@
 Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
@@ -24,18 +24,18 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
@@ -43,10 +43,10 @@ priority is used to define when the method will be called in relation to the oth
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -70,10 +70,10 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index ff3da79..069215e 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.3.1</version>
+    <version>1.3.2</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index be4ed8a..a43dacc 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
-    <version>1.3.1</version>
+    <version>1.3.2</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
-    <version>1.3.1</version>
+    <version>1.3.2</version>
 </dependency>
 

Example
@Service
 public final class ExampleService {
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index 0b0e9f0..47612db 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -5,12 +5,12 @@
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.3.1</version>
+    <version>1.3.2</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.3.1</version>
+    <version>1.3.2</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index 52e86d1..2bf04b2 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -6,7 +6,7 @@
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.3.1</version>
+    <version>1.3.2</version>
 </dependency>
 

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
 Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

Identifier generator
Identifier type Assignable to Identifier generator annotation
CUID CUID, String, byte[] @CuidGenerator
UUID UUID, String, byte[] @UuidGenerator

Exemple
@Entity
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index 64ccab5..d359c24 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.3.1</version>
+    <version>1.3.2</version>
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index c2d8d17..498e432 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
-    <version>1.3.1</version>
+    <version>1.3.2</version>
 </dependency>
 

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
 @ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
diff --git a/doc/vfs/introduction/index.html b/doc/vfs/introduction/index.html
index 272d97e..cd725f0 100644
--- a/doc/vfs/introduction/index.html
+++ b/doc/vfs/introduction/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
-    <version>1.3.1</version>
+    <version>1.3.2</version>
 </dependency>
 

Configuration
Different VirtualFileStorage implementation must be configured in voidframework.vfs namespace. The following configuration key can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
 Note that each implementation can have extra configuration keys.

Example
voidframework {
diff --git a/index.xml b/index.xml
index 7706d79..1e5001a 100644
--- a/index.xml
+++ b/index.xml
@@ -1,13 +1,13 @@
 Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
@@ -24,18 +24,18 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
@@ -43,15 +43,15 @@ priority is used to define when the method will be called in relation to the oth
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
-Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003) New WebSocket support New Can configure temporary files location (voidframework.web.server.tempFileLocation) New Mockito annotation support New CUID: a Collision-resistant Unique ID New Add HttpHeaderNames class New Virtual File Storage New No HTTP request timeout (voidframework.web.server.idleTimeout) Fixed The abbreviation of "december" is now correct (scheduler) Fixed "Day of Week" and "Month" can't be zero (Scheduler) Fixed Redis methods addInList, getFromList and decrement now working correctly Fixed Force close all InputStream of uploaded files Fixed Can use template-freemarker without web Improved Configuration Key/Value from CLI JVM properties (-D flag) Improved Annotation @RequestVariable can now retrieve array Improved Move cache annotations to subpackage annotation Improved Use wrap/unwrap on Memory cache engine Improved Updated version of all dependencies Improved Redis parameter connectionTimeout is now a duration Improved Rename all utility classes Improved Add new redirection methods on Result Improved HttpRequestBodyContent::asRaw is now an InputStream Improved Redis::addInList now return the current list size Improved ValidationError is now a record 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
-Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003) New WebSocket support New Can configure temporary files location (voidframework.web.server.tempFileLocation) New Mockito annotation support New CUID: a Collision-resistant Unique ID New Add HttpHeaderNames class New Virtual File Storage New No HTTP request timeout (voidframework.web.server.idleTimeout) Fixed The abbreviation of "december" is now correct (scheduler) Fixed "Day of Week" and "Month" can't be zero (Scheduler) Fixed Redis methods addInList, getFromList and decrement now working correctly Fixed Force close all InputStream of uploaded files Fixed Can use template-freemarker without web Improved Configuration Key/Value from CLI JVM properties (-D flag) Improved Annotation @RequestVariable can now retrieve array Improved Move cache annotations to subpackage annotation Improved Use wrap/unwrap on Memory cache engine Improved Updated version of all dependencies Improved Redis parameter connectionTimeout is now a duration Improved Rename all utility classes Improved Add new redirection methods on Result Improved HttpRequestBodyContent::asRaw is now an InputStream Improved Redis::addInList now return the current list size Improved ValidationError is now a record 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.3.2 2022-11-14 Fixed NullPointerException when requested config is null on FreeMarker 1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
+Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003) New WebSocket support New Can configure temporary files location (voidframework.web.server.tempFileLocation) New Mockito annotation support New CUID: a Collision-resistant Unique ID New Add HttpHeaderNames class New Virtual File Storage New No HTTP request timeout (voidframework.web.server.idleTimeout) Fixed The abbreviation of "december" is now correct (scheduler) Fixed "Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.3.2 2022-11-14 Fixed NullPointerException when requested config is null on FreeMarker 1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
+Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003) New WebSocket support New Can configure temporary files location (voidframework.web.server.tempFileLocation) New Mockito annotation support New CUID: a Collision-resistant Unique ID New Add HttpHeaderNames class New Virtual File Storage New No HTTP request timeout (voidframework.web.server.idleTimeout) Fixed The abbreviation of "december" is now correct (scheduler) Fixed "Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
@@ -72,10 +72,10 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 6818117..b50d0c0 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,8 +1,9 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.3.1

+Release notes
1.3.2

+2022-11-14
Fixed NullPointerException when requested config is null on FreeMarker

1.3.1

 2022-11-07
Fixed NullPointerException if header Accept-Language not provided

1.3.0

 2022-11-07
Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003)
New WebSocket support
New Can configure temporary files location (voidframework.web.server.tempFileLocation)
New Mockito annotation support
New CUID: a Collision-resistant Unique ID
New Add HttpHeaderNames class
New Virtual File Storage
New No HTTP request timeout (voidframework.web.server.idleTimeout)
Fixed The abbreviation of "december" is now correct (scheduler)
Fixed "Day of Week" and "Month" can't be zero (Scheduler)
Fixed Redis methods addInList, getFromList and decrement now working correctly
Fixed Force close all InputStream of uploaded files
Fixed Can use template-freemarker without web
Improved Configuration Key/Value from CLI JVM properties (-D flag)
Improved Annotation @RequestVariable can now retrieve array
Improved Move cache annotations to subpackage annotation
Improved Use wrap/unwrap on Memory cache engine
Improved Updated version of all dependencies
Improved Redis parameter connectionTimeout is now a duration
Improved Rename all utility classes
Improved Add new redirection methods on Result
Improved HttpRequestBodyContent::asRaw is now an InputStream
Improved Redis::addInList now return the current list size
Improved ValidationError is now a record

1.2.1

 2022-09-15
Fixed The "Modules loaded" log is displayed too early
Fixed Remove unused "GlobalFilterDefinition" interface
Improved Add converter String to Locale (Web). Used to extract Locale from incoming request (route path or query parameter)

1.2.0


From 2fbd47d09cb178c9a00b8fdffe558515dec5f9b7 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Sat, 19 Nov 2022 08:39:23 +0000
Subject: [PATCH 29/75] Automated website build

---
 doc/advanced/advanced/index.html              |  2 +-
 doc/advanced/index.html                       |  2 +-
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/index.html                          |  2 +-
 doc/cache/redis-cache/index.html              |  2 +-
 doc/cache/using-cache/index.html              |  2 +-
 doc/core/boot-sequence/index.html             |  2 +-
 doc/core/class-scanning/index.html            |  2 +-
 doc/core/configuration/index.html             |  2 +-
 doc/core/index.html                           |  2 +-
 doc/core/life-cycle/index.html                |  2 +-
 doc/core/type-conversion/index.html           |  2 +-
 doc/getting-started/index.html                |  2 +-
 .../new-application/index.html                |  2 +-
 doc/getting-started/requirements/index.html   |  2 +-
 .../upgrading-from-old-version/index.html     |  2 +-
 doc/i18n/index.html                           |  2 +-
 doc/index.html                                |  2 +-
 doc/index.xml                                 |  3 +-
 .../using-i18n/index.html                     |  2 +-
 doc/nosql-databases/index.html                |  2 +-
 doc/nosql-databases/redis/index.html          |  2 +-
 .../datasource/index.html                     |  2 +-
 doc/relational-databases/index.html           |  2 +-
 .../persistence-hibernate/index.html          |  2 +-
 doc/scheduler/index.html                      |  2 +-
 doc/scheduler/scheduling-job-cron/index.html  |  2 +-
 doc/template/freemarker/index.html            |  2 +-
 doc/template/index.html                       |  2 +-
 doc/template/using-template/index.html        | 33 +++++++++++++++++++
 doc/testing/index.html                        |  2 +-
 doc/testing/junit-extension/index.html        |  2 +-
 doc/vfs/index.html                            |  2 +-
 doc/vfs/introduction/index.html               |  2 +-
 doc/web/controller/index.html                 |  2 +-
 doc/web/filters/index.html                    |  2 +-
 doc/web/index.html                            |  2 +-
 doc/web/render-template/index.html            |  2 +-
 doc/web/security-csrf/index.html              |  2 +-
 doc/web/security-headers/index.html           |  2 +-
 doc/web/session/index.html                    |  2 +-
 index.xml                                     |  3 +-
 sitemap.xml                                   |  2 +-
 43 files changed, 77 insertions(+), 42 deletions(-)
 create mode 100644 doc/template/using-template/index.html

diff --git a/doc/advanced/advanced/index.html b/doc/advanced/advanced/index.html
index 45c73a9..9b92035 100644
--- a/doc/advanced/advanced/index.html
+++ b/doc/advanced/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – reference.conf

 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/advanced/index.html b/doc/advanced/index.html
index 0083980..bc8d133 100644
--- a/doc/advanced/index.html
+++ b/doc/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – Advanced
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Advanced

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Advanced

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index c225f80..27b84dd 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,7 +2,7 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
     <version>1.3.2</version>
diff --git a/doc/cache/index.html b/doc/cache/index.html
index c1b1802..c36fc63 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 561645a..5ad779e 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
     <version>1.3.2</version>
diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index 3a1c7d0..c2c9308 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,7 +2,7 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
 Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index 23e215d..2ddc172 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c . t u r c a h i l l P . c c e r b e o c o o n o v o m v">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index 7d32d64..9fda9b0 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,7 +2,7 @@
 Bindable classes (see below) classes implementing the TypeConverter interface classes which e">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
 3 types of elements are recognised during the scan:
Bindable classes (see below)
classes implementing the TypeConverter interface
classes which extend AbstractModule (Guice)

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@BindClass Indicates that an annotated class is a “Bindable”
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index 3a6c5b3..9903797 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -1,7 +1,7 @@
 Void Framework – Configuration
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
 

Retrieve configuration value from Java
@Service
 public class MyService {
 
diff --git a/doc/core/index.html b/doc/core/index.html
index 106f178..6cc5fca 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Core

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Core

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index 5555f4f..da85774 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index f01c7d7..9e9f67f 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index c03bec0..cc9e878 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Getting Started

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Getting Started

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 5032b23..327d1fc 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,7 +2,7 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
     <version>1.3.2</version>
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index 2796e83..b686fa4 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index 1d743f9..a444d56 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.1.0 ApplicationLa">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index 39bd405..f0a63fa 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Internationalization

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Internationalization

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index 4627ecc..faae85e 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Documentation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Documentation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 2912c74..7f5d9de 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -72,7 +72,8 @@ Using conversion The conversion is used via the Conversion service which is acce
 To enable this module, just add following lines to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 069215e..e197ce0 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
     <version>1.3.2</version>
diff --git a/doc/nosql-databases/index.html b/doc/nosql-databases/index.html
index 6f364d4..b282cc1 100644
--- a/doc/nosql-databases/index.html
+++ b/doc/nosql-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – NoSQL Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

NoSQL Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

NoSQL Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index a43dacc..212e9b7 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -2,7 +2,7 @@
 Installation To enable this module, just add following lines to ">Void Framework – Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
     <version>1.3.2</version>
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index 47612db..b0c185d 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -1,7 +1,7 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
diff --git a/doc/relational-databases/index.html b/doc/relational-databases/index.html
index bb10d00..99c0982 100644
--- a/doc/relational-databases/index.html
+++ b/doc/relational-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Relational Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Relational Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Relational Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index 2bf04b2..4f3e4e1 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -2,7 +2,7 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
diff --git a/doc/scheduler/index.html b/doc/scheduler/index.html
index c2f6270..a3c85d0 100644
--- a/doc/scheduler/index.html
+++ b/doc/scheduler/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduler
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduler

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduler

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index 3c6a962..a7828a1 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduling a local job
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay defines the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate defines the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay defines the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron defines a CRON-like expression. The default value is empty (disabled).
cronZone defines the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay defines the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate defines the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay defines the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron defines a CRON-like expression. The default value is empty (disabled).
cronZone defines the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
 public final class Ping {
 
     private static final Logger LOGGER = LoggerFactory.getLogger(Ping.class);
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index d359c24..1d4e1e2 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifact">Void Framework – FreeMarker
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
     <version>1.3.2</version>
diff --git a/doc/template/index.html b/doc/template/index.html
index e2d96d3..9499286 100644
--- a/doc/template/index.html
+++ b/doc/template/index.html
@@ -1,7 +1,7 @@
 Void Framework – Template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Template

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Template

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/template/using-template/index.html b/doc/template/using-template/index.html
new file mode 100644
index 0000000..9f7df6b
--- /dev/null
+++ b/doc/template/using-template/index.html
@@ -0,0 +1,33 @@
+Void Framework – Using template
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using template
Sooner or later you will need to generate documents (HTML, PDF…). Void Framework provides all the tools you need!

Example
public class TemplateExample {
+
+    private final TemplateRenderer templateRenderer;
+
+    @Inject
+    public TemplateExample(final TemplateRenderer templateRenderer) {
+
+        this.templateRenderer = templateRenderer;
+    }
+
+    public void renderTemplate() {
+
+        final Map<String, Object> dataModel = new HashMap<>();
+        dataModel.put("greating.msg", "Hello World!")
+
+        final String result = templateRenderer.render(
+            "renderWithDataModel.ftl",
+            Locale.ENGLISH,
+            dataModel);
+
+        System.out.println(result);
+    }
+}
+
 
+Note that the data Map must be mutable. Internally the different implementations can add other data to it. If you provide a immutable Map, an exception will be thrown.

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/testing/index.html b/doc/testing/index.html
index 86b9a9e..afeee28 100644
--- a/doc/testing/index.html
+++ b/doc/testing/index.html
@@ -1,7 +1,7 @@
 Void Framework – Testing
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Testing

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Testing

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index 498e432..b01a5be 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -2,7 +2,7 @@
 To enable this module, just add following lines to th">Void Framework – JUnit's extension
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
     <version>1.3.2</version>
diff --git a/doc/vfs/index.html b/doc/vfs/index.html
index 7513e23..34fc374 100644
--- a/doc/vfs/index.html
+++ b/doc/vfs/index.html
@@ -1,7 +1,7 @@
 Void Framework – Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Virtual File Storage

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Virtual File Storage

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/vfs/introduction/index.html b/doc/vfs/introduction/index.html
index cd725f0..a48db88 100644
--- a/doc/vfs/introduction/index.html
+++ b/doc/vfs/introduction/index.html
@@ -1,7 +1,7 @@
 Void Framework – Using Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
     <version>1.3.2</version>
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index cef8c4e..f61cd64 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index 60052b5..883055c 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the">Void Framework – Filters
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
 Note that the use of dependencies direct injection is possible in filters.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
 @Singleton
 @WebController
diff --git a/doc/web/index.html b/doc/web/index.html
index 99e3362..9672969 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Web

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Web

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/render-template/index.html b/doc/web/render-template/index.html
index e86f7e7..1f5d2e8 100644
--- a/doc/web/render-template/index.html
+++ b/doc/web/render-template/index.html
@@ -2,7 +2,7 @@
 Although you can manually use the template engine, in most cases this would not be handy. Howev">Void Framework – Render template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Example
controller/HomeController.java
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Example
controller/HomeController.java
@Singleton
 @WebController
 public class HomeController {
 
diff --git a/doc/web/security-csrf/index.html b/doc/web/security-csrf/index.html
index edc6d0f..e1ea176 100644
--- a/doc/web/security-csrf/index.html
+++ b/doc/web/security-csrf/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is recommended tha">Void Framework – CSRF
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
 It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP.
Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/security-headers/index.html b/doc/web/security-headers/index.html
index c5ea74e..4ef7b3f 100644
--- a/doc/web/security-headers/index.html
+++ b/doc/web/security-headers/index.html
@@ -2,7 +2,7 @@
 Configuration The following configuration keys can be used in the configuration">Void Framework – Security headers
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
 You can disable one of the headers by assigning the value null. The header will then not be sent.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/session/index.html b/doc/web/session/index.html
index 6e2b394..d56bb06 100644
--- a/doc/web/session/index.html
+++ b/doc/web/session/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the session is not stored on the server side, but on the client side v">Void Framework – Session
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
 Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie.

Because session is implemented using cookies, there are some implications.The data size is limited to 4 KiB
Only string can be stored

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.

Read value
You can access the session data via the Context. Methods get or getOrDefault can be used.
@Singleton
 @WebController
 public class Controller {
diff --git a/index.xml b/index.xml
index 1e5001a..534849a 100644
--- a/index.xml
+++ b/index.xml
@@ -74,7 +74,8 @@ Using conversion The conversion is used via the Conversion service which is acce
 To enable this module, just add following lines to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
diff --git a/sitemap.xml b/sitemap.xml
index 3ae5ca1..015acea 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/template/using-template/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/
\ No newline at end of file

From c15564af6a55fda5d5641bdbd9e3b88963d4a077 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Mon, 5 Dec 2022 21:44:39 +0000
Subject: [PATCH 30/75] Automated website build

---
 doc/advanced/advanced/index.html              |   2 +-
 doc/advanced/index.html                       |   2 +-
 doc/cache/in-memory-cache/index.html          |   4 +-
 doc/cache/index.html                          |   2 +-
 doc/cache/redis-cache/index.html              |   6 +-
 doc/cache/using-cache/index.html              |   2 +-
 doc/core/boot-sequence/index.html             |   4 +-
 doc/core/class-scanning/index.html            |   2 +-
 doc/core/configuration/index.html             |   6 +-
 doc/core/index.html                           |   2 +-
 doc/core/life-cycle/index.html                |   2 +-
 doc/core/type-conversion/index.html           |   2 +-
 doc/getting-started/index.html                |   2 +-
 .../new-application/index.html                |   6 +-
 doc/getting-started/requirements/index.html   |   2 +-
 .../upgrading-from-old-version/index.html     |   2 +-
 doc/i18n/index.html                           |   2 +-
 doc/index.html                                |   2 +-
 doc/index.xml                                 |  42 +++---
 .../using-i18n/index.html                     |   4 +-
 doc/nosql-databases/index.html                |   2 +-
 doc/nosql-databases/redis/index.html          |   6 +-
 .../datasource/index.html                     |   6 +-
 doc/relational-databases/index.html           |   2 +-
 .../persistence-hibernate/index.html          |  13 +-
 .../persistence-jooq/index.html               | 128 ++++++++++++++++++
 .../transactional/index.html                  |   9 ++
 doc/scheduler/index.html                      |   2 +-
 doc/scheduler/scheduling-job-cron/index.html  |   2 +-
 doc/template/freemarker/index.html            |   4 +-
 doc/template/index.html                       |   2 +-
 doc/template/using-template/index.html        |   2 +-
 doc/testing/index.html                        |   2 +-
 doc/testing/junit-extension/index.html        |   4 +-
 doc/vfs/index.html                            |   2 +-
 doc/vfs/introduction/index.html               |   4 +-
 doc/web/controller/index.html                 |   4 +-
 doc/web/filters/index.html                    |   2 +-
 doc/web/index.html                            |   2 +-
 doc/web/render-template/index.html            |   3 +-
 doc/web/security-csrf/index.html              |   2 +-
 doc/web/security-headers/index.html           |   2 +-
 doc/web/session/index.html                    |   2 +-
 index.xml                                     |  48 ++++---
 releasenotes/index.html                       |   6 +-
 sitemap.xml                                   |   2 +-
 46 files changed, 258 insertions(+), 103 deletions(-)
 create mode 100644 doc/relational-databases/persistence-jooq/index.html
 create mode 100644 doc/relational-databases/transactional/index.html

diff --git a/doc/advanced/advanced/index.html b/doc/advanced/advanced/index.html
index 9b92035..e50ec65 100644
--- a/doc/advanced/advanced/index.html
+++ b/doc/advanced/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – reference.conf
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/advanced/index.html b/doc/advanced/index.html
index bc8d133..4939d66 100644
--- a/doc/advanced/index.html
+++ b/doc/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – Advanced
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Advanced

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Advanced

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 27b84dd..8c23be5 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,10 +2,10 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.3.2</version>
+    <version>1.4.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/index.html b/doc/cache/index.html
index c36fc63..b622e30 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 5ad779e..62b1044 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -1,11 +1,11 @@
 Void Framework – Cache engine : Redis
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.4.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.3.2</version>
+    <version>1.4.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index c2c9308..0b751c1 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,7 +2,7 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
 Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index 2ddc172..86a0132 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -1,8 +1,8 @@
 Void Framework – Boot sequence
+S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G R o e l u L e L a a i o g i d C s ( c a i f o s 3 e d s e l n p a t C o f a ) m G e y c . t o u r c a h d i l l P . u c c e">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index 9fda9b0..42d41b7 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,7 +2,7 @@
 Bindable classes (see below) classes implementing the TypeConverter interface classes which e">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
 3 types of elements are recognised during the scan:
Bindable classes (see below)
classes implementing the TypeConverter interface
classes which extend AbstractModule (Guice)

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@BindClass Indicates that an annotated class is a “Bindable”
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index 9903797..fcbdb5d 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -1,7 +1,7 @@
 Void Framework – Configuration
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
 

Retrieve configuration value from Java
@Service
 public class MyService {
 
@@ -25,7 +25,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.3.2</version>
+  <version>1.4.0</version>
 </dependency>
 
voidframework {
     code {
@@ -60,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.3.2</version>
+  <version>1.4.0</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/core/index.html b/doc/core/index.html
index 6cc5fca..24303c9 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Core

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Core

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index da85774..c5725ee 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index 9e9f67f..c3cc65d 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index cc9e878..35c6def 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Getting Started

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Getting Started

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 327d1fc..6066617 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,15 +2,15 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.3.2</version>
+    <version>1.4.0</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.3.2</version>
+    <version>1.4.0</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index b686fa4..8f75c9a 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index a444d56..e92f68a 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.1.0 ApplicationLa">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index f0a63fa..75f45b8 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Internationalization

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Internationalization

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index faae85e..7501539 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Documentation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Documentation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 7f5d9de..1c893b7 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,13 +1,13 @@
 Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
-S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
-S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G R o e l u L e L a a i o g i d C s ( c a i f o s 3 e d s e l n p a t C o f a ) m G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G R o e l u L e L a a i o g i d C s ( c a i f o s 3 e d s e l n p a t C o f a ) m G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
@@ -24,18 +24,22 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
@@ -43,10 +47,10 @@ priority is used to define when the method will be called in relation to the oth
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -63,18 +67,20 @@ Define a Job To define a job, simply use the @Scheduled annotation on one or mor
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
-&nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
+&nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
+@Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
+@Transactional The transactional annotation itself defines the scope of a single database transaction.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Upgrading from old versionhttps://voidframework.dev/doc/getting-started/upgrading-from-old-version/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/upgrading-from-old-version/Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.
 1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now required 1.2.0 The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index e197ce0..5baf773 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,10 +1,10 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.3.2</version>
+    <version>1.4.0</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/index.html b/doc/nosql-databases/index.html
index b282cc1..47863bd 100644
--- a/doc/nosql-databases/index.html
+++ b/doc/nosql-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – NoSQL Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

NoSQL Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

NoSQL Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index 212e9b7..8ebe5b2 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -2,15 +2,15 @@
 Installation To enable this module, just add following lines to ">Void Framework – Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
-    <version>1.3.2</version>
+    <version>1.4.0</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
-    <version>1.3.2</version>
+    <version>1.4.0</version>
 </dependency>
 

Example
@Service
 public final class ExampleService {
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index b0c185d..f793a10 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -1,16 +1,16 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.3.2</version>
+    <version>1.4.0</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.3.2</version>
+    <version>1.4.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/relational-databases/index.html b/doc/relational-databases/index.html
index 99c0982..bc3b245 100644
--- a/doc/relational-databases/index.html
+++ b/doc/relational-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Relational Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Relational Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Relational Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index 4f3e4e1..cfcc417 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -2,14 +2,19 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.3.2</version>
+    <version>1.4.0</version>
 </dependency>
-

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
-Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

Identifier generator
Identifier type Assignable to Identifier generator annotation
CUID CUID, String, byte[] @CuidGenerator
UUID UUID, String, byte[] @UuidGenerator

Exemple
@Entity
+

Working with transaction manually
final EntityManager entityManager = this.entityManagerProvider.get();
+final EntityTransaction transaction = entityManager.getTransaction();
+
+transaction.begin();
+/* insert/update/delete operations */
+transaction.commit();
+

Identifier generator
Identifier type Assignable to Identifier generator annotation
CUID CUID, String, byte[] @CuidGenerator
UUID UUID, String, byte[] @UuidGenerator

Exemple
@Entity
 @DynamicUpdate
 @Table(name = "NEWS")
 public class NewsModel extends Model {
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
new file mode 100644
index 0000000..15e0b13
--- /dev/null
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -0,0 +1,128 @@
+Void Framework – Hibernate
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
+    <groupId>dev.voidframework</groupId>
+    <artifactId>voidframework-persistence-jooq</artifactId>
+    <version>1.4.0</version>
+</dependency>
+

Generator
To work, jOOQ needs files generated during the compilation of the project. It is possible to generate the required classes in different ways (scan database, scan entity, …). For more information, please visit the official jOOQ website.
To enable code generation, add & customize the code below.
pom.xml
<build>
+    <plugins>
+        <plugin>
+            <groupId>org.jooq</groupId>
+            <artifactId>jooq-codegen-maven</artifactId>
+            <executions>
+                <execution>
+                    <id>jooq-codegen</id>
+                    <phase>generate-sources</phase>
+                    <goals>
+                        <goal>generate</goal>
+                    </goals>
+                </execution>
+            </executions>
+            <configuration>
+                <configurationFile>${project.build.sourceDirectory}/../resources/jooq-code-generator.xml</configurationFile>
+            </configuration>
+        </plugin>
+        <plugin>
+            <groupId>org.codehaus.mojo</groupId>
+            <artifactId>build-helper-maven-plugin</artifactId>
+            <executions>
+                <execution>
+                    <id>add-jooq-gen-code-test-sources</id>
+                    <phase>generate-sources</phase>
+                    <goals>
+                        <goal>add-test-source</goal>
+                    </goals>
+                    <configuration>
+                        <sources>
+                            <source>${project.build.directory}/generated-sources/java/</source>
+                        </sources>
+                    </configuration>
+                </execution>
+            </executions>
+        </plugin>
+    </plugins>
+</build>
+
jooq-code-generator.xml
<configuration>
+    <generator>
+        <database>
+            <name>org.jooq.meta.extensions.jpa.JPADatabase</name>
+            <properties>
+
+                <!-- A comma separated list of Java packages, that contain your entities -->
+                <property>
+                    <key>packages</key>
+                    <value>com.myapp.models</value>
+                </property>
+
+                <!-- Whether JPA 2.1 AttributeConverters should be auto-mapped to jOOQ Converters.
+                     Custom <forcedType/> configurations will have a higher priority than these auto-mapped converters.
+                     This defaults to true. -->
+                <property>
+                    <key>useAttributeConverters</key>
+                    <value>true</value>
+                </property>
+
+                <!-- The default schema for unqualified objects:
+
+                     - public: all unqualified objects are located in the PUBLIC (upper case) schema
+                     - none: all unqualified objects are located in the default schema (default)
+
+                     This configuration can be overridden with the schema mapping feature -->
+                <property>
+                    <key>unqualifiedSchema</key>
+                    <value>public</value>
+                </property>
+            </properties>
+        </database>
+        <target>
+            <packageName>com.myapp.models.jooq</packageName>
+            <directory>target/generated-test-sources/java</directory>
+        </target>
+    </generator>
+</configuration>
+

Working with transaction manually
final DSLContext dslContext = this.dslContextProvider.get();
+dslContext.transaction((configuration) -> {
+    /* insert/update/delete operations with configuration.dsl() */
+});
+

Exemple
@Entity
+@Table(name = "NEWS")
+public class NewsModel {
+
+    @Id
+    @Column(name = "ID", nullable = false)
+    public String id;
+
+    @Column(name = "TITLE", nullable = false)
+    public String title;
+}
+
public class NewsRepositoryImpl implements NewsRepository {
+
+    private final Conversion conversion;
+    private final Provider<DSLContext> dslContext;
+
+    @Inject
+    public NewsRepositoryImpl(final Conversion conversion,
+                              final Provider<DSLContext> dslContextProvider) {
+        this.conversion = conversion;
+        this.dslContext = dslContext;
+    }
+
+    @Overide
+    @Transactional(Transactional.TxType.SUPPORTS)
+    public List<News> findAll() {
+        final List<NewsModel> newsModelList = dslContextProvider.get()
+            .select()
+            .from(Tables.NEWS)
+            .where(Tables.NEWS.TITLE.isNotNull())
+            .fetchInto(NewsModel.class);
+
+        return conversion.convert(newsModelList, NewsModel.class, News.class);
+    }
+

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/relational-databases/transactional/index.html b/doc/relational-databases/transactional/index.html
new file mode 100644
index 0000000..0e281c6
--- /dev/null
+++ b/doc/relational-databases/transactional/index.html
@@ -0,0 +1,9 @@
+Void Framework – Transactional
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Transactional
It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional (Jakarta) annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
+Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/scheduler/index.html b/doc/scheduler/index.html
index a3c85d0..4a1465e 100644
--- a/doc/scheduler/index.html
+++ b/doc/scheduler/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduler
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduler

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduler

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index a7828a1..076a2a0 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduling a local job
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay defines the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate defines the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay defines the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron defines a CRON-like expression. The default value is empty (disabled).
cronZone defines the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay defines the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate defines the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay defines the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron defines a CRON-like expression. The default value is empty (disabled).
cronZone defines the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
 public final class Ping {
 
     private static final Logger LOGGER = LoggerFactory.getLogger(Ping.class);
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index 1d4e1e2..7f68db8 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -2,10 +2,10 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifact">Void Framework – FreeMarker
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.3.2</version>
+    <version>1.4.0</version>
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/doc/template/index.html b/doc/template/index.html
index 9499286..8c692dd 100644
--- a/doc/template/index.html
+++ b/doc/template/index.html
@@ -1,7 +1,7 @@
 Void Framework – Template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Template

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Template

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/template/using-template/index.html b/doc/template/using-template/index.html
index 9f7df6b..70739fb 100644
--- a/doc/template/using-template/index.html
+++ b/doc/template/using-template/index.html
@@ -2,7 +2,7 @@
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final Temp">Void Framework – Using template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using template
Sooner or later you will need to generate documents (HTML, PDF…). Void Framework provides all the tools you need!

Example
public class TemplateExample {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using template
Sooner or later you will need to generate documents (HTML, PDF…). Void Framework provides all the tools you need!

Example
public class TemplateExample {
 
     private final TemplateRenderer templateRenderer;
 
diff --git a/doc/testing/index.html b/doc/testing/index.html
index afeee28..e8fb927 100644
--- a/doc/testing/index.html
+++ b/doc/testing/index.html
@@ -1,7 +1,7 @@
 Void Framework – Testing
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Testing

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Testing

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index b01a5be..d099b2d 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -2,10 +2,10 @@
 To enable this module, just add following lines to th">Void Framework – JUnit's extension
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
-    <version>1.3.2</version>
+    <version>1.4.0</version>
 </dependency>
 

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
 @ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
diff --git a/doc/vfs/index.html b/doc/vfs/index.html
index 34fc374..a174f82 100644
--- a/doc/vfs/index.html
+++ b/doc/vfs/index.html
@@ -1,7 +1,7 @@
 Void Framework – Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Virtual File Storage

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Virtual File Storage

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/vfs/introduction/index.html b/doc/vfs/introduction/index.html
index a48db88..7ed5394 100644
--- a/doc/vfs/introduction/index.html
+++ b/doc/vfs/introduction/index.html
@@ -1,10 +1,10 @@
 Void Framework – Using Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
-    <version>1.3.2</version>
+    <version>1.4.0</version>
 </dependency>
 

Configuration
Different VirtualFileStorage implementation must be configured in voidframework.vfs namespace. The following configuration key can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
 Note that each implementation can have extra configuration keys.

Example
voidframework {
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index f61cd64..944f6ac 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
@@ -17,7 +17,7 @@
         return Result.ok("Hello World");
     }
 }
-

Defining a route
A route is defined by two components, firstly @WebController defines the prefix that will be applied to all methods of the controller and by the @RequestRoute annotation providing various options. The latter tells the Void Framework that the method is an entry point.
@WebController
This annotation is based on the @Controller annotation. It simply allows the class to be better specified and provides additional options. This annotation can only be used at class level.
The annotation accepts the following parameter:
prefixRoute defines a prefix to be used on all endpoints in the class. By default, the value is empty.
@RequestRoute
This annotation allows you to configure an entry point that will process an incoming request. This annotation can only be used at method level.
The annotation accepts the following parameters:
method defines the HTTP method. The default value is HttpMethod.GET.
route defines a route. Regular expression with named capturing group can be used. The default value is /.
name defines an alias name who can be used with the reverse routing. By default, the value is empty.

Retrieving parameters
To work, a controller will probably need some incoming data. To do this, the @RequestPath, @RequestVariable and @RequestBody annotations make it easy to retrieve information from the request. It is also possible to retrieve information from the Context itself.
@RequestPath
This annotation allows you to extract parameters named in the URL path.
The annotation accepts the following parameter:
value defines the name of the parameter (correlated with the regexp used in the route definition) to extract.
@RequestVariable
This annotation allows you to extract query string value (simple or array) from the URI.
The annotation accepts the following parameter:
value defines the name of the query string value to extract.
@RequestBody
This annotation allows you to retrieve the contents of the request (i.e. from a POST query) as a Java object. If something goes wrong, the extracted value will be null.

Parameter types
It is sure that you will have to retrieve the parameters with their respective type (e.g. int, boolean, …). For this, Void Framework uses the converter mechanism to allow conversion from a String. By default, the following types are handled:
Boolean
Byte
Character
CUID
Double
Float
Integer
Locale
Long
Short
String
UUID

Handle custom types
To handle a new type, you simply have to implement a new converter. For more information, read the Type conversion chapter.

Example
@Singleton
+

What is a route?
A route consists of three elements: a context path, a prefix and a route itself. The first is configured in the application.conf file via the use of the voidframework.web.contextPath key (default value is /) while the other two are endpoint dependent.

Defining a route
A route is defined by two components, firstly @WebController defines the prefix that will be applied to all methods of the controller and by the @RequestRoute annotation providing various options. The latter tells the Void Framework that the method is an entry point.
@WebController
This annotation is based on the @Controller annotation. It simply allows the class to be better specified and provides additional options. This annotation can only be used at class level.
The annotation accepts the following parameter:
prefixRoute defines a prefix to be used on all endpoints in the class. By default, the value is empty.
@RequestRoute
This annotation allows you to configure an entry point that will process an incoming request. This annotation can only be used at method level.
The annotation accepts the following parameters:
method defines the HTTP method. The default value is HttpMethod.GET.
route defines a route. Regular expression with named capturing group can be used. The default value is /.
name defines an alias name who can be used with the reverse routing. By default, the value is empty.

Retrieving parameters
To work, a controller will probably need some incoming data. To do this, the @RequestPath, @RequestVariable and @RequestBody annotations make it easy to retrieve information from the request. It is also possible to retrieve information from the Context itself.
@RequestPath
This annotation allows you to extract parameters named in the URL path.
The annotation accepts the following parameter:
value defines the name of the parameter (correlated with the regexp used in the route definition) to extract.
@RequestVariable
This annotation allows you to extract query string value (simple or array) from the URI.
The annotation accepts the following parameter:
value defines the name of the query string value to extract.
@RequestBody
This annotation allows you to retrieve the contents of the request (i.e. from a POST query) as a Java object. If something goes wrong, the extracted value will be null.

Parameter types
It is sure that you will have to retrieve the parameters with their respective type (e.g. int, boolean, …). For this, Void Framework uses the converter mechanism to allow conversion from a String. By default, the following types are handled:
Boolean
Byte
Character
CUID
Double
Float
Integer
Locale
Long
Short
String
UUID

Handle custom types
To handle a new type, you simply have to implement a new converter. For more information, read the Type conversion chapter.

Example
@Singleton
 @WebController
 public class ExampleController {
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index 883055c..6dcb705 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the">Void Framework – Filters
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
 Note that the use of dependencies direct injection is possible in filters.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
 @Singleton
 @WebController
diff --git a/doc/web/index.html b/doc/web/index.html
index 9672969..39682d8 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Web

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Web

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/render-template/index.html b/doc/web/render-template/index.html
index 1f5d2e8..3e057b3 100644
--- a/doc/web/render-template/index.html
+++ b/doc/web/render-template/index.html
@@ -2,7 +2,7 @@
 Although you can manually use the template engine, in most cases this would not be handy. Howev">Void Framework – Render template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Example
controller/HomeController.java
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Static files
If you need to include static files in your HTML page (e.g. css, javascript, image, …), you can use the urlfor method with the first parameter static_file or static_webjar and the second parameter the path to the file.

Example
controller/HomeController.java
@Singleton
 @WebController
 public class HomeController {
 
@@ -16,6 +16,7 @@
 <html lang="${lang!}">
     <body>
       <h1>${greating}</h1>
+      <img src="${urlfor('static_file', 'img/logo.png')}" alt="image"/>
     </body>
 </html>
 

© 2022 Void Framework

diff --git a/doc/web/security-csrf/index.html b/doc/web/security-csrf/index.html
index e1ea176..1db9b77 100644
--- a/doc/web/security-csrf/index.html
+++ b/doc/web/security-csrf/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is recommended tha">Void Framework – CSRF
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
 It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP.
Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/security-headers/index.html b/doc/web/security-headers/index.html
index 4ef7b3f..f40624c 100644
--- a/doc/web/security-headers/index.html
+++ b/doc/web/security-headers/index.html
@@ -2,7 +2,7 @@
 Configuration The following configuration keys can be used in the configuration">Void Framework – Security headers
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
 You can disable one of the headers by assigning the value null. The header will then not be sent.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/session/index.html b/doc/web/session/index.html
index d56bb06..3e0b241 100644
--- a/doc/web/session/index.html
+++ b/doc/web/session/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the session is not stored on the server side, but on the client side v">Void Framework – Session
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Hibernate ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
 Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie.

Because session is implemented using cookies, there are some implications.The data size is limited to 4 KiB
Only string can be stored

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.

Read value
You can access the session data via the Context. Methods get or getOrDefault can be used.
@Singleton
 @WebController
 public class Controller {
diff --git a/index.xml b/index.xml
index 534849a..1c91b5a 100644
--- a/index.xml
+++ b/index.xml
@@ -1,13 +1,13 @@
 Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
-S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
-S c a N n O C l N a O s s p a R t e h m s o L t c R o e l L e L a a o g i d C s ( a i f o s 3 d s e l n p a t C o f a ) G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G R o e l u L e L a a i o g i d C s ( c a i f o s 3 e d s e l n p a t C o f a ) m G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G R o e l u L e L a a i o g i d C s ( c a i f o s 3 e d s e l n p a t C o f a ) m G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
@@ -24,18 +24,22 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
@@ -43,15 +47,15 @@ priority is used to define when the method will be called in relation to the oth
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.3.2 2022-11-14 Fixed NullPointerException when requested config is null on FreeMarker 1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
-Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003) New WebSocket support New Can configure temporary files location (voidframework.web.server.tempFileLocation) New Mockito annotation support New CUID: a Collision-resistant Unique ID New Add HttpHeaderNames class New Virtual File Storage New No HTTP request timeout (voidframework.web.server.idleTimeout) Fixed The abbreviation of "december" is now correct (scheduler) Fixed "Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.3.2 2022-11-14 Fixed NullPointerException when requested config is null on FreeMarker 1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
-Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003) New WebSocket support New Can configure temporary files location (voidframework.web.server.tempFileLocation) New Mockito annotation support New CUID: a Collision-resistant Unique ID New Add HttpHeaderNames class New Virtual File Storage New No HTTP request timeout (voidframework.web.server.idleTimeout) Fixed The abbreviation of "december" is now correct (scheduler) Fixed "Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.4.0 2022-XX-XX New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.3.2 2022-11-14 Fixed NullPointerException when requested config is null on FreeMarker 1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
+Security Upgrade Jackson Databind version to 2.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.4.0 2022-XX-XX New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.3.2 2022-11-14 Fixed NullPointerException when requested config is null on FreeMarker 1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
+Security Upgrade Jackson Databind version to 2.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
@@ -65,18 +69,20 @@ Define a Job To define a job, simply use the @Scheduled annotation on one or mor
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
-&nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
+&nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
+@Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
+@Transactional The transactional annotation itself defines the scope of a single database transaction.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Upgrading from old versionhttps://voidframework.dev/doc/getting-started/upgrading-from-old-version/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/upgrading-from-old-version/Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.
 1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now required 1.2.0 The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.3.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index b50d0c0..ea9369e 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,8 +1,8 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.3.2

+Release notes1.4.0

+2022-XX-XX
New Guice module prioritisation
New jOOQ module
New Web context path is now customizable (voidframework.web.contextPath)
Improved Deserialization: Unknown enum value to null
Improved Scheduler "run once" mode
Improved Static files/webjars controller: add route name (static_file and static_webjar)
Improved Updated version of all dependencies

1.3.2

 2022-11-14
Fixed NullPointerException when requested config is null on FreeMarker

1.3.1

 2022-11-07
Fixed NullPointerException if header Accept-Language not provided

1.3.0

 2022-11-07
Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003)
New WebSocket support
New Can configure temporary files location (voidframework.web.server.tempFileLocation)
New Mockito annotation support
New CUID: a Collision-resistant Unique ID
New Add HttpHeaderNames class
New Virtual File Storage
New No HTTP request timeout (voidframework.web.server.idleTimeout)
Fixed The abbreviation of "december" is now correct (scheduler)
Fixed "Day of Week" and "Month" can't be zero (Scheduler)
Fixed Redis methods addInList, getFromList and decrement now working correctly
Fixed Force close all InputStream of uploaded files
Fixed Can use template-freemarker without web
Improved Configuration Key/Value from CLI JVM properties (-D flag)
Improved Annotation @RequestVariable can now retrieve array
Improved Move cache annotations to subpackage annotation
Improved Use wrap/unwrap on Memory cache engine
Improved Updated version of all dependencies
Improved Redis parameter connectionTimeout is now a duration
Improved Rename all utility classes
Improved Add new redirection methods on Result
Improved HttpRequestBodyContent::asRaw is now an InputStream
Improved Redis::addInList now return the current list size
Improved ValidationError is now a record

1.2.1

diff --git a/sitemap.xml b/sitemap.xml
index 015acea..e2da9c7 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/template/using-template/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/template/using-template/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/
\ No newline at end of file

From 47cd52bf98e740d6a6d75dc3ceebe170f82eb711 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Mon, 5 Dec 2022 21:46:55 +0000
Subject: [PATCH 31/75] Automated website build

---
 index.xml               | 4 ++--
 releasenotes/index.html | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/index.xml b/index.xml
index 1c91b5a..70ddaac 100644
--- a/index.xml
+++ b/index.xml
@@ -53,8 +53,8 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.4.0 2022-XX-XX New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.3.2 2022-11-14 Fixed NullPointerException when requested config is null on FreeMarker 1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
-Security Upgrade Jackson Databind version to 2.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.4.0 2022-XX-XX New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.3.2 2022-11-14 Fixed NullPointerException when requested config is null on FreeMarker 1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.3.2 2022-11-14 Fixed NullPointerException when requested config is null on FreeMarker 1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
+Security Upgrade Jackson Databind version to 2.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.3.2 2022-11-14 Fixed NullPointerException when requested config is null on FreeMarker 1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
 Security Upgrade Jackson Databind version to 2.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
diff --git a/releasenotes/index.html b/releasenotes/index.html
index ea9369e..3f1b8c4 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,8 +1,8 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
 Release notes
1.4.0

-2022-XX-XX
New Guice module prioritisation
New jOOQ module
New Web context path is now customizable (voidframework.web.contextPath)
Improved Deserialization: Unknown enum value to null
Improved Scheduler "run once" mode
Improved Static files/webjars controller: add route name (static_file and static_webjar)
Improved Updated version of all dependencies

1.3.2

+2022-12-05
New Guice module prioritisation
New jOOQ module
New Web context path is now customizable (voidframework.web.contextPath)
Improved Deserialization: Unknown enum value to null
Improved Scheduler "run once" mode
Improved Static files/webjars controller: add route name (static_file and static_webjar)
Improved Updated version of all dependencies

1.3.2

 2022-11-14
Fixed NullPointerException when requested config is null on FreeMarker

1.3.1

 2022-11-07
Fixed NullPointerException if header Accept-Language not provided

1.3.0

 2022-11-07
Security Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003)
New WebSocket support
New Can configure temporary files location (voidframework.web.server.tempFileLocation)
New Mockito annotation support
New CUID: a Collision-resistant Unique ID
New Add HttpHeaderNames class
New Virtual File Storage
New No HTTP request timeout (voidframework.web.server.idleTimeout)
Fixed The abbreviation of "december" is now correct (scheduler)
Fixed "Day of Week" and "Month" can't be zero (Scheduler)
Fixed Redis methods addInList, getFromList and decrement now working correctly
Fixed Force close all InputStream of uploaded files
Fixed Can use template-freemarker without web
Improved Configuration Key/Value from CLI JVM properties (-D flag)
Improved Annotation @RequestVariable can now retrieve array
Improved Move cache annotations to subpackage annotation
Improved Use wrap/unwrap on Memory cache engine
Improved Updated version of all dependencies
Improved Redis parameter connectionTimeout is now a duration
Improved Rename all utility classes
Improved Add new redirection methods on Result
Improved HttpRequestBodyContent::asRaw is now an InputStream
Improved Redis::addInList now return the current list size
Improved ValidationError is now a record

1.2.1


From 729e0dc7402b5d0795b7cc8369b9311822104f42 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Mon, 5 Dec 2022 21:49:31 +0000
Subject: [PATCH 32/75] Automated website build

---
 doc/scheduler/scheduling-job-cron/index.html | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index 076a2a0..066e525 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -20,6 +20,11 @@
     public void doPingEveryMondayAtMidnightEuropeParis() {
         LOGGER.info("PING!!");
     }
+
+    @Scheduled(initialDelay = 1000)
+    public void doPingOnceAfter1Second() {
+        LOGGER.info("PING!!");
+    }
 }
 

© 2022 Void Framework

 Void Framework is released under the MIT License


From f4767afa66e94c3c543ab2861faf2f7a65c3548e Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Tue, 6 Dec 2022 20:12:12 +0000
Subject: [PATCH 33/75] Automated website build

---
 doc/core/class-scanning/index.html | 7 ++++---
 doc/index.xml                      | 6 ++++--
 index.xml                          | 6 ++++--
 3 files changed, 12 insertions(+), 7 deletions(-)

diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index 42d41b7..e70c29b 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -1,10 +1,11 @@
 Void Framework – Class scanning
+Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes i">Void Framework – Class scanning
 Void Framework
Documentation
    
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
-3 types of elements are recognised during the scan:
Bindable classes (see below)
classes implementing the TypeConverter interface
classes which extend AbstractModule (Guice)

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
-Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@BindClass Indicates that an annotated class is a “Bindable”
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
+3 types of elements are recognised during the scan:
Classes extending AbstractModule (Guice)
Classes annotated with Bindable annotation
Classes implementing defined interface

Guice module
Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.
 
+If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
+Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@BindClass Indicates that an annotated class is a “Bindable”
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Defined interface
The configuration key voidframework.core.bindExtraInterfaces is used to define a set of interfaces for which to bind the found implementations. For example, converters are automatically detected in this way via the TypeConverter interface.

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
     <artifactId>exec-maven-plugin</artifactId>
     <version>3.0.0</version>
diff --git a/doc/index.xml b/doc/index.xml
index 1c893b7..2f2ebe1 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -9,8 +9,10 @@ Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
+Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.
+&nbsp; If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.
+&nbsp; If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
diff --git a/index.xml b/index.xml
index 70ddaac..484d898 100644
--- a/index.xml
+++ b/index.xml
@@ -9,8 +9,10 @@ Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Bindable classes (see below) classes implementing the TypeConverter interface classes which extend AbstractModule (Guice) Bindable @Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan. Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
+Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.
+&nbsp; If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.
+&nbsp; If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example

From e6589e62a2682d75ab2c4b986866da16bc18ae54 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Mon, 2 Jan 2023 09:22:12 +0000
Subject: [PATCH 34/75] Automated website build

---
 doc/advanced/advanced/index.html              |  2 +-
 doc/advanced/index.html                       |  2 +-
 doc/cache/in-memory-cache/index.html          |  4 +-
 doc/cache/index.html                          |  2 +-
 doc/cache/redis-cache/index.html              |  6 +--
 doc/cache/using-cache/index.html              |  2 +-
 doc/core/boot-sequence/index.html             |  2 +-
 doc/core/class-scanning/index.html            |  6 +--
 doc/core/conditional-feature/index.html       | 17 +++++++
 doc/core/configuration/index.html             |  6 +--
 doc/core/index.html                           |  2 +-
 doc/core/lang/index.html                      | 25 ++++++++++
 doc/core/life-cycle/index.html                |  2 +-
 doc/core/type-conversion/index.html           |  2 +-
 doc/getting-started/index.html                |  2 +-
 .../new-application/index.html                |  6 +--
 doc/getting-started/requirements/index.html   |  2 +-
 .../upgrading-from-old-version/index.html     |  2 +-
 doc/i18n/index.html                           |  2 +-
 doc/index.html                                |  2 +-
 doc/index.xml                                 | 44 ++++++++++-------
 .../using-i18n/index.html                     |  4 +-
 doc/nosql-databases/index.html                |  2 +-
 doc/nosql-databases/redis/index.html          |  6 +--
 .../datasource/index.html                     |  6 +--
 doc/relational-databases/index.html           |  2 +-
 .../persistence-hibernate/index.html          |  4 +-
 .../persistence-jooq/index.html               |  4 +-
 .../transactional/index.html                  |  2 +-
 doc/scheduler/index.html                      |  2 +-
 doc/scheduler/scheduling-job-cron/index.html  |  2 +-
 doc/template/freemarker/index.html            |  4 +-
 doc/template/index.html                       |  2 +-
 doc/template/using-template/index.html        |  2 +-
 doc/testing/index.html                        |  2 +-
 doc/testing/junit-extension/index.html        |  4 +-
 doc/vfs/index.html                            |  2 +-
 doc/vfs/introduction/index.html               |  4 +-
 doc/web/controller/index.html                 |  2 +-
 doc/web/filters/index.html                    |  2 +-
 doc/web/index.html                            |  2 +-
 doc/web/render-template/index.html            |  2 +-
 doc/web/security-csrf/index.html              |  2 +-
 doc/web/security-headers/index.html           |  2 +-
 doc/web/session/index.html                    |  2 +-
 index.xml                                     | 48 +++++++++++--------
 releasenotes/index.html                       |  5 +-
 sitemap.xml                                   |  2 +-
 48 files changed, 160 insertions(+), 103 deletions(-)
 create mode 100644 doc/core/conditional-feature/index.html
 create mode 100644 doc/core/lang/index.html

diff --git a/doc/advanced/advanced/index.html b/doc/advanced/advanced/index.html
index e50ec65..fe25bc5 100644
--- a/doc/advanced/advanced/index.html
+++ b/doc/advanced/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – reference.conf
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/advanced/index.html b/doc/advanced/index.html
index 4939d66..93c43bb 100644
--- a/doc/advanced/index.html
+++ b/doc/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – Advanced
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Advanced

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Advanced

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 8c23be5..203ccaf 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,10 +2,10 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.4.0</version>
+    <version>1.5.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/index.html b/doc/cache/index.html
index b622e30..c27a303 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 62b1044..95d089b 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -1,11 +1,11 @@
 Void Framework – Cache engine : Redis
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.5.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.4.0</version>
+    <version>1.5.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index 0b751c1..9bc99ed 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,7 +2,7 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
 Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index 86a0132..2129d5d 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G R o e l u L e L a a i o g i d C s ( c a i f o s 3 e d s e l n p a t C o f a ) m G e y c . t o u r c a h d i l l P . u c c e">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index e70c29b..b19e4a8 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,10 +2,10 @@
 Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes i">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
-3 types of elements are recognised during the scan:
Classes extending AbstractModule (Guice)
Classes annotated with Bindable annotation
Classes implementing defined interface

Guice module
Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+3 types of elements are recognised during the scan:
Classes extending AbstractModule (Guice)
Classes annotated with Bindable annotation
Classes implementing defined interface

Guice module
Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.
 
 If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
-Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@BindClass Indicates that an annotated class is a “Bindable”
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Defined interface
The configuration key voidframework.core.bindExtraInterfaces is used to define a set of interfaces for which to bind the found implementations. For example, converters are automatically detected in this way via the TypeConverter interface.

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
+Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@Bindable 
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Defined interface
The configuration key voidframework.core.bindExtraInterfaces is used to define a set of interfaces for which to bind the found implementations. For example, converters are automatically detected in this way via the TypeConverter interface.

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
     <artifactId>exec-maven-plugin</artifactId>
     <version>3.0.0</version>
diff --git a/doc/core/conditional-feature/index.html b/doc/core/conditional-feature/index.html
new file mode 100644
index 0000000..5db122c
--- /dev/null
+++ b/doc/core/conditional-feature/index.html
@@ -0,0 +1,17 @@
+Void Framework – Conditional feature
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Conditional feature
Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.

@ConditionalFeature
The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
The annotation accepts the following parameter:
value is used to define the implementation of Condition interface to use.
Exemple
@WebController
+@ConditionalFeature(MyCustomCondition.class)
+public final class SampleController {
+}
+

@ConfigurationConditionalFeature
The @ConfigurationConditionalFeature annotation allows a feature to be enabled or disabled based on a value in the configuration, properties, or environment variables.
The annotation accepts the following parameter:
value is used to define the name of the configuration/property/env. variable to be read.
expectedValue is used to define all possible expected values. The default value is {"true", "enabled", "yes", "1"}.
Exemple
@WebController
+@ConfigurationConditionalFeature("feature.name")
+public final class SampleController {
+}
+

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index fcbdb5d..10b4734 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -1,7 +1,7 @@
 Void Framework – Configuration
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
 

Retrieve configuration value from Java
@Service
 public class MyService {
 
@@ -25,7 +25,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.4.0</version>
+  <version>1.5.0</version>
 </dependency>
 
voidframework {
     code {
@@ -60,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.4.0</version>
+  <version>1.5.0</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/core/index.html b/doc/core/index.html
index 24303c9..3041ced 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Core

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Core

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/lang/index.html b/doc/core/lang/index.html
new file mode 100644
index 0000000..05ce199
--- /dev/null
+++ b/doc/core/lang/index.html
@@ -0,0 +1,25 @@
+Void Framework – Lang
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Lang
The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.

CUID
CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
// Random CUID
+final CUID cuid = CUID.randomCUID();
+
+// CUID from String representating a CUID
+final CUID cuid = CUID.fromString("cl9gts1kw00393647w1z4v2tc");
+
+// Check if String contains a valid CUID (implicitly called by "fromString" method)
+final boolean isValid = CUID.isValid("cl9gts1kw00393647w1z4v2tc");
+
 
+CUID works with Jackson serialization/deserialization.

Either
Either represents a value of one or two possible types (a disjoint union). Read the Java file to get more information about available methods.
final Either<String, Integer> either = Either.ofLeft("1337");
+
+final Integer value = either.match(Integer::valueOf, right -> right);
+

TypedMap
TypedMap is a simple hashmap with typed key. Typed means that the type of the value associated to the key is part of the key itself. Read the Java file to get more information about available methods.
final TypedMap.Key<String> STRING_KEY = TypedMap.Key.of("STRING_KEY", String.class)
+final TypedMap typedMap = new TypedMap();
+
+typedMap.put(STRING_KEY, "Hello World");
+

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index c5725ee..6e9ae01 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index c3cc65d..d312615 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index 35c6def..42d74d1 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Getting Started

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Getting Started

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 6066617..ab2d8ec 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,15 +2,15 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.4.0</version>
+    <version>1.5.0</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.4.0</version>
+    <version>1.5.0</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index 8f75c9a..8b4b7ee 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index e92f68a..ffbb10c 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.1.0 ApplicationLa">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index 75f45b8..81f3fa0 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Internationalization

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Internationalization

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index 7501539..61d7dae 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Documentation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Documentation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 2f2ebe1..3fef88e 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,18 +1,22 @@
 Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G R o e l u L e L a a i o g i d C s ( c a i f o s 3 e d s e l n p a t C o f a ) m G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G R o e l u L e L a a i o g i d C s ( c a i f o s 3 e d s e l n p a t C o f a ) m G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.
-&nbsp; If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.
-&nbsp; If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
+Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
+@ConditionalFeature The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
+The annotation accepts the following parameter:
+value is used to define the implementation of Condition interface to use.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
+@ConditionalFeature The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
+The annotation accepts the following parameter:
+value is used to define the implementation of Condition interface to use.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
@@ -26,10 +30,10 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
@@ -39,9 +43,13 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
+// Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
+// Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
@@ -49,10 +57,10 @@ priority is used to define when the method will be called in relation to the oth
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -78,11 +86,11 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 5baf773..e7afdf4 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,10 +1,10 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.4.0</version>
+    <version>1.5.0</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/index.html b/doc/nosql-databases/index.html
index 47863bd..a1fc8b6 100644
--- a/doc/nosql-databases/index.html
+++ b/doc/nosql-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – NoSQL Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

NoSQL Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

NoSQL Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index 8ebe5b2..6f63e78 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -2,15 +2,15 @@
 Installation To enable this module, just add following lines to ">Void Framework – Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
-    <version>1.4.0</version>
+    <version>1.5.0</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
-    <version>1.4.0</version>
+    <version>1.5.0</version>
 </dependency>
 

Example@Service
 public final class ExampleService {
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index f793a10..f523519 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -1,16 +1,16 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.4.0</version>
+    <version>1.5.0</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.4.0</version>
+    <version>1.5.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/relational-databases/index.html b/doc/relational-databases/index.html
index bc3b245..6b9d45d 100644
--- a/doc/relational-databases/index.html
+++ b/doc/relational-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Relational Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Relational Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Relational Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index cfcc417..48ec4eb 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -2,11 +2,11 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.4.0</version>
+    <version>1.5.0</version>
 </dependency>
 

Working with transaction manuallyfinal EntityManager entityManager = this.entityManagerProvider.get();
 final EntityTransaction transaction = entityManager.getTransaction();
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index 15e0b13..ceee479 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -2,10 +2,10 @@
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provid">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-jooq</artifactId>
-    <version>1.4.0</version>
+    <version>1.5.0</version>
 </dependency>
 

Generator
To work, jOOQ needs files generated during the compilation of the project. It is possible to generate the required classes in different ways (scan database, scan entity, …). For more information, please visit the official jOOQ website.
To enable code generation, add & customize the code below.
pom.xml
<build>
     <plugins>
diff --git a/doc/relational-databases/transactional/index.html b/doc/relational-databases/transactional/index.html
index 0e281c6..e833187 100644
--- a/doc/relational-databases/transactional/index.html
+++ b/doc/relational-databases/transactional/index.html
@@ -1,7 +1,7 @@
 Void Framework – Transactional
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Transactional
It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional (Jakarta) annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Transactional
It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional (Jakarta) annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
 Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

© 2022 Void Framework

 Void Framework is released under the MIT License

 
diff --git a/doc/scheduler/index.html b/doc/scheduler/index.html
index 4a1465e..5f0db2c 100644
--- a/doc/scheduler/index.html
+++ b/doc/scheduler/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduler
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduler

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduler

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index 066e525..0fed666 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduling a local job
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay defines the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate defines the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay defines the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron defines a CRON-like expression. The default value is empty (disabled).
cronZone defines the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay defines the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate defines the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay defines the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron defines a CRON-like expression. The default value is empty (disabled).
cronZone defines the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples@BindClass
 public final class Ping {
 
     private static final Logger LOGGER = LoggerFactory.getLogger(Ping.class);
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index 7f68db8..bdb4f0f 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -2,10 +2,10 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifact">Void Framework – FreeMarker
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.4.0</version>
+    <version>1.5.0</version>
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/doc/template/index.html b/doc/template/index.html
index 8c692dd..8e62a1e 100644
--- a/doc/template/index.html
+++ b/doc/template/index.html
@@ -1,7 +1,7 @@
 Void Framework – Template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Template

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Template

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/template/using-template/index.html b/doc/template/using-template/index.html
index 70739fb..80c6346 100644
--- a/doc/template/using-template/index.html
+++ b/doc/template/using-template/index.html
@@ -2,7 +2,7 @@
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final Temp">Void Framework – Using template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using template
Sooner or later you will need to generate documents (HTML, PDF…). Void Framework provides all the tools you need!

Example
public class TemplateExample {
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using template
Sooner or later you will need to generate documents (HTML, PDF…). Void Framework provides all the tools you need!

Example
public class TemplateExample {
 
     private final TemplateRenderer templateRenderer;
 
diff --git a/doc/testing/index.html b/doc/testing/index.html
index e8fb927..21a1284 100644
--- a/doc/testing/index.html
+++ b/doc/testing/index.html
@@ -1,7 +1,7 @@
 Void Framework – Testing
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Testing

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Testing

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index d099b2d..057aae0 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -2,10 +2,10 @@
 To enable this module, just add following lines to th">Void Framework – JUnit's extension
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
-    <version>1.4.0</version>
+    <version>1.5.0</version>
 </dependency>
 

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
 @ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
diff --git a/doc/vfs/index.html b/doc/vfs/index.html
index a174f82..8ada637 100644
--- a/doc/vfs/index.html
+++ b/doc/vfs/index.html
@@ -1,7 +1,7 @@
 Void Framework – Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Virtual File Storage

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Virtual File Storage

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/vfs/introduction/index.html b/doc/vfs/introduction/index.html
index 7ed5394..a741c2f 100644
--- a/doc/vfs/introduction/index.html
+++ b/doc/vfs/introduction/index.html
@@ -1,10 +1,10 @@
 Void Framework – Using Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
-    <version>1.4.0</version>
+    <version>1.5.0</version>
 </dependency>
 

Configuration
Different VirtualFileStorage implementation must be configured in voidframework.vfs namespace. The following configuration key can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
 Note that each implementation can have extra configuration keys.

Examplevoidframework {
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index 944f6ac..9327a45 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index 6dcb705..ebd9de9 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the">Void Framework – Filters
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
 Note that the use of dependencies direct injection is possible in filters.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
 @Singleton
 @WebController
diff --git a/doc/web/index.html b/doc/web/index.html
index 39682d8..da1fddd 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Web

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Web

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/render-template/index.html b/doc/web/render-template/index.html
index 3e057b3..95c5d97 100644
--- a/doc/web/render-template/index.html
+++ b/doc/web/render-template/index.html
@@ -2,7 +2,7 @@
 Although you can manually use the template engine, in most cases this would not be handy. Howev">Void Framework – Render template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Static files
If you need to include static files in your HTML page (e.g. css, javascript, image, …), you can use the urlfor method with the first parameter static_file or static_webjar and the second parameter the path to the file.

Example
controller/HomeController.java
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Static files
If you need to include static files in your HTML page (e.g. css, javascript, image, …), you can use the urlfor method with the first parameter static_file or static_webjar and the second parameter the path to the file.

Example
controller/HomeController.java
@Singleton
 @WebController
 public class HomeController {
 
diff --git a/doc/web/security-csrf/index.html b/doc/web/security-csrf/index.html
index 1db9b77..012175e 100644
--- a/doc/web/security-csrf/index.html
+++ b/doc/web/security-csrf/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is recommended tha">Void Framework – CSRF
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
 It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP.
Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/security-headers/index.html b/doc/web/security-headers/index.html
index f40624c..a78eb94 100644
--- a/doc/web/security-headers/index.html
+++ b/doc/web/security-headers/index.html
@@ -2,7 +2,7 @@
 Configuration The following configuration keys can be used in the configuration">Void Framework – Security headers
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
 You can disable one of the headers by assigning the value null. The header will then not be sent.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/session/index.html b/doc/web/session/index.html
index 3e0b241..69d2790 100644
--- a/doc/web/session/index.html
+++ b/doc/web/session/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the session is not stored on the server side, but on the client side v">Void Framework – Session
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Class scanning
Life cycle
Type conversion
Configuration
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
 Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie.

Because session is implemented using cookies, there are some implications.The data size is limited to 4 KiB
Only string can be stored

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.

Read value
You can access the session data via the Context. Methods get or getOrDefault can be used.
@Singleton
 @WebController
 public class Controller {
diff --git a/index.xml b/index.xml
index 484d898..dfbe558 100644
--- a/index.xml
+++ b/index.xml
@@ -1,18 +1,22 @@
 Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G R o e l u L e L a a i o g i d C s ( c a i f o s 3 e d s e l n p a t C o f a ) m G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G R o e l u L e L a a i o g i d C s ( c a i f o s 3 e d s e l n p a t C o f a ) m G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.
-&nbsp; If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.
-&nbsp; If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
+Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
+@ConditionalFeature The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
+The annotation accepts the following parameter:
+value is used to define the implementation of Condition interface to use.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
+@ConditionalFeature The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
+The annotation accepts the following parameter:
+value is used to define the implementation of Condition interface to use.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Configurationhttps://voidframework.dev/doc/core/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/configuration/Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project&rsquo;s page.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Controllerhttps://voidframework.dev/doc/web/controller/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/controller/Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.
 Example
@@ -26,10 +30,10 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
@@ -39,9 +43,13 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
+// Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
+// Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
@@ -49,15 +57,13 @@ priority is used to define when the method will be called in relation to the oth
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.3.2 2022-11-14 Fixed NullPointerException when requested config is null on FreeMarker 1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
-Security Upgrade Jackson Databind version to 2.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.3.2 2022-11-14 Fixed NullPointerException when requested config is null on FreeMarker 1.3.1 2022-11-07 Fixed NullPointerException if header Accept-Language not provided 1.3.0 2022-11-07
-Security Upgrade Jackson Databind version to 2.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.5.0 XXXX-XX-XX New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.5.0 XXXX-XX-XX New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
@@ -80,11 +86,11 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.4.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 3f1b8c4..ef3958d 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,7 +1,8 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.4.0

+Release notes1.5.0

+XXXX-XX-XX
New CUID validator
New Internationalization for JavaScript
New Conditional feature
Improved Http Result methods now accept charset
Improved Rename bindable annotation from @BindClass to @Bindable
Improved Clean thread data (Transactional)
Improved Updated version of all dependencies

1.4.0

 2022-12-05
New Guice module prioritisation
New jOOQ module
New Web context path is now customizable (voidframework.web.contextPath)
Improved Deserialization: Unknown enum value to null
Improved Scheduler "run once" mode
Improved Static files/webjars controller: add route name (static_file and static_webjar)
Improved Updated version of all dependencies

1.3.2

 2022-11-14
Fixed NullPointerException when requested config is null on FreeMarker

1.3.1

 2022-11-07
Fixed NullPointerException if header Accept-Language not provided

1.3.0

diff --git a/sitemap.xml b/sitemap.xml
index e2da9c7..970d167 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/template/using-template/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/template/using-template/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/
\ No newline at end of file

From f499b486e0af601cfcb51f7552cd54b43380df64 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Mon, 2 Jan 2023 09:24:43 +0000
Subject: [PATCH 35/75] Automated website build

---
 index.xml               | 2 +-
 releasenotes/index.html | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.xml b/index.xml
index dfbe558..946e750 100644
--- a/index.xml
+++ b/index.xml
@@ -63,7 +63,7 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.5.0 XXXX-XX-XX New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.5.0 XXXX-XX-XX New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
diff --git a/releasenotes/index.html b/releasenotes/index.html
index ef3958d..ca3c01c 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,8 +1,8 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
 Release notes
1.5.0

-XXXX-XX-XX
New CUID validator
New Internationalization for JavaScript
New Conditional feature
Improved Http Result methods now accept charset
Improved Rename bindable annotation from @BindClass to @Bindable
Improved Clean thread data (Transactional)
Improved Updated version of all dependencies

1.4.0

+2023-01-02
New CUID validator
New Internationalization for JavaScript
New Conditional feature
Improved Http Result methods now accept charset
Improved Rename bindable annotation from @BindClass to @Bindable
Improved Clean thread data (Transactional)
Improved Updated version of all dependencies

1.4.0

 2022-12-05
New Guice module prioritisation
New jOOQ module
New Web context path is now customizable (voidframework.web.contextPath)
Improved Deserialization: Unknown enum value to null
Improved Scheduler "run once" mode
Improved Static files/webjars controller: add route name (static_file and static_webjar)
Improved Updated version of all dependencies

1.3.2

 2022-11-14
Fixed NullPointerException when requested config is null on FreeMarker

1.3.1

 2022-11-07
Fixed NullPointerException if header Accept-Language not provided

1.3.0


From 7bd9a571a3ca2e8af6cdc8d0779d7b2d6ca2c20e Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Mon, 2 Jan 2023 09:50:27 +0000
Subject: [PATCH 36/75] Automated website build

---
 doc/web/controller/index.html | 34 ++++++++++++++++++++++++++++++++--
 1 file changed, 32 insertions(+), 2 deletions(-)

diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index 9327a45..73c7b3d 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -17,7 +17,7 @@
         return Result.ok("Hello World");
     }
 }
-

What is a route?
A route consists of three elements: a context path, a prefix and a route itself. The first is configured in the application.conf file via the use of the voidframework.web.contextPath key (default value is /) while the other two are endpoint dependent.

Defining a route
A route is defined by two components, firstly @WebController defines the prefix that will be applied to all methods of the controller and by the @RequestRoute annotation providing various options. The latter tells the Void Framework that the method is an entry point.
@WebController
This annotation is based on the @Controller annotation. It simply allows the class to be better specified and provides additional options. This annotation can only be used at class level.
The annotation accepts the following parameter:
prefixRoute defines a prefix to be used on all endpoints in the class. By default, the value is empty.
@RequestRoute
This annotation allows you to configure an entry point that will process an incoming request. This annotation can only be used at method level.
The annotation accepts the following parameters:
method defines the HTTP method. The default value is HttpMethod.GET.
route defines a route. Regular expression with named capturing group can be used. The default value is /.
name defines an alias name who can be used with the reverse routing. By default, the value is empty.

Retrieving parameters
To work, a controller will probably need some incoming data. To do this, the @RequestPath, @RequestVariable and @RequestBody annotations make it easy to retrieve information from the request. It is also possible to retrieve information from the Context itself.
@RequestPath
This annotation allows you to extract parameters named in the URL path.
The annotation accepts the following parameter:
value defines the name of the parameter (correlated with the regexp used in the route definition) to extract.
@RequestVariable
This annotation allows you to extract query string value (simple or array) from the URI.
The annotation accepts the following parameter:
value defines the name of the query string value to extract.
@RequestBody
This annotation allows you to retrieve the contents of the request (i.e. from a POST query) as a Java object. If something goes wrong, the extracted value will be null.

Parameter types
It is sure that you will have to retrieve the parameters with their respective type (e.g. int, boolean, …). For this, Void Framework uses the converter mechanism to allow conversion from a String. By default, the following types are handled:
Boolean
Byte
Character
CUID
Double
Float
Integer
Locale
Long
Short
String
UUID

Handle custom types
To handle a new type, you simply have to implement a new converter. For more information, read the Type conversion chapter.

Example
@Singleton
+

What is a route?
A route consists of three elements: a context path, a prefix and a route itself. The first is configured in the application.conf file via the use of the voidframework.web.contextPath key (default value is /) while the other two are endpoint dependent.

Defining a route
A route is defined by two components, firstly @WebController defines the prefix that will be applied to all methods of the controller and by the @RequestRoute annotation providing various options. The latter tells the Void Framework that the method is an entry point.
@WebController
This annotation is based on the @Controller annotation. It simply allows the class to be better specified and provides additional options. This annotation can only be used at class level.
The annotation accepts the following parameter:
prefixRoute defines a prefix to be used on all endpoints in the class. By default, the value is empty.
@RequestRoute
This annotation allows you to configure an entry point that will process an incoming request. This annotation can only be used at method level.
The annotation accepts the following parameters:
method defines the HTTP method. The default value is HttpMethod.GET.
route defines a route. Regular expression with named capturing group can be used. The default value is /.
name defines an alias name who can be used with the reverse routing. By default, the value is empty.

Retrieving parameters
To work, a controller will probably need some incoming data. To do this, the @RequestPath, @RequestVariable and @RequestBody annotations make it easy to retrieve information from the request. It is also possible to retrieve information from the Context itself.
@RequestPath
This annotation allows you to extract parameters named in the URL path.
The annotation accepts the following parameter:
value defines the name of the parameter (correlated with the regexp used in the route definition) to extract.
@RequestVariable
This annotation allows you to extract query string value (simple or array) from the URI.
The annotation accepts the following parameter:
value defines the name of the query string value to extract.
@RequestBody
This annotation allows you to retrieve the contents of the request (i.e. from a POST query) as a Java object. If something goes wrong, the extracted value will be null.

Example
@Singleton
 @WebController
 public class ExampleController {
 
@@ -26,11 +26,41 @@
         return Result.ok(Yaml.toString(yearArray));
     }
 
-     @RequestRoute(method = HttpMethod.POST, route = "/")
+    @RequestRoute(method = HttpMethod.POST, route = "/")
     public Result retrieveListFromBody(@RequestBody("year") final List<Integer> yearList) {
         return Result.ok(Yaml.toString(yearList));
     }
 }
+

Parameter types
It is sure that you will have to retrieve the parameters with their respective type (e.g. int, boolean, …). For this, Void Framework uses the converter mechanism to allow conversion from a String. By default, the following types are handled:
Boolean
Byte
Character
CUID
Double
Float
Integer
Locale
Long
Short
String
UUID

Handle custom types
To handle a new type, you simply have to implement a new converter. For more information, read the Type conversion chapter.

Static assets & webjars
The abstract class AbstractStaticAssetsController provides the methods needed to serve static files and webjars. It provides the reverse routing names static_file and static_webjar. Static files default folder can be changed via the voidframework.web.baseAssetResourcesDirectory configuration key.
@Singleton
+@WebController
+public class StaticAssetsController extends AbstractStaticAssetsController {
+
+    @Inject
+    public StaticAssetsController(final Config configuration) {
+        super(configuration);
+    }
+}
+
<link rel="stylesheet" href="${urlfor('static_file', 'css/application.css')}">
+

JavaScript internationalization (i18n)
If you need to handle client-side translations via JavaScript, the abstract class AbstractJavaScriptInternationalizationController provides an endpoint to retrieve a helper that you can use directly on the client side. It provides the reverse routing name js_i18n.
@Singleton
+@WebController
+public final class JavaScriptInternationalizationController extends AbstractJavaScriptInternationalizationController {
+
+    @Inject
+    public JavaScriptInternationalizationController(final Internationalization internationalization) {
+
+        super(internationalization);
+
+        // Optional: only retrieve matching translations
+        this.filterKeyPatternList.add("footer.*");
+    }
+}
+
<script src="${urlfor('js_i18n', 'fr')}"></script>
+
+<script>
+i18n.getMessage('msg.key');
+i18n.getMessage('msg.key', 'var');
+i18n.getMessage('msg.key', 'var1', 'var2', /*...*/'varn');
+</script>
 

© 2022 Void Framework

 Void Framework is released under the MIT License

 

From d9df38e9e8502ba121f9c76d9da5008a67c6be3c Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Sat, 7 Jan 2023 14:24:51 +0000
Subject: [PATCH 37/75] Automated website build

---
 index.xml               | 2 +-
 releasenotes/index.html | 5 +++--
 2 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/index.xml b/index.xml
index 946e750..d448aab 100644
--- a/index.xml
+++ b/index.xml
@@ -63,7 +63,7 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "run once" mode Improved Static files/webjars controller: add route name (static_file and static_webjar) Improved Updated version of all dependencies 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
diff --git a/releasenotes/index.html b/releasenotes/index.html
index ca3c01c..1efe0ed 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,7 +1,8 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.5.0

+Release notes
1.5.1

+2023-01-07
Fixed JavaScript i18n reverse routing name (js_i18n)

1.5.0

 2023-01-02
New CUID validator
New Internationalization for JavaScript
New Conditional feature
Improved Http Result methods now accept charset
Improved Rename bindable annotation from @BindClass to @Bindable
Improved Clean thread data (Transactional)
Improved Updated version of all dependencies

1.4.0

 2022-12-05
New Guice module prioritisation
New jOOQ module
New Web context path is now customizable (voidframework.web.contextPath)
Improved Deserialization: Unknown enum value to null
Improved Scheduler "run once" mode
Improved Static files/webjars controller: add route name (static_file and static_webjar)
Improved Updated version of all dependencies

1.3.2

 2022-11-14
Fixed NullPointerException when requested config is null on FreeMarker

1.3.1


From 26c0de61778639a05e4b8520583f67a5bf76a79a Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Sat, 11 Feb 2023 09:28:01 +0000
Subject: [PATCH 38/75] Automated website build

---
 doc/advanced/advanced/index.html              |  2 +-
 doc/advanced/index.html                       |  2 +-
 doc/cache/in-memory-cache/index.html          |  4 +-
 doc/cache/index.html                          |  2 +-
 doc/cache/redis-cache/index.html              |  6 +--
 doc/cache/using-cache/index.html              |  4 +-
 doc/core/boot-sequence/index.html             |  4 +-
 doc/core/class-scanning/index.html            |  2 +-
 doc/core/conditional-feature/index.html       |  2 +-
 doc/core/configuration/index.html             |  6 +--
 doc/core/index.html                           |  2 +-
 doc/core/lang/index.html                      |  2 +-
 doc/core/life-cycle/index.html                |  4 +-
 doc/core/type-conversion/index.html           |  2 +-
 doc/getting-started/index.html                |  2 +-
 .../new-application/index.html                |  6 +--
 doc/getting-started/requirements/index.html   |  2 +-
 .../upgrading-from-old-version/index.html     |  4 +-
 doc/i18n/index.html                           |  2 +-
 doc/index.html                                |  2 +-
 doc/index.xml                                 | 43 +++++++++++-------
 .../using-i18n/index.html                     |  4 +-
 doc/nosql-databases/index.html                |  2 +-
 doc/nosql-databases/redis/index.html          |  6 +--
 .../datasource/index.html                     |  8 ++--
 doc/relational-databases/index.html           |  2 +-
 .../persistence-hibernate/index.html          |  4 +-
 .../persistence-jooq/index.html               |  4 +-
 .../transactional/index.html                  |  2 +-
 doc/scheduler/index.html                      |  2 +-
 doc/scheduler/scheduling-job-cron/index.html  |  2 +-
 doc/template/freemarker/index.html            |  4 +-
 doc/template/index.html                       |  2 +-
 doc/template/using-template/index.html        |  2 +-
 doc/testing/index.html                        |  2 +-
 doc/testing/junit-extension/index.html        |  4 +-
 doc/vfs/index.html                            |  2 +-
 .../{introduction => using-vfs}/index.html    | 10 ++---
 doc/web/controller/index.html                 |  4 +-
 doc/web/filters/index.html                    |  2 +-
 doc/web/index.html                            |  2 +-
 doc/web/render-template/index.html            |  2 +-
 doc/web/security-csrf/index.html              |  2 +-
 doc/web/security-headers/index.html           |  2 +-
 doc/web/session/index.html                    |  2 +-
 doc/web/using-web/index.html                  | 14 ++++++
 index.xml                                     | 45 +++++++++++--------
 releasenotes/index.html                       |  5 ++-
 sitemap.xml                                   |  2 +-
 49 files changed, 141 insertions(+), 108 deletions(-)
 rename doc/vfs/{introduction => using-vfs}/index.html (66%)
 create mode 100644 doc/web/using-web/index.html

diff --git a/doc/advanced/advanced/index.html b/doc/advanced/advanced/index.html
index fe25bc5..9698274 100644
--- a/doc/advanced/advanced/index.html
+++ b/doc/advanced/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – reference.conf

 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/advanced/index.html b/doc/advanced/index.html
index 93c43bb..1bba4bd 100644
--- a/doc/advanced/index.html
+++ b/doc/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – Advanced
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Advanced

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Advanced

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 203ccaf..c173620 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,10 +2,10 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.5.0</version>
+    <version>1.6.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/index.html b/doc/cache/index.html
index c27a303..5822dc7 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 95d089b..c69dac9 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -1,11 +1,11 @@
 Void Framework – Cache engine : Redis
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.5.0</version>
+    <version>1.6.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index 9bc99ed..7dbd056 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,9 +2,9 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
-Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key defines the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
+Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
 
     @CacheResult
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index 2129d5d..e889cae 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -1,8 +1,8 @@
 Void Framework – Boot sequence
+S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c . t o u e y a h d i r c l P . u c l r b">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index b19e4a8..623ce8b 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,7 +2,7 @@
 Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes i">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
 3 types of elements are recognised during the scan:
Classes extending AbstractModule (Guice)
Classes annotated with Bindable annotation
Classes implementing defined interface

Guice module
Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.
 
 If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@Bindable 
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Defined interface
The configuration key voidframework.core.bindExtraInterfaces is used to define a set of interfaces for which to bind the found implementations. For example, converters are automatically detected in this way via the TypeConverter interface.

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
diff --git a/doc/core/conditional-feature/index.html b/doc/core/conditional-feature/index.html
index 5db122c..78c7ea4 100644
--- a/doc/core/conditional-feature/index.html
+++ b/doc/core/conditional-feature/index.html
@@ -2,7 +2,7 @@
 @ConditionalFeature The @ConditionalFeature annotation allows a feature to be enabled or">Void Framework – Conditional feature
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Conditional feature
Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.

@ConditionalFeature
The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
The annotation accepts the following parameter:
value is used to define the implementation of Condition interface to use.
Exemple
@WebController
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Conditional feature
Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.

@ConditionalFeature
The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
The annotation accepts the following parameter:
value is used to define the implementation of Condition interface to use.
Exemple
@WebController
 @ConditionalFeature(MyCustomCondition.class)
 public final class SampleController {
 }
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index 10b4734..cee8797 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -1,7 +1,7 @@
 Void Framework – Configuration
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
 

Retrieve configuration value from Java
@Service
 public class MyService {
 
@@ -25,7 +25,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.5.0</version>
+  <version>1.6.0</version>
 </dependency>
 
voidframework {
     code {
@@ -60,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.5.0</version>
+  <version>1.6.0</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/core/index.html b/doc/core/index.html
index 3041ced..2eded10 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Core

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Core

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/lang/index.html b/doc/core/lang/index.html
index 05ce199..987fea3 100644
--- a/doc/core/lang/index.html
+++ b/doc/core/lang/index.html
@@ -2,7 +2,7 @@
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get mor">Void Framework – Lang
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Lang
The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.

CUID
CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
// Random CUID
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Lang
The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.

CUID
CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.// Random CUID
 final CUID cuid = CUID.randomCUID();
 
 // CUID from String representating a CUID
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index 6e9ae01..891e00c 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,8 +2,8 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
-It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time (duration or milliseconds) to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
 
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index d312615..9be2f7f 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index 42d74d1..08b7095 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Getting Started

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Getting Started

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index ab2d8ec..417c81c 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,15 +2,15 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.5.0</version>
+    <version>1.6.0</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.5.0</version>
+    <version>1.6.0</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index 8b4b7ee..9ce3665 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index ffbb10c..8688310 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -1,8 +1,8 @@
 Void Framework – Upgrading from old version
+1.0.0 Initial relea">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.0.0
Initial release

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

1.6.0
Configuration keys voidframework.web.server.listenHost and voidframework.web.server.listenPort have been renamed to voidframework.web.server.http.listenHost and voidframework.web.server.http.listenPort

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index 81f3fa0..80d4d75 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Internationalization

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Internationalization

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index 61d7dae..3732cac 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Documentation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Documentation

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 3fef88e..a200563 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,13 +1,13 @@
 Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
-S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G R o e l u L e L a a i o g i d C s ( c a i f o s 3 e d s e l n p a t C o f a ) m G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
-S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G R o e l u L e L a a i o g i d C s ( c a i f o s 3 e d s e l n p a t C o f a ) m G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -30,10 +30,10 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
@@ -43,9 +43,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -57,10 +57,10 @@ priority is used to define when the method will be called in relation to the oth
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -82,15 +82,24 @@ voidframework.web.securityHeaders.contentTypeOptions the value for the header &a
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Upgrading from old versionhttps://voidframework.dev/doc/getting-started/upgrading-from-old-version/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/upgrading-from-old-version/Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.
+1.0.0 Initial release
 1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now required 1.2.0 The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
-Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+Base
+voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+Base
+voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index e7afdf4..bec1f8f 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,10 +1,10 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.5.0</version>
+    <version>1.6.0</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/index.html b/doc/nosql-databases/index.html
index a1fc8b6..e5c84c8 100644
--- a/doc/nosql-databases/index.html
+++ b/doc/nosql-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – NoSQL Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

NoSQL Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

NoSQL Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index 6f63e78..304fda0 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -2,15 +2,15 @@
 Installation To enable this module, just add following lines to ">Void Framework – Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
-    <version>1.5.0</version>
+    <version>1.6.0</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
-    <version>1.5.0</version>
+    <version>1.6.0</version>
 </dependency>
 

Example
@Service
 public final class ExampleService {
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index f523519..3881739 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -1,16 +1,16 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.5.0</version>
+    <version>1.6.0</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.5.0</version>
+    <version>1.6.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
@@ -18,7 +18,7 @@
 voidframework.datasource.default.username the username to be provided durint the authentication step.
required
 voidframework.datasource.default.password the password to be provided durint the authentication step.
optional
 C3P0 only
-voidframework.datasource.default.statementCacheNumDeferredCloseThreads defines the number of threads to track when Connections are in use, and only destroy Statements when their parent Connections are not otherwise in use.
optional
+voidframework.datasource.default.statementCacheNumDeferredCloseThreads the number of threads to track when Connections are in use, and only destroy Statements when their parent Connections are not otherwise in use.
optional
 HikariCP only
 voidframework.datasource.default.cachePrepStmts enable or disable the prepared statements cache.
optional
 voidframework.datasource.default.prepStmtCacheSize the number of prepared statements cache to keep in the cache.
optional
diff --git a/doc/relational-databases/index.html b/doc/relational-databases/index.html
index 6b9d45d..e1403f7 100644
--- a/doc/relational-databases/index.html
+++ b/doc/relational-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Relational Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Relational Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Relational Databases

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index 48ec4eb..325dc81 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -2,11 +2,11 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.5.0</version>
+    <version>1.6.0</version>
 </dependency>
 

Working with transaction manually
final EntityManager entityManager = this.entityManagerProvider.get();
 final EntityTransaction transaction = entityManager.getTransaction();
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index ceee479..47eba04 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -2,10 +2,10 @@
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provid">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-jooq</artifactId>
-    <version>1.5.0</version>
+    <version>1.6.0</version>
 </dependency>
 

Generator
To work, jOOQ needs files generated during the compilation of the project. It is possible to generate the required classes in different ways (scan database, scan entity, …). For more information, please visit the official jOOQ website.
To enable code generation, add & customize the code below.
pom.xml
<build>
     <plugins>
diff --git a/doc/relational-databases/transactional/index.html b/doc/relational-databases/transactional/index.html
index e833187..1b054bc 100644
--- a/doc/relational-databases/transactional/index.html
+++ b/doc/relational-databases/transactional/index.html
@@ -1,7 +1,7 @@
 Void Framework – Transactional
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Transactional
It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional (Jakarta) annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Transactional
It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional (Jakarta) annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
 Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

© 2022 Void Framework

 Void Framework is released under the MIT License

 
diff --git a/doc/scheduler/index.html b/doc/scheduler/index.html
index 5f0db2c..0ef0ff3 100644
--- a/doc/scheduler/index.html
+++ b/doc/scheduler/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduler
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduler

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduler

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index 0fed666..dd96623 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduling a local job
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay defines the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate defines the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay defines the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron defines a CRON-like expression. The default value is empty (disabled).
cronZone defines the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron a CRON-like expression. The default value is empty (disabled).
cronZone the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
 public final class Ping {
 
     private static final Logger LOGGER = LoggerFactory.getLogger(Ping.class);
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index bdb4f0f..2eb76ce 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -2,10 +2,10 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifact">Void Framework – FreeMarker
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.5.0</version>
+    <version>1.6.0</version>
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/doc/template/index.html b/doc/template/index.html
index 8e62a1e..da2142e 100644
--- a/doc/template/index.html
+++ b/doc/template/index.html
@@ -1,7 +1,7 @@
 Void Framework – Template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Template

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Template

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/template/using-template/index.html b/doc/template/using-template/index.html
index 80c6346..d9d6bdc 100644
--- a/doc/template/using-template/index.html
+++ b/doc/template/using-template/index.html
@@ -2,7 +2,7 @@
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final Temp">Void Framework – Using template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using template
Sooner or later you will need to generate documents (HTML, PDF…). Void Framework provides all the tools you need!

Example
public class TemplateExample {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using template
Sooner or later you will need to generate documents (HTML, PDF…). Void Framework provides all the tools you need!

Example
public class TemplateExample {
 
     private final TemplateRenderer templateRenderer;
 
diff --git a/doc/testing/index.html b/doc/testing/index.html
index 21a1284..87fb580 100644
--- a/doc/testing/index.html
+++ b/doc/testing/index.html
@@ -1,7 +1,7 @@
 Void Framework – Testing
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Testing

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Testing

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index 057aae0..1fd1d29 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -2,10 +2,10 @@
 To enable this module, just add following lines to th">Void Framework – JUnit's extension
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
-    <version>1.5.0</version>
+    <version>1.6.0</version>
 </dependency>
 

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
 @ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
diff --git a/doc/vfs/index.html b/doc/vfs/index.html
index 8ada637..dd6800a 100644
--- a/doc/vfs/index.html
+++ b/doc/vfs/index.html
@@ -1,7 +1,7 @@
 Void Framework – Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Virtual File Storage

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Virtual File Storage

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/vfs/introduction/index.html b/doc/vfs/using-vfs/index.html
similarity index 66%
rename from doc/vfs/introduction/index.html
rename to doc/vfs/using-vfs/index.html
index a741c2f..b715e40 100644
--- a/doc/vfs/introduction/index.html
+++ b/doc/vfs/using-vfs/index.html
@@ -1,12 +1,12 @@
-Void Framework – Using Virtual File Storage
+Void Framework – Using Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
-    <version>1.5.0</version>
+    <version>1.6.0</version>
 </dependency>
-

Configuration
Different VirtualFileStorage implementation must be configured in voidframework.vfs namespace. The following configuration key can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation. 
+

Configuration
Different VirtualFileStorage implementations must be configured in voidframework.vfs namespace. The following configuration keys can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
 Note that each implementation can have extra configuration keys.

Example
voidframework {
     vfs {
 
@@ -38,7 +38,7 @@
 
     @Inject
     public UploadController(final VirtualFileStorage vfs) {
-
+        
         this.vfs = vfs;
     }
 
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index 73c7b3d..b3dbad7 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
@@ -17,7 +17,7 @@
         return Result.ok("Hello World");
     }
 }
-

What is a route?
A route consists of three elements: a context path, a prefix and a route itself. The first is configured in the application.conf file via the use of the voidframework.web.contextPath key (default value is /) while the other two are endpoint dependent.

Defining a route
A route is defined by two components, firstly @WebController defines the prefix that will be applied to all methods of the controller and by the @RequestRoute annotation providing various options. The latter tells the Void Framework that the method is an entry point.
@WebController
This annotation is based on the @Controller annotation. It simply allows the class to be better specified and provides additional options. This annotation can only be used at class level.
The annotation accepts the following parameter:
prefixRoute defines a prefix to be used on all endpoints in the class. By default, the value is empty.
@RequestRoute
This annotation allows you to configure an entry point that will process an incoming request. This annotation can only be used at method level.
The annotation accepts the following parameters:
method defines the HTTP method. The default value is HttpMethod.GET.
route defines a route. Regular expression with named capturing group can be used. The default value is /.
name defines an alias name who can be used with the reverse routing. By default, the value is empty.

Retrieving parameters
To work, a controller will probably need some incoming data. To do this, the @RequestPath, @RequestVariable and @RequestBody annotations make it easy to retrieve information from the request. It is also possible to retrieve information from the Context itself.
@RequestPath
This annotation allows you to extract parameters named in the URL path.
The annotation accepts the following parameter:
value defines the name of the parameter (correlated with the regexp used in the route definition) to extract.
@RequestVariable
This annotation allows you to extract query string value (simple or array) from the URI.
The annotation accepts the following parameter:
value defines the name of the query string value to extract.
@RequestBody
This annotation allows you to retrieve the contents of the request (i.e. from a POST query) as a Java object. If something goes wrong, the extracted value will be null.

Example
@Singleton
+

What is a route?
A route consists of three elements: a context path, a prefix and a route itself. The first is configured in the application.conf file via the use of the voidframework.web.contextPath key (default value is /) while the other two are endpoint dependent.

Defining a route
A route is defined by two components, firstly @WebController defines the prefix that will be applied to all methods of the controller and by the @RequestRoute annotation providing various options. The latter tells the Void Framework that the method is an entry point.
@WebController
This annotation is based on the @Controller annotation. It simply allows the class to be better specified and provides additional options. This annotation can only be used at class level.
The annotation accepts the following parameter:
prefixRoute a prefix to use on all endpoints in the class. By default, the value is empty.
@RequestRoute
This annotation allows you to configure an entry point that will process an incoming request. This annotation can only be used at method level.
The annotation accepts the following parameters:
method the HTTP method. The default value is HttpMethod.GET.
route the route. Regular expression with named capturing group can be used. The default value is /.
name an alias name who can be used with the reverse routing. By default, the value is empty.

Retrieving parameters
To work, a controller will probably need some incoming data. To do this, the @RequestPath, @RequestVariable and @RequestBody annotations make it easy to retrieve information from the request. It is also possible to retrieve information from the Context itself.
@RequestPath
This annotation allows you to extract parameters named in the URL path.
The annotation accepts the following parameter:
value the name of the parameter (correlated with the regexp used in the route definition) to extract.
@RequestVariable
This annotation allows you to extract query string value (simple or array) from the URI.
The annotation accepts the following parameter:
value the name of the query string value to extract.
fallback the value to use as fallback.
@RequestBody
This annotation allows you to retrieve the contents of the request (i.e. from a POST query) as a Java object. If something goes wrong, the extracted value will be null.

Example
@Singleton
 @WebController
 public class ExampleController {
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index ebd9de9..fffea3b 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the">Void Framework – Filters
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
 Note that the use of dependencies direct injection is possible in filters.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
 @Singleton
 @WebController
diff --git a/doc/web/index.html b/doc/web/index.html
index da1fddd..f86e551 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Web

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Web

© 2022 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/render-template/index.html b/doc/web/render-template/index.html
index 95c5d97..b096577 100644
--- a/doc/web/render-template/index.html
+++ b/doc/web/render-template/index.html
@@ -2,7 +2,7 @@
 Although you can manually use the template engine, in most cases this would not be handy. Howev">Void Framework – Render template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Static files
If you need to include static files in your HTML page (e.g. css, javascript, image, …), you can use the urlfor method with the first parameter static_file or static_webjar and the second parameter the path to the file.

Example
controller/HomeController.java
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Static files
If you need to include static files in your HTML page (e.g. css, javascript, image, …), you can use the urlfor method with the first parameter static_file or static_webjar and the second parameter the path to the file.

Example
controller/HomeController.java
@Singleton
 @WebController
 public class HomeController {
 
diff --git a/doc/web/security-csrf/index.html b/doc/web/security-csrf/index.html
index 012175e..5f51721 100644
--- a/doc/web/security-csrf/index.html
+++ b/doc/web/security-csrf/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is recommended tha">Void Framework – CSRF
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
 It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP.
Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/security-headers/index.html b/doc/web/security-headers/index.html
index a78eb94..38c79c1 100644
--- a/doc/web/security-headers/index.html
+++ b/doc/web/security-headers/index.html
@@ -2,7 +2,7 @@
 Configuration The following configuration keys can be used in the configuration">Void Framework – Security headers
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
 You can disable one of the headers by assigning the value null. The header will then not be sent.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/session/index.html b/doc/web/session/index.html
index 69d2790..e3e1ba0 100644
--- a/doc/web/session/index.html
+++ b/doc/web/session/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the session is not stored on the server side, but on the client side v">Void Framework – Session
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
 Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie.

Because session is implemented using cookies, there are some implications.The data size is limited to 4 KiB
Only string can be stored

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.

Read value
You can access the session data via the Context. Methods get or getOrDefault can be used.
@Singleton
 @WebController
 public class Controller {
diff --git a/doc/web/using-web/index.html b/doc/web/using-web/index.html
new file mode 100644
index 0000000..bfa5cc1
--- /dev/null
+++ b/doc/web/using-web/index.html
@@ -0,0 +1,14 @@
+Void Framework – Using Web
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+    <groupId>dev.voidframework</groupId>
+    <artifactId>voidframework-web</artifactId>
+    <version>1.6.0</version>
+</dependency>
+

Configuration
The following configuration keys can be used.
Base
voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly. The default value is 15 seconds.
voidframework.web.errorHandler the implementation of the error handler to use in case of http error. The default value is dev.voidframework.web.http.errorhandler.DefaultErrorHandler.
voidframework.web.contextPath the default context path root. The default value is /.
voidframework.web.routes a list of routing definition classes (must implement the interface AppRoutesDefinition). The default value is [].
voidframework.web.globalFilters a list of routing global filter classes (must implement the interface Filter). The default value is [].
voidframework.web.baseAssetResourcesDirectory the default location of static files in the “resources” directory. The default value is static.
Server
voidframework.web.server.idleTimeout the time without any request to wait before the connection is closed. The default value is 30 seconds.
voidframework.web.server.extraWebServerConfiguration the implementation of the interface ExtraWebServerConfiguration to apply a custom configuration to the Undertow web server. The default value is null.
voidframework.web.server.ioThreads the number of I/O threads. If not specified (value = null or 0), Math.max(Runtime.getRuntime().availableProcessors(), 2) value will be used. The default value is null.
voidframework.web.server.workerThreads the number of Worker threads. If not specified (value = null or 0), ioThreadsNumber * 8 value will be used. The default value is null.
voidframework.web.server.maxBodySize the max body content size. The default value is 1 MiB.
voidframework.web.server.fileSizeThreshold the maximum size allowed in memory before the uploaded file was stored on the disk rather than in memory. The default value is 256 KiB.
voidframework.web.server.tempFileLocation the location where temporary files will be stored. The default value is null (default Java temporary folder).
HTTP
voidframework.web.server.http.listenHost the interface on which the server will listen for non-secure HTTP requests. The default value is 127.0.0.1.
voidframework.web.server.http.listenPort the port on which the server will listen for non-secure HTTP requests. The default value is 9000.
HTTPS
voidframework.web.server.https.listenHost the interface on which the server will listen for HTTPS requests. The default value is 127.0.0.1.
voidframework.web.server.https.listenPort the port on which the server will listen for HTTPS requests. The default value is 9001.
voidframework.web.server.https.ssl.protocols the protocols to use. The default value is ["TLSv1.2", "TLSv1.3"].
voidframework.web.server.https.ssl.ciphers the allowed ciphers. If list is empty, all ciphers will be allowed. The default value is [].
voidframework.web.server.https.ssl.keyStorePath the path where is located the key store. Could be a “resources” path, a URL or a simple path. The default value is null.
voidframework.web.server.https.ssl.keyStoreType the type of the key store. The default value is JKS.
voidframework.web.server.https.ssl.keyStorePassword the password to use to open the key store. The default value is null.
voidframework.web.server.https.ssl.keyAlias the alias of the key to use. If “null” the key will be choosen automatically. The default value is null.
voidframework.web.server.https.ssl.keyPassword the key password. The default value is ${voidframework.web.server.https.ssl.keyStorePassword}.
Language
voidframework.web.language.availableLanguages the available languages. The default value is ["en", "fr"].
voidframework.web.language.cookieName the name of the cookie containing the current language. The default value is VOID_LANG.
voidframework.web.language.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.language.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Flash messages
voidframework.web.flashMessages.cookieName the name of the cookie containing the current flash messages. The default value is VOID_FLASH.
voidframework.web.flashMessages.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.flashMessages.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Session
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.
CSRF
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.
Security headers
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.

© 2022 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/index.xml b/index.xml
index d448aab..f383271 100644
--- a/index.xml
+++ b/index.xml
@@ -1,13 +1,13 @@
 Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
-S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G R o e l u L e L a a i o g i d C s ( c a i f o s 3 e d s e l n p a t C o f a ) m G e y c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
-S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G R o e l u L e L a a i o g i d C s ( c a i f o s 3 e d s e l n p a t C o f a ) m G e y c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -30,10 +30,10 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
@@ -43,9 +43,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -57,13 +57,13 @@ priority is used to define when the method will be called in relation to the oth
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.4.0 2022-12-05 New Guice module prioritisation New jOOQ module New Web context path is now customizable (voidframework.web.contextPath) Improved Deserialization: Unknown enum value to null Improved Scheduler "Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.0 2023-xx-xx New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.0 2023-xx-xx New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
@@ -82,15 +82,24 @@ voidframework.web.securityHeaders.contentTypeOptions the value for the header &a
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Type conversionhttps://voidframework.dev/doc/core/type-conversion/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/type-conversion/Type conversion is a mechanism for converting data from one type to another. For example, convert the string &ldquo;1234&rdquo; to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.
 Using conversion The conversion is used via the Conversion service which is accessible via direct injection.Upgrading from old versionhttps://voidframework.dev/doc/getting-started/upgrading-from-old-version/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/upgrading-from-old-version/Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.
+1.0.0 Initial release
 1.1.0 ApplicationLauncher has been renamed to VoidApplication The setting key voidframework.web.session.signatureKey is now required 1.2.0 The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
-Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/introduction/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.5.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementation must be configured in voidframework.
\ No newline at end of file
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+Base
+voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+Base
+voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 1efe0ed..363a8d9 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,7 +1,8 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.5.1

+Release notes1.6.0

+2023-xx-xx
New Web module can now respond to requests securely via HTTPS
New NotInstance validation constraint
New Utility class DurationUtils
Improved Graceful stop timeout is now a duration (with time unit)
Improved Commercial at "@" constant now available in CharConstants and StringConstants classes
Improved Annotation RequestVariable can now use fallback value
Improved Updated version of all dependencies

1.5.1

 2023-01-07
Fixed JavaScript i18n reverse routing name (js_i18n)

1.5.0

 2023-01-02
New CUID validator
New Internationalization for JavaScript
New Conditional feature
Improved Http Result methods now accept charset
Improved Rename bindable annotation from @BindClass to @Bindable
Improved Clean thread data (Transactional)
Improved Updated version of all dependencies

1.4.0

 2022-12-05
New Guice module prioritisation
New jOOQ module
New Web context path is now customizable (voidframework.web.contextPath)
Improved Deserialization: Unknown enum value to null
Improved Scheduler "run once" mode
Improved Static files/webjars controller: add route name (static_file and static_webjar)
Improved Updated version of all dependencies

1.3.2

diff --git a/sitemap.xml b/sitemap.xml
index 970d167..c9578b1 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/template/using-template/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/doc/vfs/introduction/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/template/using-template/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/
\ No newline at end of file

From 9b1638a8c2687bc1079e07d4a1a4e4f1b8eeafe3 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Sat, 11 Feb 2023 09:29:44 +0000
Subject: [PATCH 39/75] Automated website build

---
 index.xml               | 2 +-
 releasenotes/index.html | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.xml b/index.xml
index f383271..4ce851f 100644
--- a/index.xml
+++ b/index.xml
@@ -63,7 +63,7 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.0 2023-xx-xx New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.0 2023-xx-xx New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.0 2023-02-11 New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.0 2023-02-11 New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 363a8d9..477ef52 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,8 +1,8 @@
-Void Framework – Release notes

+Void Framework – Release notes
 Void Framework
Documentation
    
 Release notes
1.6.0

-2023-xx-xx
New Web module can now respond to requests securely via HTTPS
New NotInstance validation constraint
New Utility class DurationUtils
Improved Graceful stop timeout is now a duration (with time unit)
Improved Commercial at "@" constant now available in CharConstants and StringConstants classes
Improved Annotation RequestVariable can now use fallback value
Improved Updated version of all dependencies

1.5.1

+2023-02-11
New Web module can now respond to requests securely via HTTPS
New NotInstance validation constraint
New Utility class DurationUtils
Improved Graceful stop timeout is now a duration (with time unit)
Improved Commercial at "@" constant now available in CharConstants and StringConstants classes
Improved Annotation RequestVariable can now use fallback value
Improved Updated version of all dependencies

1.5.1

 2023-01-07
Fixed JavaScript i18n reverse routing name (js_i18n)

1.5.0

 2023-01-02
New CUID validator
New Internationalization for JavaScript
New Conditional feature
Improved Http Result methods now accept charset
Improved Rename bindable annotation from @BindClass to @Bindable
Improved Clean thread data (Transactional)
Improved Updated version of all dependencies

1.4.0

 2022-12-05
New Guice module prioritisation
New jOOQ module
New Web context path is now customizable (voidframework.web.contextPath)
Improved Deserialization: Unknown enum value to null
Improved Scheduler "run once" mode
Improved Static files/webjars controller: add route name (static_file and static_webjar)
Improved Updated version of all dependencies

1.3.2


From f21d6bb83856ec52f9c331b091b2af69c9bd6cfd Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Sat, 11 Feb 2023 09:31:54 +0000
Subject: [PATCH 40/75] Automated website build

---
 doc/advanced/advanced/index.html                          | 2 +-
 doc/advanced/index.html                                   | 2 +-
 doc/cache/in-memory-cache/index.html                      | 2 +-
 doc/cache/index.html                                      | 2 +-
 doc/cache/redis-cache/index.html                          | 2 +-
 doc/cache/using-cache/index.html                          | 2 +-
 doc/core/boot-sequence/index.html                         | 2 +-
 doc/core/class-scanning/index.html                        | 2 +-
 doc/core/conditional-feature/index.html                   | 2 +-
 doc/core/configuration/index.html                         | 2 +-
 doc/core/index.html                                       | 2 +-
 doc/core/lang/index.html                                  | 2 +-
 doc/core/life-cycle/index.html                            | 2 +-
 doc/core/type-conversion/index.html                       | 2 +-
 doc/getting-started/index.html                            | 2 +-
 doc/getting-started/new-application/index.html            | 2 +-
 doc/getting-started/requirements/index.html               | 2 +-
 doc/getting-started/upgrading-from-old-version/index.html | 2 +-
 doc/i18n/index.html                                       | 2 +-
 doc/index.html                                            | 2 +-
 doc/internationalization/using-i18n/index.html            | 2 +-
 doc/nosql-databases/index.html                            | 2 +-
 doc/nosql-databases/redis/index.html                      | 2 +-
 doc/relational-databases/datasource/index.html            | 2 +-
 doc/relational-databases/index.html                       | 2 +-
 doc/relational-databases/persistence-hibernate/index.html | 2 +-
 doc/relational-databases/persistence-jooq/index.html      | 2 +-
 doc/relational-databases/transactional/index.html         | 2 +-
 doc/scheduler/index.html                                  | 2 +-
 doc/scheduler/scheduling-job-cron/index.html              | 2 +-
 doc/template/freemarker/index.html                        | 2 +-
 doc/template/index.html                                   | 2 +-
 doc/template/using-template/index.html                    | 2 +-
 doc/testing/index.html                                    | 2 +-
 doc/testing/junit-extension/index.html                    | 2 +-
 doc/vfs/index.html                                        | 2 +-
 doc/vfs/using-vfs/index.html                              | 2 +-
 doc/web/controller/index.html                             | 2 +-
 doc/web/filters/index.html                                | 2 +-
 doc/web/index.html                                        | 2 +-
 doc/web/render-template/index.html                        | 2 +-
 doc/web/security-csrf/index.html                          | 2 +-
 doc/web/security-headers/index.html                       | 2 +-
 doc/web/session/index.html                                | 2 +-
 doc/web/using-web/index.html                              | 2 +-
 index.html                                                | 2 +-
 releasenotes/index.html                                   | 2 +-
 47 files changed, 47 insertions(+), 47 deletions(-)

diff --git a/doc/advanced/advanced/index.html b/doc/advanced/advanced/index.html
index 9698274..16aaa0a 100644
--- a/doc/advanced/advanced/index.html
+++ b/doc/advanced/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – reference.conf

 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/advanced/index.html b/doc/advanced/index.html
index 1bba4bd..fbaeb22 100644
--- a/doc/advanced/index.html
+++ b/doc/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – Advanced
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Advanced

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Advanced

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index c173620..486e0e5 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -7,7 +7,7 @@
     <artifactId>voidframework-cache</artifactId>
     <version>1.6.0</version>
 </dependency>
-
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022 Void Framework

+
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/index.html b/doc/cache/index.html
index 5822dc7..9edc2d2 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index c69dac9..3392cf9 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -7,7 +7,7 @@
     <artifactId>voidframework-cache-redis</artifactId>
     <version>1.6.0</version>
 </dependency>
-
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022 Void Framework

+
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index 7dbd056..cdee189 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -25,7 +25,7 @@
         cacheEngine.set("key", "value");
     }
 }
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index e889cae..2758d28 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c . t o u e y a h d i r c l P . u c l r b">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index 623ce8b..6e2d6cc 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -25,7 +25,7 @@
         </execution>
     </executions>
 </plugin>
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/conditional-feature/index.html b/doc/core/conditional-feature/index.html
index 78c7ea4..74142c0 100644
--- a/doc/core/conditional-feature/index.html
+++ b/doc/core/conditional-feature/index.html
@@ -10,7 +10,7 @@
 @ConfigurationConditionalFeature("feature.name")
 public final class SampleController {
 }
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index cee8797..0aebe40 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -90,7 +90,7 @@
         }
     }
 }
-

Creating a Remote configuration provider
Creating a new provider is very easy. Simply implement the RemoteConfigurationProvider interface or extend the AbstractRemoteConfigurationProvider abstract class.

© 2022 Void Framework

+

Creating a Remote configuration provider
Creating a new provider is very easy. Simply implement the RemoteConfigurationProvider interface or extend the AbstractRemoteConfigurationProvider abstract class.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/index.html b/doc/core/index.html
index 2eded10..eb3aa01 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Core

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Core

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/lang/index.html b/doc/core/lang/index.html
index 987fea3..23063e4 100644
--- a/doc/core/lang/index.html
+++ b/doc/core/lang/index.html
@@ -18,7 +18,7 @@
 final TypedMap typedMap = new TypedMap();
 
 typedMap.put(STRING_KEY, "Hello World");
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index 891e00c..d22d540 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -23,7 +23,7 @@
     public void onStop() {
     }
 }
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index 9be2f7f..b710d8e 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -30,7 +30,7 @@
     }
 }
 
 
-A type converter must be stateless, simple and thread safe. Even if direct injection is available, it is not recommended to perform too complex, blocking or slow operation.

© 2022 Void Framework

+A type converter must be stateless, simple and thread safe. Even if direct injection is available, it is not recommended to perform too complex, blocking or slow operation.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index 08b7095..81c7adc 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Getting Started

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Getting Started

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 417c81c..4006c3a 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -42,7 +42,7 @@
 }
 

Application launcher
To start the application, you have to instantiate ApplicationLauncher and then call the launch method.
final VoidApplication app = new VoidApplication();
 app.launch();
-

Run your application
You can now start your application and go to the URL http://127.0.0.1:9000 in your favourite web browser.

© 2022 Void Framework

+

Run your application
You can now start your application and go to the URL http://127.0.0.1:9000 in your favourite web browser.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index 9ce3665..1c42561 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -12,7 +12,7 @@
 Java version: 17.0.2, vendor: Oracle Corporation, runtime: C:\Users\user\.jdks\openjdk-17.0.2
 Default locale: en_US, platform encoding: UTF-8
 OS name: "windows 11", version: "10.0", arch: "amd64", family: "windows"
-
If Maven is not available on your computer, you can get Maven from Apache Maven Project.

© 2022 Void Framework

+
If Maven is not available on your computer, you can get Maven from Apache Maven Project.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index 8688310..f0f4284 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.0.0 Initial relea">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.0.0
Initial release

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

1.6.0
Configuration keys voidframework.web.server.listenHost and voidframework.web.server.listenPort have been renamed to voidframework.web.server.http.listenHost and voidframework.web.server.http.listenPort

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.0.0
Initial release

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

1.6.0
Configuration keys voidframework.web.server.listenHost and voidframework.web.server.listenPort have been renamed to voidframework.web.server.http.listenHost and voidframework.web.server.http.listenPort

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index 80d4d75..4f5e20c 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Internationalization

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Internationalization

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index 3732cac..f42ead5 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Documentation

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Documentation

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index bec1f8f..5d83c28 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -51,7 +51,7 @@
     // Output: Inbox "Unread" contains 42 messages
     i18n.getMessage(Locale.ENGLISH, 42, "inbox", "Unread", 42);
 }
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/nosql-databases/index.html b/doc/nosql-databases/index.html
index e5c84c8..94196e2 100644
--- a/doc/nosql-databases/index.html
+++ b/doc/nosql-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – NoSQL Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

NoSQL Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

NoSQL Databases

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index 304fda0..f156790 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -26,7 +26,7 @@
         final long nextValue = this.redis.increment("incr.key");
     }
 }
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index 3881739..f901501 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -56,7 +56,7 @@
       conn.close();
     }
 }
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/index.html b/doc/relational-databases/index.html
index e1403f7..7a9e025 100644
--- a/doc/relational-databases/index.html
+++ b/doc/relational-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Relational Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Relational Databases

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Relational Databases

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index 325dc81..4e56157 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -84,7 +84,7 @@
 
         return conversion.convert(newsModelList, NewsModel.class, News.class);
     }
-

Speed-up PersistenceEntityFactory initialization time
By default, Void Framework tells the PersistenceEntityFactory to scan all JARs of the application’s and dependencies. This scan is necessary to detect models. If you want to greatly improve this initialization time, it is advisable to set the voidframework.persistence.modelsJarUrlPattern configuration key to indicate which JARs to keep. The could be null, a regular expression, or auto (default value).
If the configuration is set to null, only the current JAR / classpath (when started in IDE) will be used. auto is like using the regular expression (.*).

© 2022 Void Framework

+

Speed-up PersistenceEntityFactory initialization time
By default, Void Framework tells the PersistenceEntityFactory to scan all JARs of the application’s and dependencies. This scan is necessary to detect models. If you want to greatly improve this initialization time, it is advisable to set the voidframework.persistence.modelsJarUrlPattern configuration key to indicate which JARs to keep. The could be null, a regular expression, or auto (default value).
If the configuration is set to null, only the current JAR / classpath (when started in IDE) will be used. auto is like using the regular expression (.*).

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index 47eba04..fa61221 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -121,7 +121,7 @@
 
         return conversion.convert(newsModelList, NewsModel.class, News.class);
     }
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/transactional/index.html b/doc/relational-databases/transactional/index.html
index 1b054bc..25f5c77 100644
--- a/doc/relational-databases/transactional/index.html
+++ b/doc/relational-databases/transactional/index.html
@@ -2,7 +2,7 @@
 Void Framework
Documentation
    
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Transactional
It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional (Jakarta) annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
-Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

© 2022 Void Framework

+Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/scheduler/index.html b/doc/scheduler/index.html
index 0ef0ff3..4a0ebad 100644
--- a/doc/scheduler/index.html
+++ b/doc/scheduler/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduler
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduler

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduler

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index dd96623..a83e10f 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -26,7 +26,7 @@
         LOGGER.info("PING!!");
     }
 }
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index 2eb76ce..163c678 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -9,7 +9,7 @@
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
-on the official website.

© 2022 Void Framework

+on the official website.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/template/index.html b/doc/template/index.html
index da2142e..ef6e4e7 100644
--- a/doc/template/index.html
+++ b/doc/template/index.html
@@ -1,7 +1,7 @@
 Void Framework – Template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Template

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Template

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/template/using-template/index.html b/doc/template/using-template/index.html
index d9d6bdc..f1aaf44 100644
--- a/doc/template/using-template/index.html
+++ b/doc/template/using-template/index.html
@@ -26,7 +26,7 @@
     }
 }
 
 
-Note that the data Map must be mutable. Internally the different implementations can add other data to it. If you provide a immutable Map, an exception will be thrown.

© 2022 Void Framework

+Note that the data Map must be mutable. Internally the different implementations can add other data to it. If you provide a immutable Map, an exception will be thrown.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/testing/index.html b/doc/testing/index.html
index 87fb580..ab9d3b6 100644
--- a/doc/testing/index.html
+++ b/doc/testing/index.html
@@ -1,7 +1,7 @@
 Void Framework – Testing
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Testing

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Testing

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index 1fd1d29..7002f4e 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -30,7 +30,7 @@
         Mockito.verify(myRepository, Mockito.times(1)).findAll();
     }
 }
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/vfs/index.html b/doc/vfs/index.html
index dd6800a..ddc1b19 100644
--- a/doc/vfs/index.html
+++ b/doc/vfs/index.html
@@ -1,7 +1,7 @@
 Void Framework – Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Virtual File Storage

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Virtual File Storage

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/vfs/using-vfs/index.html b/doc/vfs/using-vfs/index.html
index b715e40..d83490d 100644
--- a/doc/vfs/using-vfs/index.html
+++ b/doc/vfs/using-vfs/index.html
@@ -53,7 +53,7 @@
         return Result.noContent();
     }
 }
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index b3dbad7..8f7279a 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -61,7 +61,7 @@
 i18n.getMessage('msg.key', 'var');
 i18n.getMessage('msg.key', 'var1', 'var2', /*...*/'varn');
 </script>
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index fffea3b..cc08ad5 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -31,7 +31,7 @@
         return filterChain.applyNext(context);
     }
 }
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/index.html b/doc/web/index.html
index f86e551..b3f18e3 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Web

© 2022 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Web

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/render-template/index.html b/doc/web/render-template/index.html
index b096577..3506e0e 100644
--- a/doc/web/render-template/index.html
+++ b/doc/web/render-template/index.html
@@ -19,7 +19,7 @@
       <img src="${urlfor('static_file', 'img/logo.png')}" alt="image"/>
     </body>
 </html>
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/security-csrf/index.html b/doc/web/security-csrf/index.html
index 5f51721..ae78303 100644
--- a/doc/web/security-csrf/index.html
+++ b/doc/web/security-csrf/index.html
@@ -9,7 +9,7 @@
         globalFilters += "dev.voidframework.web.http.filter.csrf.CSRFFilter"
     }
 }
-

@NoCSRF
Although you have enabled the CSRF filter, you may need to disable CSRF protection on a specific endpoint. To do this, you can use the @NoCSRF annotation which will indicate that the CSRF token does not need to be checked.

© 2022 Void Framework

+

@NoCSRF
Although you have enabled the CSRF filter, you may need to disable CSRF protection on a specific endpoint. To do this, you can use the @NoCSRF annotation which will indicate that the CSRF token does not need to be checked.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/security-headers/index.html b/doc/web/security-headers/index.html
index 38c79c1..623494e 100644
--- a/doc/web/security-headers/index.html
+++ b/doc/web/security-headers/index.html
@@ -9,7 +9,7 @@
         globalFilters += "dev.voidframework.web.http.filter.security.SecurityHeadersFilter"
     }
 }
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/session/index.html b/doc/web/session/index.html
index e3e1ba0..29c5948 100644
--- a/doc/web/session/index.html
+++ b/doc/web/session/index.html
@@ -23,7 +23,7 @@
         return Result.of(userId);
     }
 }
-

© 2022 Void Framework

+

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/using-web/index.html b/doc/web/using-web/index.html
index bfa5cc1..5d2f111 100644
--- a/doc/web/using-web/index.html
+++ b/doc/web/using-web/index.html
@@ -7,7 +7,7 @@
     <artifactId>voidframework-web</artifactId>
     <version>1.6.0</version>
 </dependency>
-

Configuration
The following configuration keys can be used.
Base
voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly. The default value is 15 seconds.
voidframework.web.errorHandler the implementation of the error handler to use in case of http error. The default value is dev.voidframework.web.http.errorhandler.DefaultErrorHandler.
voidframework.web.contextPath the default context path root. The default value is /.
voidframework.web.routes a list of routing definition classes (must implement the interface AppRoutesDefinition). The default value is [].
voidframework.web.globalFilters a list of routing global filter classes (must implement the interface Filter). The default value is [].
voidframework.web.baseAssetResourcesDirectory the default location of static files in the “resources” directory. The default value is static.
Server
voidframework.web.server.idleTimeout the time without any request to wait before the connection is closed. The default value is 30 seconds.
voidframework.web.server.extraWebServerConfiguration the implementation of the interface ExtraWebServerConfiguration to apply a custom configuration to the Undertow web server. The default value is null.
voidframework.web.server.ioThreads the number of I/O threads. If not specified (value = null or 0), Math.max(Runtime.getRuntime().availableProcessors(), 2) value will be used. The default value is null.
voidframework.web.server.workerThreads the number of Worker threads. If not specified (value = null or 0), ioThreadsNumber * 8 value will be used. The default value is null.
voidframework.web.server.maxBodySize the max body content size. The default value is 1 MiB.
voidframework.web.server.fileSizeThreshold the maximum size allowed in memory before the uploaded file was stored on the disk rather than in memory. The default value is 256 KiB.
voidframework.web.server.tempFileLocation the location where temporary files will be stored. The default value is null (default Java temporary folder).
HTTP
voidframework.web.server.http.listenHost the interface on which the server will listen for non-secure HTTP requests. The default value is 127.0.0.1.
voidframework.web.server.http.listenPort the port on which the server will listen for non-secure HTTP requests. The default value is 9000.
HTTPS
voidframework.web.server.https.listenHost the interface on which the server will listen for HTTPS requests. The default value is 127.0.0.1.
voidframework.web.server.https.listenPort the port on which the server will listen for HTTPS requests. The default value is 9001.
voidframework.web.server.https.ssl.protocols the protocols to use. The default value is ["TLSv1.2", "TLSv1.3"].
voidframework.web.server.https.ssl.ciphers the allowed ciphers. If list is empty, all ciphers will be allowed. The default value is [].
voidframework.web.server.https.ssl.keyStorePath the path where is located the key store. Could be a “resources” path, a URL or a simple path. The default value is null.
voidframework.web.server.https.ssl.keyStoreType the type of the key store. The default value is JKS.
voidframework.web.server.https.ssl.keyStorePassword the password to use to open the key store. The default value is null.
voidframework.web.server.https.ssl.keyAlias the alias of the key to use. If “null” the key will be choosen automatically. The default value is null.
voidframework.web.server.https.ssl.keyPassword the key password. The default value is ${voidframework.web.server.https.ssl.keyStorePassword}.
Language
voidframework.web.language.availableLanguages the available languages. The default value is ["en", "fr"].
voidframework.web.language.cookieName the name of the cookie containing the current language. The default value is VOID_LANG.
voidframework.web.language.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.language.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Flash messages
voidframework.web.flashMessages.cookieName the name of the cookie containing the current flash messages. The default value is VOID_FLASH.
voidframework.web.flashMessages.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.flashMessages.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Session
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.
CSRF
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.
Security headers
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.

© 2022 Void Framework

+

Configuration
The following configuration keys can be used.
Base
voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly. The default value is 15 seconds.
voidframework.web.errorHandler the implementation of the error handler to use in case of http error. The default value is dev.voidframework.web.http.errorhandler.DefaultErrorHandler.
voidframework.web.contextPath the default context path root. The default value is /.
voidframework.web.routes a list of routing definition classes (must implement the interface AppRoutesDefinition). The default value is [].
voidframework.web.globalFilters a list of routing global filter classes (must implement the interface Filter). The default value is [].
voidframework.web.baseAssetResourcesDirectory the default location of static files in the “resources” directory. The default value is static.
Server
voidframework.web.server.idleTimeout the time without any request to wait before the connection is closed. The default value is 30 seconds.
voidframework.web.server.extraWebServerConfiguration the implementation of the interface ExtraWebServerConfiguration to apply a custom configuration to the Undertow web server. The default value is null.
voidframework.web.server.ioThreads the number of I/O threads. If not specified (value = null or 0), Math.max(Runtime.getRuntime().availableProcessors(), 2) value will be used. The default value is null.
voidframework.web.server.workerThreads the number of Worker threads. If not specified (value = null or 0), ioThreadsNumber * 8 value will be used. The default value is null.
voidframework.web.server.maxBodySize the max body content size. The default value is 1 MiB.
voidframework.web.server.fileSizeThreshold the maximum size allowed in memory before the uploaded file was stored on the disk rather than in memory. The default value is 256 KiB.
voidframework.web.server.tempFileLocation the location where temporary files will be stored. The default value is null (default Java temporary folder).
HTTP
voidframework.web.server.http.listenHost the interface on which the server will listen for non-secure HTTP requests. The default value is 127.0.0.1.
voidframework.web.server.http.listenPort the port on which the server will listen for non-secure HTTP requests. The default value is 9000.
HTTPS
voidframework.web.server.https.listenHost the interface on which the server will listen for HTTPS requests. The default value is 127.0.0.1.
voidframework.web.server.https.listenPort the port on which the server will listen for HTTPS requests. The default value is 9001.
voidframework.web.server.https.ssl.protocols the protocols to use. The default value is ["TLSv1.2", "TLSv1.3"].
voidframework.web.server.https.ssl.ciphers the allowed ciphers. If list is empty, all ciphers will be allowed. The default value is [].
voidframework.web.server.https.ssl.keyStorePath the path where is located the key store. Could be a “resources” path, a URL or a simple path. The default value is null.
voidframework.web.server.https.ssl.keyStoreType the type of the key store. The default value is JKS.
voidframework.web.server.https.ssl.keyStorePassword the password to use to open the key store. The default value is null.
voidframework.web.server.https.ssl.keyAlias the alias of the key to use. If “null” the key will be choosen automatically. The default value is null.
voidframework.web.server.https.ssl.keyPassword the key password. The default value is ${voidframework.web.server.https.ssl.keyStorePassword}.
Language
voidframework.web.language.availableLanguages the available languages. The default value is ["en", "fr"].
voidframework.web.language.cookieName the name of the cookie containing the current language. The default value is VOID_LANG.
voidframework.web.language.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.language.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Flash messages
voidframework.web.flashMessages.cookieName the name of the cookie containing the current flash messages. The default value is VOID_FLASH.
voidframework.web.flashMessages.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.flashMessages.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Session
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.
CSRF
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.
Security headers
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/index.html b/index.html
index a72d4e4..981b1b1 100644
--- a/index.html
+++ b/index.html
@@ -2,7 +2,7 @@
 Void Framework
Documentation
    
 Release notes
Light and modular Framework for Java
Stay focus on your business

Documentation
-Release notes
Fork me on GitHub

© 2022 Void Framework

+Release notes
Fork me on GitHub

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 477ef52..bdf20c7 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -15,7 +15,7 @@
 2022-07-24
Fixed Error 500 CSRF when POST request render template
Improved Change CSRF signature algorithm to HMACSHA256

1.1.0

 2022-07-22
New Methods on Reflection util class: getAnnotatedField(Object, Class) and getAnnotatedField(Class, Class)
New Configuration keys to define number of I/O and Worker threads (Web)
New Redis (base + cache + healthcheck)
New CSRF token
Fixed Cookie revocation not working
Fixed C3P0/HikariCP settings
Fixed Issue on routes sorting when regex and capture regex are used
Fixed Assets not found when devMode=false
Fixed Hibernate : Models not found when application is compiled
Improved No longer necessary for HealthChecker to be Singleton
Improved Add cache abstraction helper
Improved Session signature key configuration is now required
Improved Rename ApplicationLauncher to VoidApplication
Improved Updated version of all dependencies

1.0.1

 2022-07-08
New Ability to retrieve XML body content as Java object
Fixed Removed I18N reference from Hibernate module
Fixed Transactional annotation : rollback not occur on unchecked exception
Fixed Routes are randomly sorted
Improved Cache management : rename the annotation Cache to CacheResult and add CacheRemove

1.0.0

-2022-07-02
Initial release

© 2022 Void Framework

+2022-07-02
Initial release

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 

From 8361486d1525b89e2e79ac16cb1340576639740b Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Fri, 24 Feb 2023 19:06:03 +0000
Subject: [PATCH 41/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/redis-cache/index.html              |  2 +-
 doc/core/configuration/index.html             |  4 +--
 .../new-application/index.html                |  4 +--
 doc/index.xml                                 | 32 ++++++++---------
 .../using-i18n/index.html                     |  2 +-
 doc/nosql-databases/redis/index.html          |  4 +--
 .../datasource/index.html                     |  4 +--
 .../persistence-hibernate/index.html          |  2 +-
 .../persistence-jooq/index.html               |  2 +-
 doc/template/freemarker/index.html            |  2 +-
 doc/testing/junit-extension/index.html        |  2 +-
 doc/vfs/using-vfs/index.html                  |  2 +-
 doc/web/using-web/index.html                  |  2 +-
 index.xml                                     | 34 +++++++++----------
 releasenotes/index.html                       |  5 +--
 16 files changed, 53 insertions(+), 52 deletions(-)

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 486e0e5..19b6e4d 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.6.0</version>
+    <version>1.6.1</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 3392cf9..94bc391 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.6.0</version>
+    <version>1.6.1</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index 0aebe40..f7d191b 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -25,7 +25,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.6.0</version>
+  <version>1.6.1</version>
 </dependency>
 
voidframework {
     code {
@@ -60,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.6.0</version>
+  <version>1.6.1</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 4006c3a..ee3d07c 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.6.0</version>
+    <version>1.6.1</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.6.0</version>
+    <version>1.6.1</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/index.xml b/doc/index.xml
index a200563..0e054e9 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,13 +1,13 @@
 Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -30,10 +30,10 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
@@ -43,9 +43,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -57,10 +57,10 @@ priority is used to define when the method will be called in relation to the oth
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -87,19 +87,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 5d83c28..ecc4ae2 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.6.0</version>
+    <version>1.6.1</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index f156790..b2b008b 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
-    <version>1.6.0</version>
+    <version>1.6.1</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
-    <version>1.6.0</version>
+    <version>1.6.1</version>
 </dependency>
 

Example
@Service
 public final class ExampleService {
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index f901501..3b88745 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -5,12 +5,12 @@
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.6.0</version>
+    <version>1.6.1</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.6.0</version>
+    <version>1.6.1</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index 4e56157..23bf245 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -6,7 +6,7 @@
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.6.0</version>
+    <version>1.6.1</version>
 </dependency>
 

Working with transaction manually
final EntityManager entityManager = this.entityManagerProvider.get();
 final EntityTransaction transaction = entityManager.getTransaction();
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index fa61221..5b8e1a7 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-jooq</artifactId>
-    <version>1.6.0</version>
+    <version>1.6.1</version>
 </dependency>
 

Generator
To work, jOOQ needs files generated during the compilation of the project. It is possible to generate the required classes in different ways (scan database, scan entity, …). For more information, please visit the official jOOQ website.
To enable code generation, add & customize the code below.
pom.xml
<build>
     <plugins>
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index 163c678..b2e19cd 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.6.0</version>
+    <version>1.6.1</version>
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index 7002f4e..25cc0ff 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
-    <version>1.6.0</version>
+    <version>1.6.1</version>
 </dependency>
 

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
 @ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
diff --git a/doc/vfs/using-vfs/index.html b/doc/vfs/using-vfs/index.html
index d83490d..95cac78 100644
--- a/doc/vfs/using-vfs/index.html
+++ b/doc/vfs/using-vfs/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
-    <version>1.6.0</version>
+    <version>1.6.1</version>
 </dependency>
 

Configuration
Different VirtualFileStorage implementations must be configured in voidframework.vfs namespace. The following configuration keys can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
 Note that each implementation can have extra configuration keys.

Example
voidframework {
diff --git a/doc/web/using-web/index.html b/doc/web/using-web/index.html
index 5d2f111..a1c742b 100644
--- a/doc/web/using-web/index.html
+++ b/doc/web/using-web/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.6.0</version>
+    <version>1.6.1</version>
 </dependency>
 

Configuration
The following configuration keys can be used.
Base
voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly. The default value is 15 seconds.
voidframework.web.errorHandler the implementation of the error handler to use in case of http error. The default value is dev.voidframework.web.http.errorhandler.DefaultErrorHandler.
voidframework.web.contextPath the default context path root. The default value is /.
voidframework.web.routes a list of routing definition classes (must implement the interface AppRoutesDefinition). The default value is [].
voidframework.web.globalFilters a list of routing global filter classes (must implement the interface Filter). The default value is [].
voidframework.web.baseAssetResourcesDirectory the default location of static files in the “resources” directory. The default value is static.
Server
voidframework.web.server.idleTimeout the time without any request to wait before the connection is closed. The default value is 30 seconds.
voidframework.web.server.extraWebServerConfiguration the implementation of the interface ExtraWebServerConfiguration to apply a custom configuration to the Undertow web server. The default value is null.
voidframework.web.server.ioThreads the number of I/O threads. If not specified (value = null or 0), Math.max(Runtime.getRuntime().availableProcessors(), 2) value will be used. The default value is null.
voidframework.web.server.workerThreads the number of Worker threads. If not specified (value = null or 0), ioThreadsNumber * 8 value will be used. The default value is null.
voidframework.web.server.maxBodySize the max body content size. The default value is 1 MiB.
voidframework.web.server.fileSizeThreshold the maximum size allowed in memory before the uploaded file was stored on the disk rather than in memory. The default value is 256 KiB.
voidframework.web.server.tempFileLocation the location where temporary files will be stored. The default value is null (default Java temporary folder).
HTTP
voidframework.web.server.http.listenHost the interface on which the server will listen for non-secure HTTP requests. The default value is 127.0.0.1.
voidframework.web.server.http.listenPort the port on which the server will listen for non-secure HTTP requests. The default value is 9000.
HTTPS
voidframework.web.server.https.listenHost the interface on which the server will listen for HTTPS requests. The default value is 127.0.0.1.
voidframework.web.server.https.listenPort the port on which the server will listen for HTTPS requests. The default value is 9001.
voidframework.web.server.https.ssl.protocols the protocols to use. The default value is ["TLSv1.2", "TLSv1.3"].
voidframework.web.server.https.ssl.ciphers the allowed ciphers. If list is empty, all ciphers will be allowed. The default value is [].
voidframework.web.server.https.ssl.keyStorePath the path where is located the key store. Could be a “resources” path, a URL or a simple path. The default value is null.
voidframework.web.server.https.ssl.keyStoreType the type of the key store. The default value is JKS.
voidframework.web.server.https.ssl.keyStorePassword the password to use to open the key store. The default value is null.
voidframework.web.server.https.ssl.keyAlias the alias of the key to use. If “null” the key will be choosen automatically. The default value is null.
voidframework.web.server.https.ssl.keyPassword the key password. The default value is ${voidframework.web.server.https.ssl.keyStorePassword}.
Language
voidframework.web.language.availableLanguages the available languages. The default value is ["en", "fr"].
voidframework.web.language.cookieName the name of the cookie containing the current language. The default value is VOID_LANG.
voidframework.web.language.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.language.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Flash messages
voidframework.web.flashMessages.cookieName the name of the cookie containing the current flash messages. The default value is VOID_FLASH.
voidframework.web.flashMessages.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.flashMessages.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Session
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.
CSRF
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.
Security headers
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/index.xml b/index.xml
index 4ce851f..cdbdb1c 100644
--- a/index.xml
+++ b/index.xml
@@ -1,13 +1,13 @@
 Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -30,10 +30,10 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
@@ -43,9 +43,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -57,13 +57,13 @@ priority is used to define when the method will be called in relation to the oth
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.0 2023-02-11 New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.0 2023-02-11 New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.5.0 2023-01-02 New CUID validator New Internationalization for JavaScript New Conditional feature Improved Http Result methods now accept charset Improved Rename bindable annotation from @BindClass to @Bindable Improved Clean thread data (Transactional) Improved Updated version of all dependencies 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.1 2023-02-11 Fixed HTTP webserver graceful shutdown not honored 1.6.0 2023-02-11 New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.1 2023-02-11 Fixed HTTP webserver graceful shutdown not honored 1.6.0 2023-02-11 New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
@@ -87,19 +87,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index bdf20c7..cdd7e99 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,7 +1,8 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.6.0

+Release notes
1.6.1

+2023-02-11
Fixed HTTP webserver graceful shutdown not honored

1.6.0

 2023-02-11
New Web module can now respond to requests securely via HTTPS
New NotInstance validation constraint
New Utility class DurationUtils
Improved Graceful stop timeout is now a duration (with time unit)
Improved Commercial at "@" constant now available in CharConstants and StringConstants classes
Improved Annotation RequestVariable can now use fallback value
Improved Updated version of all dependencies

1.5.1

 2023-01-07
Fixed JavaScript i18n reverse routing name (js_i18n)

1.5.0

 2023-01-02
New CUID validator
New Internationalization for JavaScript
New Conditional feature
Improved Http Result methods now accept charset
Improved Rename bindable annotation from @BindClass to @Bindable
Improved Clean thread data (Transactional)
Improved Updated version of all dependencies

1.4.0


From 9045c73617092aa48fce90e6e79fd74626d26ebf Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Fri, 24 Feb 2023 19:09:07 +0000
Subject: [PATCH 42/75] Automated website build

---
 index.xml               | 2 +-
 releasenotes/index.html | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.xml b/index.xml
index cdbdb1c..857b226 100644
--- a/index.xml
+++ b/index.xml
@@ -63,7 +63,7 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.1 2023-02-11 Fixed HTTP webserver graceful shutdown not honored 1.6.0 2023-02-11 New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.1 2023-02-11 Fixed HTTP webserver graceful shutdown not honored 1.6.0 2023-02-11 New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.1 2023-02-24 Fixed HTTP webserver graceful shutdown not honored 1.6.0 2023-02-11 New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.1 2023-02-24 Fixed HTTP webserver graceful shutdown not honored 1.6.0 2023-02-11 New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
diff --git a/releasenotes/index.html b/releasenotes/index.html
index cdd7e99..479cd2d 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,8 +1,8 @@
-Void Framework – Release notes

+Void Framework – Release notes
 Void Framework
Documentation
    
 Release notes
1.6.1

-2023-02-11
Fixed HTTP webserver graceful shutdown not honored

1.6.0

+2023-02-24
Fixed HTTP webserver graceful shutdown not honored

1.6.0

 2023-02-11
New Web module can now respond to requests securely via HTTPS
New NotInstance validation constraint
New Utility class DurationUtils
Improved Graceful stop timeout is now a duration (with time unit)
Improved Commercial at "@" constant now available in CharConstants and StringConstants classes
Improved Annotation RequestVariable can now use fallback value
Improved Updated version of all dependencies

1.5.1

 2023-01-07
Fixed JavaScript i18n reverse routing name (js_i18n)

1.5.0

 2023-01-02
New CUID validator
New Internationalization for JavaScript
New Conditional feature
Improved Http Result methods now accept charset
Improved Rename bindable annotation from @BindClass to @Bindable
Improved Clean thread data (Transactional)
Improved Updated version of all dependencies

1.4.0


From 2273a4c5185e6df7b2fc0ff6ffb92b8628fefe45 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 13 Apr 2023 18:16:42 +0000
Subject: [PATCH 43/75] Automated website build

---
 doc/advanced/advanced/index.html              |  2 +-
 doc/advanced/index.html                       |  2 +-
 doc/cache/in-memory-cache/index.html          |  4 +-
 doc/cache/index.html                          |  2 +-
 doc/cache/redis-cache/index.html              |  6 +--
 doc/cache/using-cache/index.html              |  6 +--
 doc/core/boot-sequence/index.html             |  2 +-
 doc/core/class-scanning/index.html            |  2 +-
 doc/core/conditional-feature/index.html       |  2 +-
 doc/core/configuration/index.html             |  6 +--
 doc/core/index.html                           |  2 +-
 doc/core/lang/index.html                      |  2 +-
 doc/core/life-cycle/index.html                |  2 +-
 doc/core/type-conversion/index.html           |  2 +-
 doc/getting-started/index.html                |  2 +-
 .../new-application/index.html                |  6 +--
 doc/getting-started/requirements/index.html   |  2 +-
 .../upgrading-from-old-version/index.html     |  2 +-
 doc/i18n/index.html                           |  2 +-
 doc/index.html                                |  2 +-
 doc/index.xml                                 | 50 +++++++++++--------
 .../using-i18n/index.html                     |  4 +-
 doc/nosql-databases/index.html                |  2 +-
 doc/nosql-databases/redis/index.html          |  6 +--
 .../datasource/index.html                     |  6 +--
 doc/relational-databases/index.html           |  2 +-
 .../persistence-hibernate/index.html          |  4 +-
 .../persistence-jooq/index.html               |  4 +-
 .../transactional/index.html                  |  2 +-
 doc/scheduler/index.html                      |  2 +-
 doc/scheduler/scheduling-job-cron/index.html  |  2 +-
 doc/sendmail/index.html                       |  8 +++
 .../mailer-apache-commons-email/index.html    | 14 ++++++
 doc/sendmail/sending-emails/index.html        | 34 +++++++++++++
 doc/template/freemarker/index.html            |  4 +-
 doc/template/index.html                       |  2 +-
 doc/template/using-template/index.html        |  2 +-
 doc/testing/index.html                        |  2 +-
 doc/testing/junit-extension/index.html        |  4 +-
 doc/vfs/index.html                            |  2 +-
 doc/vfs/using-vfs/index.html                  |  4 +-
 doc/web/controller/index.html                 |  2 +-
 doc/web/filters/index.html                    |  2 +-
 doc/web/index.html                            |  2 +-
 doc/web/render-template/index.html            |  2 +-
 doc/web/security-csrf/index.html              |  2 +-
 doc/web/security-headers/index.html           |  2 +-
 doc/web/session/index.html                    |  2 +-
 doc/web/using-web/index.html                  |  4 +-
 index.xml                                     | 50 +++++++++++--------
 releasenotes/index.html                       |  5 +-
 sitemap.xml                                   |  2 +-
 52 files changed, 183 insertions(+), 110 deletions(-)
 create mode 100644 doc/sendmail/index.html
 create mode 100644 doc/sendmail/mailer-apache-commons-email/index.html
 create mode 100644 doc/sendmail/sending-emails/index.html

diff --git a/doc/advanced/advanced/index.html b/doc/advanced/advanced/index.html
index 16aaa0a..75d3cc6 100644
--- a/doc/advanced/advanced/index.html
+++ b/doc/advanced/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – reference.conf

 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-sendmail reference.conf
voidframework-sendmail-commonsemail reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/advanced/index.html b/doc/advanced/index.html
index fbaeb22..924b4c5 100644
--- a/doc/advanced/index.html
+++ b/doc/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – Advanced
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Advanced

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Advanced

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 19b6e4d..cfc9baf 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,10 +2,10 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.6.1</version>
+    <version>1.7.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/index.html b/doc/cache/index.html
index 9edc2d2..dfdec9f 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 94bc391..d846f89 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -1,11 +1,11 @@
 Void Framework – Cache engine : Redis
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.7.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.6.1</version>
+    <version>1.7.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index cdee189..e107d18 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,12 +2,12 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
-Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
+Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

@CachePut
Indicates that the result of the method will be cached regardless value already exists.

Example
@BindClass
 public class CacheExample {
 
-    @CacheResult
+    @CachePut
     public String exampleMethod() {
         return "value";
     }
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index 2758d28..44dbce3 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c . t o u e y a h d i r c l P . u c l r b">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index 6e2d6cc..e3c788a 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,7 +2,7 @@
 Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes i">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
 3 types of elements are recognised during the scan:
Classes extending AbstractModule (Guice)
Classes annotated with Bindable annotation
Classes implementing defined interface

Guice module
Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.
 
 If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@Bindable 
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Defined interface
The configuration key voidframework.core.bindExtraInterfaces is used to define a set of interfaces for which to bind the found implementations. For example, converters are automatically detected in this way via the TypeConverter interface.

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
diff --git a/doc/core/conditional-feature/index.html b/doc/core/conditional-feature/index.html
index 74142c0..d8f3120 100644
--- a/doc/core/conditional-feature/index.html
+++ b/doc/core/conditional-feature/index.html
@@ -2,7 +2,7 @@
 @ConditionalFeature The @ConditionalFeature annotation allows a feature to be enabled or">Void Framework – Conditional feature
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Conditional feature
Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.

@ConditionalFeature
The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
The annotation accepts the following parameter:
value is used to define the implementation of Condition interface to use.
Exemple
@WebController
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Conditional feature
Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.

@ConditionalFeature
The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
The annotation accepts the following parameter:
value is used to define the implementation of Condition interface to use.
Exemple
@WebController
 @ConditionalFeature(MyCustomCondition.class)
 public final class SampleController {
 }
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index f7d191b..ee0c7cb 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -1,7 +1,7 @@
 Void Framework – Configuration
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
 

Retrieve configuration value from Java
@Service
 public class MyService {
 
@@ -25,7 +25,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.6.1</version>
+  <version>1.7.0</version>
 </dependency>
 
voidframework {
     code {
@@ -60,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.6.1</version>
+  <version>1.7.0</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/core/index.html b/doc/core/index.html
index eb3aa01..7b74d85 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Core

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Core

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/lang/index.html b/doc/core/lang/index.html
index 23063e4..24371ce 100644
--- a/doc/core/lang/index.html
+++ b/doc/core/lang/index.html
@@ -2,7 +2,7 @@
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get mor">Void Framework – Lang
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Lang
The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.

CUID
CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
// Random CUID
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Lang
The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.

CUID
CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
// Random CUID
 final CUID cuid = CUID.randomCUID();
 
 // CUID from String representating a CUID
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index d22d540..354f447 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time (duration or milliseconds) to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index b710d8e..651c5c8 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index 81c7adc..cfd93f8 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Getting Started

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Getting Started

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index ee3d07c..40f518b 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,15 +2,15 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.6.1</version>
+    <version>1.7.0</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.6.1</version>
+    <version>1.7.0</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index 1c42561..d559bf3 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index f0f4284..a09f77e 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.0.0 Initial relea">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.0.0
Initial release

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

1.6.0
Configuration keys voidframework.web.server.listenHost and voidframework.web.server.listenPort have been renamed to voidframework.web.server.http.listenHost and voidframework.web.server.http.listenPort

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.0.0
Initial release

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

1.6.0
Configuration keys voidframework.web.server.listenHost and voidframework.web.server.listenPort have been renamed to voidframework.web.server.http.listenHost and voidframework.web.server.http.listenPort

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index 4f5e20c..9f78917 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Internationalization

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Internationalization

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index f42ead5..e68dcdd 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Documentation

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Documentation

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 0e054e9..d25de51 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,13 +1,13 @@
-Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -30,10 +30,10 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
@@ -43,9 +43,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -55,15 +55,21 @@ The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
-priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
+priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Configuration The following configuration keys can be used in the configuration file of your application:
+voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Configuration The following configuration keys can be used in the configuration file of your application:
+voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
@@ -75,7 +81,9 @@ openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment
 Define a Job To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Define a Job To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
-voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -87,19 +95,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index ecc4ae2..e747f54 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,10 +1,10 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.6.1</version>
+    <version>1.7.0</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/index.html b/doc/nosql-databases/index.html
index 94196e2..5295e87 100644
--- a/doc/nosql-databases/index.html
+++ b/doc/nosql-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – NoSQL Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

NoSQL Databases

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

NoSQL Databases

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index b2b008b..999808c 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -2,15 +2,15 @@
 Installation To enable this module, just add following lines to ">Void Framework – Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
-    <version>1.6.1</version>
+    <version>1.7.0</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
-    <version>1.6.1</version>
+    <version>1.7.0</version>
 </dependency>
 

Example
@Service
 public final class ExampleService {
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index 3b88745..9f8e03f 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -1,16 +1,16 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.6.1</version>
+    <version>1.7.0</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.6.1</version>
+    <version>1.7.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/relational-databases/index.html b/doc/relational-databases/index.html
index 7a9e025..56a75e3 100644
--- a/doc/relational-databases/index.html
+++ b/doc/relational-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Relational Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Relational Databases

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Relational Databases

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index 23bf245..28ae3f3 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -2,11 +2,11 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.6.1</version>
+    <version>1.7.0</version>
 </dependency>
 

Working with transaction manually
final EntityManager entityManager = this.entityManagerProvider.get();
 final EntityTransaction transaction = entityManager.getTransaction();
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index 5b8e1a7..6d6f670 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -2,10 +2,10 @@
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provid">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-jooq</artifactId>
-    <version>1.6.1</version>
+    <version>1.7.0</version>
 </dependency>
 

Generator
To work, jOOQ needs files generated during the compilation of the project. It is possible to generate the required classes in different ways (scan database, scan entity, …). For more information, please visit the official jOOQ website.
To enable code generation, add & customize the code below.
pom.xml
<build>
     <plugins>
diff --git a/doc/relational-databases/transactional/index.html b/doc/relational-databases/transactional/index.html
index 25f5c77..a7b07f6 100644
--- a/doc/relational-databases/transactional/index.html
+++ b/doc/relational-databases/transactional/index.html
@@ -1,7 +1,7 @@
 Void Framework – Transactional
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Transactional
It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional (Jakarta) annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Transactional
It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional (Jakarta) annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
 Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
diff --git a/doc/scheduler/index.html b/doc/scheduler/index.html
index 4a0ebad..15578a3 100644
--- a/doc/scheduler/index.html
+++ b/doc/scheduler/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduler
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduler

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduler

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index a83e10f..4571c6d 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduling a local job
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron a CRON-like expression. The default value is empty (disabled).
cronZone the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron a CRON-like expression. The default value is empty (disabled).
cronZone the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
 public final class Ping {
 
     private static final Logger LOGGER = LoggerFactory.getLogger(Ping.class);
diff --git a/doc/sendmail/index.html b/doc/sendmail/index.html
new file mode 100644
index 0000000..d20918f
--- /dev/null
+++ b/doc/sendmail/index.html
@@ -0,0 +1,8 @@
+Void Framework – Sendmail
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Sendmail

© 2022-2023 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/sendmail/mailer-apache-commons-email/index.html b/doc/sendmail/mailer-apache-commons-email/index.html
new file mode 100644
index 0000000..c95365b
--- /dev/null
+++ b/doc/sendmail/mailer-apache-commons-email/index.html
@@ -0,0 +1,14 @@
+Void Framework – Mailer : Apache Commons Email
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Mailer : Apache Commons Email
This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.

Installation
<dependency>
+    <groupId>dev.voidframework</groupId>
+    <artifactId>voidframework-sendmail-commonsemail</artifactId>
+    <version>1.7.0</version>
+</dependency>
+
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.commonsemail.username user name for authentication. The default value is null.
voidframework.sendmail.commonsemail.password password for authentication. The default value is null.
This module also includes many of the configuration keys of the Java Mail properties. To use it, simply prefix them with voidframework.sendmail.commonsemail.. Here is the list of possible properties:
https://javaee.github.io/javamail/docs/api/javax/mail/internet/package-summary.html
mail.mime.address.usecanonicalhostname
mail.mime.allowencodedmessages
mail.mime.applefilenames
mail.mime.base64.ignoreerrors
mail.mime.charset
mail.mime.contenttypehandler
mail.mime.decodefilename
mail.mime.decodeparameters
mail.mime.decodetext.strict
mail.mime.encodeeol.strict
mail.mime.encodefilename
mail.mime.encodeparameters
mail.mime.foldtext
mail.mime.ignoremultipartencoding
mail.mime.ignoreunknownencoding
mail.mime.ignorewhitespacelines
mail.mime.multipart.allowempty
mail.mime.multipart.ignoreexistingboundaryparameter
mail.mime.multipart.ignoremissingboundaryparameter
mail.mime.multipart.ignoremissingendboundary
mail.mime.parameters.strict
mail.mime.setcontenttypefilename
mail.mime.setdefaulttextcharset
mail.mime.uudecode.ignoreerrors
mail.mime.uudecode.ignoremissingbeginend
mail.mime.windowsfilenames
https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html
mail.smtp.user
mail.smtp.host
mail.smtp.port
mail.smtp.connectiontimeout
mail.smtp.timeout
mail.smtp.writetimeout
mail.smtp.from
mail.smtp.localhost
mail.smtp.localaddress
mail.smtp.localport
mail.smtp.ehlo
mail.smtp.auth
mail.smtp.auth.mechanisms
mail.smtp.auth.login.disable
mail.smtp.auth.plain.disable
mail.smtp.auth.digest-md5.disable
mail.smtp.auth.ntlm.disable
mail.smtp.auth.ntlm.domain
mail.smtp.auth.ntlm.flags
mail.smtp.auth.xoauth2.disable
mail.smtp.submitter
mail.smtp.dsn.notify
mail.smtp.dsn.ret
mail.smtp.allow8bitmime
mail.smtp.sendpartial
mail.smtp.sasl.enable
mail.smtp.sasl.mechanisms
mail.smtp.sasl.authorizationid
mail.smtp.sasl.realm
mail.smtp.sasl.usecanonicalhostname
mail.smtp.quitwait
mail.smtp.reportsuccess
mail.smtp.socketFactory
mail.smtp.socketFactory.class
mail.smtp.socketFactory.fallback
mail.smtp.socketFactory.port
mail.smtp.ssl.enable
mail.smtp.ssl.checkserveridentity
mail.smtp.ssl.trust
mail.smtp.ssl.socketFactory
mail.smtp.ssl.socketFactory.class
mail.smtp.ssl.socketFactory.port
mail.smtp.ssl.protocols
mail.smtp.ssl.ciphersuites
mail.smtp.starttls.enable
mail.smtp.starttls.required
mail.smtp.proxy.host
mail.smtp.proxy.port
mail.smtp.proxy.user
mail.smtp.proxy.password
mail.smtp.socks.host
mail.smtp.socks.port
mail.smtp.mailextension
mail.smtp.userset
mail.smtp.noop.strict

© 2022-2023 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/sendmail/sending-emails/index.html b/doc/sendmail/sending-emails/index.html
new file mode 100644
index 0000000..9912450
--- /dev/null
+++ b/doc/sendmail/sending-emails/index.html
@@ -0,0 +1,34 @@
+Void Framework – Sending emails
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Sending emails
If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.

Installation
<dependency>
+    <groupId>dev.voidframework</groupId>
+    <artifactId>voidframework-sendmail</artifactId>
+    <version>1.7.0</version>
+</dependency>
+
In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail module

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.engine the mailer implementation to use. The default value is null.
voidframework.sendmail.mailQueuePollTimeout the time to wait before giving up when retrieving a mail to be sent from the queue of mail waiting to be sent when the queue is empty. The default value is 2 seconds.
voidframework.sendmail.gracefulStopTimeout the time for the daemon to shut down properly before it was terminated. The default value is 15 seconds.

Examples
@BindClass
+public final class Service {
+
+    private final Sendmail sendmail;
+
+    @Inject
+    public Service(final Sendmail sendmail) {
+        this.sendmail = sendmail;
+    }
+
+    public void sample() {
+        final Mail mail = new Mail();
+        mail.setSubject("Hello World!");
+        mail.setBodyContentText("Hello World!");
+        mail.setFrom("charlie.root@local.domain", "Charlie Root");
+        mail.addRecipient("john@local.domain");
+
+        sendmail.send(mail);
+    }
+}
+

© 2022-2023 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index b2e19cd..833d458 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -2,10 +2,10 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifact">Void Framework – FreeMarker
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.6.1</version>
+    <version>1.7.0</version>
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/doc/template/index.html b/doc/template/index.html
index ef6e4e7..8df67e4 100644
--- a/doc/template/index.html
+++ b/doc/template/index.html
@@ -1,7 +1,7 @@
 Void Framework – Template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Template

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Template

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/template/using-template/index.html b/doc/template/using-template/index.html
index f1aaf44..934b532 100644
--- a/doc/template/using-template/index.html
+++ b/doc/template/using-template/index.html
@@ -2,7 +2,7 @@
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final Temp">Void Framework – Using template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using template
Sooner or later you will need to generate documents (HTML, PDF…). Void Framework provides all the tools you need!

Example
public class TemplateExample {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using template
Sooner or later you will need to generate documents (HTML, PDF…). Void Framework provides all the tools you need!

Example
public class TemplateExample {
 
     private final TemplateRenderer templateRenderer;
 
diff --git a/doc/testing/index.html b/doc/testing/index.html
index ab9d3b6..45dbe6e 100644
--- a/doc/testing/index.html
+++ b/doc/testing/index.html
@@ -1,7 +1,7 @@
 Void Framework – Testing
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Testing

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Testing

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index 25cc0ff..6ed5532 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -2,10 +2,10 @@
 To enable this module, just add following lines to th">Void Framework – JUnit's extension
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
-    <version>1.6.1</version>
+    <version>1.7.0</version>
 </dependency>
 

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
 @ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
diff --git a/doc/vfs/index.html b/doc/vfs/index.html
index ddc1b19..855c1a9 100644
--- a/doc/vfs/index.html
+++ b/doc/vfs/index.html
@@ -1,7 +1,7 @@
 Void Framework – Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Virtual File Storage

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Virtual File Storage

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/vfs/using-vfs/index.html b/doc/vfs/using-vfs/index.html
index 95cac78..2876904 100644
--- a/doc/vfs/using-vfs/index.html
+++ b/doc/vfs/using-vfs/index.html
@@ -1,10 +1,10 @@
 Void Framework – Using Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
-    <version>1.6.1</version>
+    <version>1.7.0</version>
 </dependency>
 

Configuration
Different VirtualFileStorage implementations must be configured in voidframework.vfs namespace. The following configuration keys can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
 Note that each implementation can have extra configuration keys.

Example
voidframework {
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index 8f7279a..d492705 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index cc08ad5..9ae52ef 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the">Void Framework – Filters
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
 Note that the use of dependencies direct injection is possible in filters.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
 @Singleton
 @WebController
diff --git a/doc/web/index.html b/doc/web/index.html
index b3f18e3..c1490eb 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Web

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Web

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/render-template/index.html b/doc/web/render-template/index.html
index 3506e0e..28d118a 100644
--- a/doc/web/render-template/index.html
+++ b/doc/web/render-template/index.html
@@ -2,7 +2,7 @@
 Although you can manually use the template engine, in most cases this would not be handy. Howev">Void Framework – Render template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Static files
If you need to include static files in your HTML page (e.g. css, javascript, image, …), you can use the urlfor method with the first parameter static_file or static_webjar and the second parameter the path to the file.

Example
controller/HomeController.java
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Static files
If you need to include static files in your HTML page (e.g. css, javascript, image, …), you can use the urlfor method with the first parameter static_file or static_webjar and the second parameter the path to the file.

Example
controller/HomeController.java
@Singleton
 @WebController
 public class HomeController {
 
diff --git a/doc/web/security-csrf/index.html b/doc/web/security-csrf/index.html
index ae78303..b6d6653 100644
--- a/doc/web/security-csrf/index.html
+++ b/doc/web/security-csrf/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is recommended tha">Void Framework – CSRF
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
 It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP.
Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/security-headers/index.html b/doc/web/security-headers/index.html
index 623494e..a39b5e6 100644
--- a/doc/web/security-headers/index.html
+++ b/doc/web/security-headers/index.html
@@ -2,7 +2,7 @@
 Configuration The following configuration keys can be used in the configuration">Void Framework – Security headers
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
 You can disable one of the headers by assigning the value null. The header will then not be sent.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/session/index.html b/doc/web/session/index.html
index 29c5948..0129cae 100644
--- a/doc/web/session/index.html
+++ b/doc/web/session/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the session is not stored on the server side, but on the client side v">Void Framework – Session
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
 Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie.

Because session is implemented using cookies, there are some implications.The data size is limited to 4 KiB
Only string can be stored

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.

Read value
You can access the session data via the Context. Methods get or getOrDefault can be used.
@Singleton
 @WebController
 public class Controller {
diff --git a/doc/web/using-web/index.html b/doc/web/using-web/index.html
index a1c742b..7a6f708 100644
--- a/doc/web/using-web/index.html
+++ b/doc/web/using-web/index.html
@@ -2,10 +2,10 @@
 Installation To enable this module, just add following lines to the pom.xml ">Void Framework – Using Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.6.1</version>
+    <version>1.7.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used.
Base
voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly. The default value is 15 seconds.
voidframework.web.errorHandler the implementation of the error handler to use in case of http error. The default value is dev.voidframework.web.http.errorhandler.DefaultErrorHandler.
voidframework.web.contextPath the default context path root. The default value is /.
voidframework.web.routes a list of routing definition classes (must implement the interface AppRoutesDefinition). The default value is [].
voidframework.web.globalFilters a list of routing global filter classes (must implement the interface Filter). The default value is [].
voidframework.web.baseAssetResourcesDirectory the default location of static files in the “resources” directory. The default value is static.
Server
voidframework.web.server.idleTimeout the time without any request to wait before the connection is closed. The default value is 30 seconds.
voidframework.web.server.extraWebServerConfiguration the implementation of the interface ExtraWebServerConfiguration to apply a custom configuration to the Undertow web server. The default value is null.
voidframework.web.server.ioThreads the number of I/O threads. If not specified (value = null or 0), Math.max(Runtime.getRuntime().availableProcessors(), 2) value will be used. The default value is null.
voidframework.web.server.workerThreads the number of Worker threads. If not specified (value = null or 0), ioThreadsNumber * 8 value will be used. The default value is null.
voidframework.web.server.maxBodySize the max body content size. The default value is 1 MiB.
voidframework.web.server.fileSizeThreshold the maximum size allowed in memory before the uploaded file was stored on the disk rather than in memory. The default value is 256 KiB.
voidframework.web.server.tempFileLocation the location where temporary files will be stored. The default value is null (default Java temporary folder).
HTTP
voidframework.web.server.http.listenHost the interface on which the server will listen for non-secure HTTP requests. The default value is 127.0.0.1.
voidframework.web.server.http.listenPort the port on which the server will listen for non-secure HTTP requests. The default value is 9000.
HTTPS
voidframework.web.server.https.listenHost the interface on which the server will listen for HTTPS requests. The default value is 127.0.0.1.
voidframework.web.server.https.listenPort the port on which the server will listen for HTTPS requests. The default value is 9001.
voidframework.web.server.https.ssl.protocols the protocols to use. The default value is ["TLSv1.2", "TLSv1.3"].
voidframework.web.server.https.ssl.ciphers the allowed ciphers. If list is empty, all ciphers will be allowed. The default value is [].
voidframework.web.server.https.ssl.keyStorePath the path where is located the key store. Could be a “resources” path, a URL or a simple path. The default value is null.
voidframework.web.server.https.ssl.keyStoreType the type of the key store. The default value is JKS.
voidframework.web.server.https.ssl.keyStorePassword the password to use to open the key store. The default value is null.
voidframework.web.server.https.ssl.keyAlias the alias of the key to use. If “null” the key will be choosen automatically. The default value is null.
voidframework.web.server.https.ssl.keyPassword the key password. The default value is ${voidframework.web.server.https.ssl.keyStorePassword}.
Language
voidframework.web.language.availableLanguages the available languages. The default value is ["en", "fr"].
voidframework.web.language.cookieName the name of the cookie containing the current language. The default value is VOID_LANG.
voidframework.web.language.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.language.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Flash messages
voidframework.web.flashMessages.cookieName the name of the cookie containing the current flash messages. The default value is VOID_FLASH.
voidframework.web.flashMessages.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.flashMessages.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Session
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.
CSRF
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.
Security headers
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/index.xml b/index.xml
index 857b226..1299024 100644
--- a/index.xml
+++ b/index.xml
@@ -1,13 +1,13 @@
-Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -30,10 +30,10 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
@@ -43,9 +43,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -55,15 +55,21 @@ The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Life cyclehttps://voidframework.dev/doc/core/life-cycle/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/life-cycle/Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
-priority is used to define when the method will be called in relation to the others.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
+priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Configuration The following configuration keys can be used in the configuration file of your application:
+voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Configuration The following configuration keys can be used in the configuration file of your application:
+voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-template-freemarker reference.conf voidframework-validation reference.conf voidframework-vfs reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.1 2023-02-24 Fixed HTTP webserver graceful shutdown not honored 1.6.0 2023-02-11 New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.6.1 2023-02-24 Fixed HTTP webserver graceful shutdown not honored 1.6.0 2023-02-11 New Web module can now respond to requests securely via HTTPS New NotInstance validation constraint New Utility class DurationUtils Improved Graceful stop timeout is now a duration (with time unit) Improved Commercial at "@" constant now available in CharConstants and StringConstants classes Improved Annotation RequestVariable can now use fallback value Improved Updated version of all dependencies 1.5.1 2023-01-07 Fixed JavaScript i18n reverse routing name (js_i18n) 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.7.0 2023-XX-XX Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.6.1 2023-02-24 Fixed HTTP webserver graceful shutdown not honored 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.7.0 2023-XX-XX Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.6.1 2023-02-24 Fixed HTTP webserver graceful shutdown not honored 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
@@ -75,7 +81,9 @@ openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment
 Define a Job To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Define a Job To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
-voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -87,19 +95,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.6.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 479cd2d..5533067 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,7 +1,8 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.6.1

+Release notes1.7.0

+2023-XX-XX
Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492)
New Conditional feature RunInDevModeConditionalFeature
New Sendmail module
New Sendmail module implementation Apache Commons Email
New Add @CachePut annotation
Improved Javadoc
Improved HttpClient is now used instead of raw URL connection (Remote Configuration)
Improved Result: method badRequest(final String content, final String contentType)
Improved Updated version of all dependencies
Fixed Transactional annotation multiple calls

1.6.1

 2023-02-24
Fixed HTTP webserver graceful shutdown not honored

1.6.0

 2023-02-11
New Web module can now respond to requests securely via HTTPS
New NotInstance validation constraint
New Utility class DurationUtils
Improved Graceful stop timeout is now a duration (with time unit)
Improved Commercial at "@" constant now available in CharConstants and StringConstants classes
Improved Annotation RequestVariable can now use fallback value
Improved Updated version of all dependencies

1.5.1

 2023-01-07
Fixed JavaScript i18n reverse routing name (js_i18n)

1.5.0

diff --git a/sitemap.xml b/sitemap.xml
index c9578b1..c241095 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/template/using-template/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/sendmail/https://voidframework.dev/doc/sendmail/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/sendmail/sending-emails/https://voidframework.dev/doc/sendmail/sending-emails/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/template/using-template/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/
\ No newline at end of file

From 270597b8919daab0a54b3cc195a61f9383b6e706 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Sat, 15 Apr 2023 06:20:08 +0000
Subject: [PATCH 44/75] Automated website build

---
 index.xml               | 2 +-
 releasenotes/index.html | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.xml b/index.xml
index 1299024..285efd3 100644
--- a/index.xml
+++ b/index.xml
@@ -69,7 +69,7 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.7.0 2023-XX-XX Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.6.1 2023-02-24 Fixed HTTP webserver graceful shutdown not honored 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.7.0 2023-XX-XX Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.6.1 2023-02-24 Fixed HTTP webserver graceful shutdown not honored 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.6.1 2023-02-24 Fixed HTTP webserver graceful shutdown not honored 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.6.1 2023-02-24 Fixed HTTP webserver graceful shutdown not honored 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 5533067..ef33d3a 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,8 +1,8 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
 Release notes
1.7.0

-2023-XX-XX
Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492)
New Conditional feature RunInDevModeConditionalFeature
New Sendmail module
New Sendmail module implementation Apache Commons Email
New Add @CachePut annotation
Improved Javadoc
Improved HttpClient is now used instead of raw URL connection (Remote Configuration)
Improved Result: method badRequest(final String content, final String contentType)
Improved Updated version of all dependencies
Fixed Transactional annotation multiple calls

1.6.1

+2023-04-12
Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492)
New Conditional feature RunInDevModeConditionalFeature
New Sendmail module
New Sendmail module implementation Apache Commons Email
New Add @CachePut annotation
Improved Javadoc
Improved HttpClient is now used instead of raw URL connection (Remote Configuration)
Improved Result: method badRequest(final String content, final String contentType)
Improved Updated version of all dependencies
Fixed Transactional annotation multiple calls

1.6.1

 2023-02-24
Fixed HTTP webserver graceful shutdown not honored

1.6.0

 2023-02-11
New Web module can now respond to requests securely via HTTPS
New NotInstance validation constraint
New Utility class DurationUtils
Improved Graceful stop timeout is now a duration (with time unit)
Improved Commercial at "@" constant now available in CharConstants and StringConstants classes
Improved Annotation RequestVariable can now use fallback value
Improved Updated version of all dependencies

1.5.1

 2023-01-07
Fixed JavaScript i18n reverse routing name (js_i18n)

1.5.0


From 93fd6b3d3b038cf723adefa24b97983f5d0a5815 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Fri, 21 Apr 2023 17:57:12 +0000
Subject: [PATCH 45/75] Automated website build

---
 doc/core/conditional-feature/index.html | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/doc/core/conditional-feature/index.html b/doc/core/conditional-feature/index.html
index d8f3120..281ba4a 100644
--- a/doc/core/conditional-feature/index.html
+++ b/doc/core/conditional-feature/index.html
@@ -10,6 +10,26 @@
 @ConfigurationConditionalFeature("feature.name")
 public final class SampleController {
 }
+

@RunInDevModeConditionalFeature
The @RunInDevModeConditionalFeature annotation allows a feature to be enabled only if the dev mode is set to true.
Exemple
@WebController
+@RunInDev
+public final class SampleController {
+}
+

Creating your own condition
To create your own condition, simply implement the Condition interface and use this new implementation with the @ConditionalFeature annotation. You can also create your own annotation if you wish.
Exemple
public class RunInDevModeCondition implements Condition {
+
+    @Override
+    public boolean isEnabled(final Config configuration,
+                             final Class<?> annotatedClassType,
+                             final AnnotationMetadata annotationMetadata) {
+
+        return configuration.getBoolean("voidframework.core.runInDevMode");
+    }
+}
+
@Documented
+@Target(ElementType.TYPE)
+@Retention(RetentionPolicy.RUNTIME)
+@ConditionalFeature(RunInDevModeCondition.class)
+public @interface RunInDevModeConditionalFeature {
+}
 

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 

From 624434d4923d933741a26f7bef32297104dbaea1 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 18 May 2023 09:48:41 +0000
Subject: [PATCH 46/75] Automated website build

---
 doc/advanced/advanced/index.html              |  2 +-
 doc/advanced/creating-module/index.html       | 29 +++++++++++++++++++
 doc/advanced/index.html                       |  2 +-
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/index.html                          |  2 +-
 doc/cache/redis-cache/index.html              |  2 +-
 doc/cache/using-cache/index.html              |  2 +-
 doc/core/boot-sequence/index.html             |  2 +-
 doc/core/class-scanning/index.html            |  8 ++---
 doc/core/conditional-feature/index.html       |  2 +-
 doc/core/configuration/index.html             |  2 +-
 doc/core/index.html                           |  2 +-
 doc/core/lang/index.html                      |  2 +-
 doc/core/life-cycle/index.html                |  2 +-
 doc/core/type-conversion/index.html           |  2 +-
 doc/getting-started/index.html                |  2 +-
 .../new-application/index.html                |  2 +-
 doc/getting-started/requirements/index.html   |  2 +-
 .../upgrading-from-old-version/index.html     |  2 +-
 doc/i18n/index.html                           |  2 +-
 doc/index.html                                |  2 +-
 doc/index.xml                                 | 26 ++++++++++++-----
 .../using-i18n/index.html                     |  2 +-
 doc/nosql-databases/index.html                |  2 +-
 doc/nosql-databases/redis/index.html          |  2 +-
 .../datasource/index.html                     |  2 +-
 doc/relational-databases/h2/index.html        | 14 +++++++++
 doc/relational-databases/index.html           |  2 +-
 .../persistence-hibernate/index.html          |  2 +-
 .../persistence-jooq/index.html               |  2 +-
 .../transactional/index.html                  |  2 +-
 doc/scheduler/index.html                      |  2 +-
 doc/scheduler/scheduling-job-cron/index.html  |  7 ++++-
 doc/sendmail/index.html                       |  2 +-
 .../mailer-apache-commons-email/index.html    |  2 +-
 doc/sendmail/mailer-dummy/index.html          |  9 ++++++
 doc/sendmail/sending-emails/index.html        |  2 +-
 doc/template/freemarker/index.html            |  2 +-
 doc/template/index.html                       |  2 +-
 doc/template/using-template/index.html        |  2 +-
 doc/testing/index.html                        |  2 +-
 doc/testing/junit-extension/index.html        |  2 +-
 doc/vfs/index.html                            |  2 +-
 doc/vfs/using-vfs/index.html                  |  2 +-
 doc/web/controller/index.html                 |  2 +-
 doc/web/filters/index.html                    |  2 +-
 doc/web/index.html                            |  2 +-
 doc/web/render-template/index.html            |  2 +-
 doc/web/security-csrf/index.html              |  2 +-
 doc/web/security-headers/index.html           |  2 +-
 doc/web/session/index.html                    |  2 +-
 doc/web/using-web/index.html                  |  2 +-
 index.xml                                     | 28 +++++++++++++-----
 releasenotes/index.html                       |  5 ++--
 sitemap.xml                                   |  2 +-
 55 files changed, 151 insertions(+), 69 deletions(-)
 create mode 100644 doc/advanced/creating-module/index.html
 create mode 100644 doc/relational-databases/h2/index.html
 create mode 100644 doc/sendmail/mailer-dummy/index.html

diff --git a/doc/advanced/advanced/index.html b/doc/advanced/advanced/index.html
index 75d3cc6..31e4e64 100644
--- a/doc/advanced/advanced/index.html
+++ b/doc/advanced/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – reference.conf
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-sendmail reference.conf
voidframework-sendmail-commonsemail reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-sendmail reference.conf
voidframework-sendmail-commonsemail reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/advanced/creating-module/index.html b/doc/advanced/creating-module/index.html
new file mode 100644
index 0000000..202af3b
--- /dev/null
+++ b/doc/advanced/creating-module/index.html
@@ -0,0 +1,29 @@
+Void Framework – Creating Module
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Creating Module
Do you want to create a Guice module that will be loaded when your application starts? Nothing could be simpler than creating an implementation of the abstract class AbstractModule or the interface Module.
To meet all needs, the Void Framework provides the ability to obtain additional information via the module’s constructor. As a constructor’s parameter, you could optionally use the following elements:
Config the current configuration of the application
ScannedClassesToLoad the classes that were scanned when the application started
In the event that one module needs to be loaded before another, you can use the OrderedModule annotation.

Example
@OrderedModule(priority = 50)
+public final class MyCustomModule extends AbstractModule {
+
+    private final Config configuration;
+    private final ScannedClassesToLoad scannedClassesToLoad;
+
+    public MyCustomModule(final Config configuration,
+                          final ScannedClassesToLoad scannedClassesToLoad) {
+
+        this.configuration = configuration;
+        this.scannedClassesToLoad = scannedClassesToLoad;
+    }
+
+    @Override
+    protected void configure() {
+    
+        // Place your module code here
+    }
+}
+
 
+Remember that the module must be in a path that is scanned when the application starts. If this is not the case, you can add a new path via the configuration key voidframework.core.acceptedScanPaths.

© 2022-2023 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/advanced/index.html b/doc/advanced/index.html
index 924b4c5..b608455 100644
--- a/doc/advanced/index.html
+++ b/doc/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – Advanced
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Advanced

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Advanced

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index cfc9baf..0a080e8 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,7 +2,7 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
     <version>1.7.0</version>
diff --git a/doc/cache/index.html b/doc/cache/index.html
index dfdec9f..bc2bdf9 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Cache

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index d846f89..5354588 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.7.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
     <version>1.7.0</version>
diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index e107d18..d41d300 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,7 +2,7 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
 Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

@CachePut
Indicates that the result of the method will be cached regardless value already exists.

Example
@BindClass
 public class CacheExample {
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index 44dbce3..183c0e9 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c . t o u e y a h d i r c l P . u c l r b">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index e3c788a..99b3f65 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -1,11 +1,11 @@
 Void Framework – Class scanning
+Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule C">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
-3 types of elements are recognised during the scan:
Classes extending AbstractModule (Guice)
Classes annotated with Bindable annotation
Classes implementing defined interface

Guice module
Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+3 types of elements are recognised during the scan:
Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule
Classes annotated with Bindable familly annotation
Classes implementing defined interface
Interfaces annotated with Proxyable annotation

Guice module
Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.
 
 If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
-Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@Bindable 
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Defined interface
The configuration key voidframework.core.bindExtraInterfaces is used to define a set of interfaces for which to bind the found implementations. For example, converters are automatically detected in this way via the TypeConverter interface.

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
+Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@Bindable 
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Defined interface
The configuration key voidframework.core.bindExtraInterfaces is used to define a set of interfaces for which to bind the found implementations. For example, converters are automatically detected in this way via the TypeConverter interface.

Proxyable interface
The @Proxyable annotation indicates that the implementation of the annotated interface is a proxy that will be configured by one of the modules that will be loaded when the application starts. The module can retrieve the interface(s) it is interested in via the ScannedClassesToLoad variable provided in the module constructor.

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
     <artifactId>exec-maven-plugin</artifactId>
     <version>3.0.0</version>
diff --git a/doc/core/conditional-feature/index.html b/doc/core/conditional-feature/index.html
index 281ba4a..d16c92f 100644
--- a/doc/core/conditional-feature/index.html
+++ b/doc/core/conditional-feature/index.html
@@ -2,7 +2,7 @@
 @ConditionalFeature The @ConditionalFeature annotation allows a feature to be enabled or">Void Framework – Conditional feature
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Conditional feature
Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.

@ConditionalFeature
The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
The annotation accepts the following parameter:
value is used to define the implementation of Condition interface to use.
Exemple
@WebController
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Conditional feature
Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.

@ConditionalFeature
The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
The annotation accepts the following parameter:
value is used to define the implementation of Condition interface to use.
Exemple
@WebController
 @ConditionalFeature(MyCustomCondition.class)
 public final class SampleController {
 }
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index ee0c7cb..25af6bf 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -1,7 +1,7 @@
 Void Framework – Configuration
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
 

Retrieve configuration value from Java
@Service
 public class MyService {
 
diff --git a/doc/core/index.html b/doc/core/index.html
index 7b74d85..9080906 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Core

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Core

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/lang/index.html b/doc/core/lang/index.html
index 24371ce..fcd99e4 100644
--- a/doc/core/lang/index.html
+++ b/doc/core/lang/index.html
@@ -2,7 +2,7 @@
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get mor">Void Framework – Lang
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Lang
The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.

CUID
CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
// Random CUID
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Lang
The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.

CUID
CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
// Random CUID
 final CUID cuid = CUID.randomCUID();
 
 // CUID from String representating a CUID
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index 354f447..7b168cf 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time (duration or milliseconds) to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index 651c5c8..cc54b39 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index cfd93f8..7aa4fee 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Getting Started

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Getting Started

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 40f518b..61f8068 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,7 +2,7 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
     <version>1.7.0</version>
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index d559bf3..0901f12 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index a09f77e..5e001d8 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.0.0 Initial relea">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.0.0
Initial release

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

1.6.0
Configuration keys voidframework.web.server.listenHost and voidframework.web.server.listenPort have been renamed to voidframework.web.server.http.listenHost and voidframework.web.server.http.listenPort

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.0.0
Initial release

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

1.6.0
Configuration keys voidframework.web.server.listenHost and voidframework.web.server.listenPort have been renamed to voidframework.web.server.http.listenHost and voidframework.web.server.http.listenPort

1.8.0
Guice 7.0 only supports the jakarta.inject, jakarta.servlet and jakarta.persistence namespaces. Read more at https://github.com/google/guice/wiki/Guice700

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index 9f78917..b095112 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Internationalization

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Internationalization

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index e68dcdd..9eb6537 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Documentation

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Documentation

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index d25de51..1396ea0 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -9,8 +9,8 @@ Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
+Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
 @ConditionalFeature The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
 The annotation accepts the following parameter:
 value is used to define the implementation of Condition interface to use.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -22,7 +22,11 @@ Example
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
-Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.CSRFhttps://voidframework.dev/doc/web/security-csrf/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-csrf/Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
+Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Creating Modulehttps://voidframework.dev/doc/advanced/creating-module/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/creating-module/Do you want to create a Guice module that will be loaded when your application starts? Nothing could be simpler than creating an implementation of the abstract class AbstractModule or the interface Module.
+To meet all needs, the Void Framework provides the ability to obtain additional information via the module&rsquo;s constructor. As a constructor&rsquo;s parameter, you could optionally use the following elements:
+Config the current configuration of the application ScannedClassesToLoad the classes that were scanned when the application started In the event that one module needs to be loaded before another, you can use the OrderedModule annotation.Creating Modulehttps://voidframework.dev/doc/advanced/creating-module/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/creating-module/Do you want to create a Guice module that will be loaded when your application starts? Nothing could be simpler than creating an implementation of the abstract class AbstractModule or the interface Module.
+To meet all needs, the Void Framework provides the ability to obtain additional information via the module&rsquo;s constructor. As a constructor&rsquo;s parameter, you could optionally use the following elements:
+Config the current configuration of the application ScannedClassesToLoad the classes that were scanned when the application started In the event that one module needs to be loaded before another, you can use the OrderedModule annotation.CSRFhttps://voidframework.dev/doc/web/security-csrf/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-csrf/Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 &nbsp; It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP. Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.Data sourcehttps://voidframework.dev/doc/relational-databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Installation Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Data sourcehttps://voidframework.dev/doc/relational-databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Installation Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
@@ -35,7 +39,11 @@ Configuration The following configuration keys can be used in the configuration
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
-voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -61,7 +69,9 @@ Configuration The following configuration keys can be used in the configuration
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
-voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
+voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
+Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
+Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
@@ -78,8 +88,10 @@ openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
-Define a Job To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
-Define a Job To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index e747f54..259ac9a 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
     <version>1.7.0</version>
diff --git a/doc/nosql-databases/index.html b/doc/nosql-databases/index.html
index 5295e87..a79cee9 100644
--- a/doc/nosql-databases/index.html
+++ b/doc/nosql-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – NoSQL Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

NoSQL Databases

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

NoSQL Databases

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index 999808c..1403b0e 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -2,7 +2,7 @@
 Installation To enable this module, just add following lines to ">Void Framework – Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
     <version>1.7.0</version>
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index 9f8e03f..895c2e3 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -1,7 +1,7 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
diff --git a/doc/relational-databases/h2/index.html b/doc/relational-databases/h2/index.html
new file mode 100644
index 0000000..3a041d4
--- /dev/null
+++ b/doc/relational-databases/h2/index.html
@@ -0,0 +1,14 @@
+Void Framework – H2
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

H2
H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+    <groupId>dev.voidframework</groupId>
+    <artifactId>voidframework-h2</artifactId>
+    <version>1.7.0</version>
+</dependency>
+

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.h2.webPort the listen port of the H2 console. The default value is 9002.
voidframework.h2.webAdminPassword the password to access preferences and tools of H2 console. The default value is sa.
voidframework.h2.webAllowOthers specifies if other computers are allowed to connect. The default value is false.

Open the web console
Once your application has started, you can access the H2 web console by going to http://127.0.0.1:9002.
 
+Note that H2 web console will be started only if the configuration is run in development mode (voidframework.core.runInDevMode = true).

© 2022-2023 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/relational-databases/index.html b/doc/relational-databases/index.html
index 56a75e3..f140a7e 100644
--- a/doc/relational-databases/index.html
+++ b/doc/relational-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Relational Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Relational Databases

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Relational Databases

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index 28ae3f3..c2e424d 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -2,7 +2,7 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index 6d6f670..73b42e9 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -2,7 +2,7 @@
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provid">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-jooq</artifactId>
     <version>1.7.0</version>
diff --git a/doc/relational-databases/transactional/index.html b/doc/relational-databases/transactional/index.html
index a7b07f6..dac609b 100644
--- a/doc/relational-databases/transactional/index.html
+++ b/doc/relational-databases/transactional/index.html
@@ -1,7 +1,7 @@
 Void Framework – Transactional
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Transactional
It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional (Jakarta) annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Transactional
It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional (Jakarta) annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
 Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
diff --git a/doc/scheduler/index.html b/doc/scheduler/index.html
index 15578a3..8d32ecc 100644
--- a/doc/scheduler/index.html
+++ b/doc/scheduler/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduler
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduler

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Scheduler

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index 4571c6d..b09b23d 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -1,7 +1,12 @@
 Void Framework – Scheduling a local job
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron a CRON-like expression. The default value is empty (disabled).
cronZone the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+    <groupId>dev.voidframework</groupId>
+    <artifactId>voidframework-scheduler</artifactId>
+    <version>1.7.0</version>
+</dependency>
+

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron a CRON-like expression. The default value is empty (disabled).
cronZone the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
 public final class Ping {
 
     private static final Logger LOGGER = LoggerFactory.getLogger(Ping.class);
diff --git a/doc/sendmail/index.html b/doc/sendmail/index.html
index d20918f..53eb75c 100644
--- a/doc/sendmail/index.html
+++ b/doc/sendmail/index.html
@@ -1,7 +1,7 @@
 Void Framework – Sendmail
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Sendmail

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Sendmail

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/sendmail/mailer-apache-commons-email/index.html b/doc/sendmail/mailer-apache-commons-email/index.html
index c95365b..8ff9995 100644
--- a/doc/sendmail/mailer-apache-commons-email/index.html
+++ b/doc/sendmail/mailer-apache-commons-email/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsema">Void Framework – Mailer : Apache Commons Email
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Mailer : Apache Commons Email
This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Mailer : Apache Commons Email
This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail-commonsemail</artifactId>
     <version>1.7.0</version>
diff --git a/doc/sendmail/mailer-dummy/index.html b/doc/sendmail/mailer-dummy/index.html
new file mode 100644
index 0000000..3e5ba7e
--- /dev/null
+++ b/doc/sendmail/mailer-dummy/index.html
@@ -0,0 +1,9 @@
+Void Framework – Mailer : Dummy
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Mailer : Dummy
This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.

Installation
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.

© 2022-2023 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/sendmail/sending-emails/index.html b/doc/sendmail/sending-emails/index.html
index 9912450..5d4bd23 100644
--- a/doc/sendmail/sending-emails/index.html
+++ b/doc/sendmail/sending-emails/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&">Void Framework – Sending emails
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Sending emails
If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Sending emails
If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail</artifactId>
     <version>1.7.0</version>
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index 833d458..c9a3db7 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifact">Void Framework – FreeMarker
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
     <version>1.7.0</version>
diff --git a/doc/template/index.html b/doc/template/index.html
index 8df67e4..83ff9e2 100644
--- a/doc/template/index.html
+++ b/doc/template/index.html
@@ -1,7 +1,7 @@
 Void Framework – Template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Template

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Template

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/template/using-template/index.html b/doc/template/using-template/index.html
index 934b532..4cf1a67 100644
--- a/doc/template/using-template/index.html
+++ b/doc/template/using-template/index.html
@@ -2,7 +2,7 @@
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final Temp">Void Framework – Using template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using template
Sooner or later you will need to generate documents (HTML, PDF…). Void Framework provides all the tools you need!

Example
public class TemplateExample {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using template
Sooner or later you will need to generate documents (HTML, PDF…). Void Framework provides all the tools you need!

Example
public class TemplateExample {
 
     private final TemplateRenderer templateRenderer;
 
diff --git a/doc/testing/index.html b/doc/testing/index.html
index 45dbe6e..1a71538 100644
--- a/doc/testing/index.html
+++ b/doc/testing/index.html
@@ -1,7 +1,7 @@
 Void Framework – Testing
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Testing

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Testing

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index 6ed5532..ecfc754 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -2,7 +2,7 @@
 To enable this module, just add following lines to th">Void Framework – JUnit's extension
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
     <version>1.7.0</version>
diff --git a/doc/vfs/index.html b/doc/vfs/index.html
index 855c1a9..083fc7e 100644
--- a/doc/vfs/index.html
+++ b/doc/vfs/index.html
@@ -1,7 +1,7 @@
 Void Framework – Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Virtual File Storage

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Virtual File Storage

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/vfs/using-vfs/index.html b/doc/vfs/using-vfs/index.html
index 2876904..3030947 100644
--- a/doc/vfs/using-vfs/index.html
+++ b/doc/vfs/using-vfs/index.html
@@ -1,7 +1,7 @@
 Void Framework – Using Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
     <version>1.7.0</version>
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index d492705..1f72ea7 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index 9ae52ef..e5a92ff 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the">Void Framework – Filters
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
 Note that the use of dependencies direct injection is possible in filters.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
 @Singleton
 @WebController
diff --git a/doc/web/index.html b/doc/web/index.html
index c1490eb..9ab5a8a 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Web

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Web

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/render-template/index.html b/doc/web/render-template/index.html
index 28d118a..81fcec6 100644
--- a/doc/web/render-template/index.html
+++ b/doc/web/render-template/index.html
@@ -2,7 +2,7 @@
 Although you can manually use the template engine, in most cases this would not be handy. Howev">Void Framework – Render template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Static files
If you need to include static files in your HTML page (e.g. css, javascript, image, …), you can use the urlfor method with the first parameter static_file or static_webjar and the second parameter the path to the file.

Example
controller/HomeController.java
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Static files
If you need to include static files in your HTML page (e.g. css, javascript, image, …), you can use the urlfor method with the first parameter static_file or static_webjar and the second parameter the path to the file.

Example
controller/HomeController.java
@Singleton
 @WebController
 public class HomeController {
 
diff --git a/doc/web/security-csrf/index.html b/doc/web/security-csrf/index.html
index b6d6653..9710af1 100644
--- a/doc/web/security-csrf/index.html
+++ b/doc/web/security-csrf/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is recommended tha">Void Framework – CSRF
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
 It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP.
Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/security-headers/index.html b/doc/web/security-headers/index.html
index a39b5e6..53c9857 100644
--- a/doc/web/security-headers/index.html
+++ b/doc/web/security-headers/index.html
@@ -2,7 +2,7 @@
 Configuration The following configuration keys can be used in the configuration">Void Framework – Security headers
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
 You can disable one of the headers by assigning the value null. The header will then not be sent.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/session/index.html b/doc/web/session/index.html
index 0129cae..271e561 100644
--- a/doc/web/session/index.html
+++ b/doc/web/session/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the session is not stored on the server side, but on the client side v">Void Framework – Session
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
 Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie.

Because session is implemented using cookies, there are some implications.The data size is limited to 4 KiB
Only string can be stored

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.

Read value
You can access the session data via the Context. Methods get or getOrDefault can be used.
@Singleton
 @WebController
 public class Controller {
diff --git a/doc/web/using-web/index.html b/doc/web/using-web/index.html
index 7a6f708..777c325 100644
--- a/doc/web/using-web/index.html
+++ b/doc/web/using-web/index.html
@@ -2,7 +2,7 @@
 Installation To enable this module, just add following lines to the pom.xml ">Void Framework – Using Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
     <version>1.7.0</version>
diff --git a/index.xml b/index.xml
index 285efd3..670fa10 100644
--- a/index.xml
+++ b/index.xml
@@ -9,8 +9,8 @@ Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Classes extending AbstractModule (Guice) Classes annotated with Bindable annotation Classes implementing defined interface Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
+Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
 @ConditionalFeature The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
 The annotation accepts the following parameter:
 value is used to define the implementation of Condition interface to use.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -22,7 +22,11 @@ Example
 Example
 @Singleton @WebController(prefixRoute = &#34;/account&#34;) public class AccountController { @RequestRoute(route = &#34;/(?&lt;accountId&gt;[a-f0-9]+)&#34;) public Result showAccount(@RequestPath(&#34;accountId&#34;) final String accountId) { return Result.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
-Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.CSRFhttps://voidframework.dev/doc/web/security-csrf/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-csrf/Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
+Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Creating Modulehttps://voidframework.dev/doc/advanced/creating-module/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/creating-module/Do you want to create a Guice module that will be loaded when your application starts? Nothing could be simpler than creating an implementation of the abstract class AbstractModule or the interface Module.
+To meet all needs, the Void Framework provides the ability to obtain additional information via the module&rsquo;s constructor. As a constructor&rsquo;s parameter, you could optionally use the following elements:
+Config the current configuration of the application ScannedClassesToLoad the classes that were scanned when the application started In the event that one module needs to be loaded before another, you can use the OrderedModule annotation.Creating Modulehttps://voidframework.dev/doc/advanced/creating-module/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/creating-module/Do you want to create a Guice module that will be loaded when your application starts? Nothing could be simpler than creating an implementation of the abstract class AbstractModule or the interface Module.
+To meet all needs, the Void Framework provides the ability to obtain additional information via the module&rsquo;s constructor. As a constructor&rsquo;s parameter, you could optionally use the following elements:
+Config the current configuration of the application ScannedClassesToLoad the classes that were scanned when the application started In the event that one module needs to be loaded before another, you can use the OrderedModule annotation.CSRFhttps://voidframework.dev/doc/web/security-csrf/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-csrf/Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 &nbsp; It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP. Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.Data sourcehttps://voidframework.dev/doc/relational-databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Installation Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Data sourcehttps://voidframework.dev/doc/relational-databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Installation Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
@@ -35,7 +39,11 @@ Configuration The following configuration keys can be used in the configuration
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
-voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -61,7 +69,9 @@ Configuration The following configuration keys can be used in the configuration
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
-voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
+voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
+Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
+Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
@@ -69,7 +79,7 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.6.1 2023-02-24 Fixed HTTP webserver graceful shutdown not honored 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.6.1 2023-02-24 Fixed HTTP webserver graceful shutdown not honored 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
@@ -78,8 +88,10 @@ openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
-Define a Job To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
-Define a Job To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
diff --git a/releasenotes/index.html b/releasenotes/index.html
index ef33d3a..aa87447 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,7 +1,8 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.7.0

+Release notes
1.8.0

+2023-05-18
New Proxyable interface
New H2 web console
Improved Bind automatically interface with single implementation
Improved Updated version of all dependencies
Fixed Guice module implementing interface not recognized

1.7.0

 2023-04-12
Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492)
New Conditional feature RunInDevModeConditionalFeature
New Sendmail module
New Sendmail module implementation Apache Commons Email
New Add @CachePut annotation
Improved Javadoc
Improved HttpClient is now used instead of raw URL connection (Remote Configuration)
Improved Result: method badRequest(final String content, final String contentType)
Improved Updated version of all dependencies
Fixed Transactional annotation multiple calls

1.6.1

 2023-02-24
Fixed HTTP webserver graceful shutdown not honored

1.6.0

 2023-02-11
New Web module can now respond to requests securely via HTTPS
New NotInstance validation constraint
New Utility class DurationUtils
Improved Graceful stop timeout is now a duration (with time unit)
Improved Commercial at "@" constant now available in CharConstants and StringConstants classes
Improved Annotation RequestVariable can now use fallback value
Improved Updated version of all dependencies

1.5.1

diff --git a/sitemap.xml b/sitemap.xml
index c241095..8947309 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/sendmail/https://voidframework.dev/doc/sendmail/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/sendmail/sending-emails/https://voidframework.dev/doc/sendmail/sending-emails/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/template/using-template/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/sendmail/https://voidframework.dev/doc/sendmail/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/advanced/creating-module/https://voidframework.dev/doc/advanced/creating-module/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/h2/https://voidframework.dev/doc/relational-databases/h2/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/https://voidframework.dev/doc/sendmail/mailer-dummy/https://voidframework.dev/doc/sendmail/mailer-dummy/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/sendmail/sending-emails/https://voidframework.dev/doc/sendmail/sending-emails/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/template/using-template/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/
\ No newline at end of file

From 539cc5ac7c66d7b1f4483a3ea29b5f8f06fa5371 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 18 May 2023 09:51:25 +0000
Subject: [PATCH 47/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/redis-cache/index.html              |  4 +-
 doc/core/configuration/index.html             |  4 +-
 .../new-application/index.html                |  4 +-
 doc/index.xml                                 | 44 +++++++++----------
 .../using-i18n/index.html                     |  2 +-
 doc/nosql-databases/redis/index.html          |  4 +-
 .../datasource/index.html                     |  4 +-
 doc/relational-databases/h2/index.html        |  2 +-
 .../persistence-hibernate/index.html          |  2 +-
 .../persistence-jooq/index.html               |  2 +-
 doc/scheduler/scheduling-job-cron/index.html  |  2 +-
 .../mailer-apache-commons-email/index.html    |  2 +-
 doc/sendmail/sending-emails/index.html        |  2 +-
 doc/template/freemarker/index.html            |  2 +-
 doc/testing/junit-extension/index.html        |  2 +-
 doc/vfs/using-vfs/index.html                  |  2 +-
 doc/web/using-web/index.html                  |  2 +-
 index.xml                                     | 44 +++++++++----------
 19 files changed, 66 insertions(+), 66 deletions(-)

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 0a080e8..b4122f8 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 5354588..dada2fb 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -1,11 +1,11 @@
 Void Framework – Cache engine : Redis
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index 25af6bf..1593bd7 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -25,7 +25,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.7.0</version>
+  <version>1.8.0</version>
 </dependency>
 
voidframework {
     code {
@@ -60,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.7.0</version>
+  <version>1.8.0</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 61f8068..f4fe264 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/index.xml b/doc/index.xml
index 1396ea0..89da28b 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,13 +1,13 @@
 Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -34,16 +34,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -51,9 +51,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -64,19 +64,19 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -94,8 +94,8 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -107,19 +107,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 259ac9a..7febf2b 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index 1403b0e..dbc965c 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 

Example
@Service
 public final class ExampleService {
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index 895c2e3..32af6da 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -5,12 +5,12 @@
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/relational-databases/h2/index.html b/doc/relational-databases/h2/index.html
index 3a041d4..432f38c 100644
--- a/doc/relational-databases/h2/index.html
+++ b/doc/relational-databases/h2/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

H2
H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-h2</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.h2.webPort the listen port of the H2 console. The default value is 9002.
voidframework.h2.webAdminPassword the password to access preferences and tools of H2 console. The default value is sa.
voidframework.h2.webAllowOthers specifies if other computers are allowed to connect. The default value is false.

Open the web console
Once your application has started, you can access the H2 web console by going to http://127.0.0.1:9002.
 
 Note that H2 web console will be started only if the configuration is run in development mode (voidframework.core.runInDevMode = true).

© 2022-2023 Void Framework

diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index c2e424d..bd9366d 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -6,7 +6,7 @@
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 

Working with transaction manually
final EntityManager entityManager = this.entityManagerProvider.get();
 final EntityTransaction transaction = entityManager.getTransaction();
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index 73b42e9..6e6ca41 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-jooq</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 

Generator
To work, jOOQ needs files generated during the compilation of the project. It is possible to generate the required classes in different ways (scan database, scan entity, …). For more information, please visit the official jOOQ website.
To enable code generation, add & customize the code below.
pom.xml
<build>
     <plugins>
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index b09b23d..0d7ee29 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-scheduler</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron a CRON-like expression. The default value is empty (disabled).
cronZone the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
 public final class Ping {
diff --git a/doc/sendmail/mailer-apache-commons-email/index.html b/doc/sendmail/mailer-apache-commons-email/index.html
index 8ff9995..b8a0e96 100644
--- a/doc/sendmail/mailer-apache-commons-email/index.html
+++ b/doc/sendmail/mailer-apache-commons-email/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Mailer : Apache Commons Email
This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail-commonsemail</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.commonsemail.username user name for authentication. The default value is null.
voidframework.sendmail.commonsemail.password password for authentication. The default value is null.
This module also includes many of the configuration keys of the Java Mail properties. To use it, simply prefix them with voidframework.sendmail.commonsemail.. Here is the list of possible properties:
https://javaee.github.io/javamail/docs/api/javax/mail/internet/package-summary.html
mail.mime.address.usecanonicalhostname
mail.mime.allowencodedmessages
mail.mime.applefilenames
mail.mime.base64.ignoreerrors
mail.mime.charset
mail.mime.contenttypehandler
mail.mime.decodefilename
mail.mime.decodeparameters
mail.mime.decodetext.strict
mail.mime.encodeeol.strict
mail.mime.encodefilename
mail.mime.encodeparameters
mail.mime.foldtext
mail.mime.ignoremultipartencoding
mail.mime.ignoreunknownencoding
mail.mime.ignorewhitespacelines
mail.mime.multipart.allowempty
mail.mime.multipart.ignoreexistingboundaryparameter
mail.mime.multipart.ignoremissingboundaryparameter
mail.mime.multipart.ignoremissingendboundary
mail.mime.parameters.strict
mail.mime.setcontenttypefilename
mail.mime.setdefaulttextcharset
mail.mime.uudecode.ignoreerrors
mail.mime.uudecode.ignoremissingbeginend
mail.mime.windowsfilenames
https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html
mail.smtp.user
mail.smtp.host
mail.smtp.port
mail.smtp.connectiontimeout
mail.smtp.timeout
mail.smtp.writetimeout
mail.smtp.from
mail.smtp.localhost
mail.smtp.localaddress
mail.smtp.localport
mail.smtp.ehlo
mail.smtp.auth
mail.smtp.auth.mechanisms
mail.smtp.auth.login.disable
mail.smtp.auth.plain.disable
mail.smtp.auth.digest-md5.disable
mail.smtp.auth.ntlm.disable
mail.smtp.auth.ntlm.domain
mail.smtp.auth.ntlm.flags
mail.smtp.auth.xoauth2.disable
mail.smtp.submitter
mail.smtp.dsn.notify
mail.smtp.dsn.ret
mail.smtp.allow8bitmime
mail.smtp.sendpartial
mail.smtp.sasl.enable
mail.smtp.sasl.mechanisms
mail.smtp.sasl.authorizationid
mail.smtp.sasl.realm
mail.smtp.sasl.usecanonicalhostname
mail.smtp.quitwait
mail.smtp.reportsuccess
mail.smtp.socketFactory
mail.smtp.socketFactory.class
mail.smtp.socketFactory.fallback
mail.smtp.socketFactory.port
mail.smtp.ssl.enable
mail.smtp.ssl.checkserveridentity
mail.smtp.ssl.trust
mail.smtp.ssl.socketFactory
mail.smtp.ssl.socketFactory.class
mail.smtp.ssl.socketFactory.port
mail.smtp.ssl.protocols
mail.smtp.ssl.ciphersuites
mail.smtp.starttls.enable
mail.smtp.starttls.required
mail.smtp.proxy.host
mail.smtp.proxy.port
mail.smtp.proxy.user
mail.smtp.proxy.password
mail.smtp.socks.host
mail.smtp.socks.port
mail.smtp.mailextension
mail.smtp.userset
mail.smtp.noop.strict

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/sendmail/sending-emails/index.html b/doc/sendmail/sending-emails/index.html
index 5d4bd23..383f61c 100644
--- a/doc/sendmail/sending-emails/index.html
+++ b/doc/sendmail/sending-emails/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Sending emails
If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 
In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail module

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.engine the mailer implementation to use. The default value is null.
voidframework.sendmail.mailQueuePollTimeout the time to wait before giving up when retrieving a mail to be sent from the queue of mail waiting to be sent when the queue is empty. The default value is 2 seconds.
voidframework.sendmail.gracefulStopTimeout the time for the daemon to shut down properly before it was terminated. The default value is 15 seconds.

Examples
@BindClass
 public final class Service {
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index c9a3db7..6c7b148 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index ecfc754..78160c1 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
 @ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
diff --git a/doc/vfs/using-vfs/index.html b/doc/vfs/using-vfs/index.html
index 3030947..0ec006e 100644
--- a/doc/vfs/using-vfs/index.html
+++ b/doc/vfs/using-vfs/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 

Configuration
Different VirtualFileStorage implementations must be configured in voidframework.vfs namespace. The following configuration keys can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
 Note that each implementation can have extra configuration keys.

Example
voidframework {
diff --git a/doc/web/using-web/index.html b/doc/web/using-web/index.html
index 777c325..4cf7014 100644
--- a/doc/web/using-web/index.html
+++ b/doc/web/using-web/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.7.0</version>
+    <version>1.8.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used.
Base
voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly. The default value is 15 seconds.
voidframework.web.errorHandler the implementation of the error handler to use in case of http error. The default value is dev.voidframework.web.http.errorhandler.DefaultErrorHandler.
voidframework.web.contextPath the default context path root. The default value is /.
voidframework.web.routes a list of routing definition classes (must implement the interface AppRoutesDefinition). The default value is [].
voidframework.web.globalFilters a list of routing global filter classes (must implement the interface Filter). The default value is [].
voidframework.web.baseAssetResourcesDirectory the default location of static files in the “resources” directory. The default value is static.
Server
voidframework.web.server.idleTimeout the time without any request to wait before the connection is closed. The default value is 30 seconds.
voidframework.web.server.extraWebServerConfiguration the implementation of the interface ExtraWebServerConfiguration to apply a custom configuration to the Undertow web server. The default value is null.
voidframework.web.server.ioThreads the number of I/O threads. If not specified (value = null or 0), Math.max(Runtime.getRuntime().availableProcessors(), 2) value will be used. The default value is null.
voidframework.web.server.workerThreads the number of Worker threads. If not specified (value = null or 0), ioThreadsNumber * 8 value will be used. The default value is null.
voidframework.web.server.maxBodySize the max body content size. The default value is 1 MiB.
voidframework.web.server.fileSizeThreshold the maximum size allowed in memory before the uploaded file was stored on the disk rather than in memory. The default value is 256 KiB.
voidframework.web.server.tempFileLocation the location where temporary files will be stored. The default value is null (default Java temporary folder).
HTTP
voidframework.web.server.http.listenHost the interface on which the server will listen for non-secure HTTP requests. The default value is 127.0.0.1.
voidframework.web.server.http.listenPort the port on which the server will listen for non-secure HTTP requests. The default value is 9000.
HTTPS
voidframework.web.server.https.listenHost the interface on which the server will listen for HTTPS requests. The default value is 127.0.0.1.
voidframework.web.server.https.listenPort the port on which the server will listen for HTTPS requests. The default value is 9001.
voidframework.web.server.https.ssl.protocols the protocols to use. The default value is ["TLSv1.2", "TLSv1.3"].
voidframework.web.server.https.ssl.ciphers the allowed ciphers. If list is empty, all ciphers will be allowed. The default value is [].
voidframework.web.server.https.ssl.keyStorePath the path where is located the key store. Could be a “resources” path, a URL or a simple path. The default value is null.
voidframework.web.server.https.ssl.keyStoreType the type of the key store. The default value is JKS.
voidframework.web.server.https.ssl.keyStorePassword the password to use to open the key store. The default value is null.
voidframework.web.server.https.ssl.keyAlias the alias of the key to use. If “null” the key will be choosen automatically. The default value is null.
voidframework.web.server.https.ssl.keyPassword the key password. The default value is ${voidframework.web.server.https.ssl.keyStorePassword}.
Language
voidframework.web.language.availableLanguages the available languages. The default value is ["en", "fr"].
voidframework.web.language.cookieName the name of the cookie containing the current language. The default value is VOID_LANG.
voidframework.web.language.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.language.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Flash messages
voidframework.web.flashMessages.cookieName the name of the cookie containing the current flash messages. The default value is VOID_FLASH.
voidframework.web.flashMessages.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.flashMessages.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Session
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.
CSRF
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.
Security headers
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/index.xml b/index.xml
index 670fa10..72f9d50 100644
--- a/index.xml
+++ b/index.xml
@@ -1,13 +1,13 @@
 Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -34,16 +34,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -51,9 +51,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -64,19 +64,19 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -94,8 +94,8 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -107,19 +107,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.7.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file

From 463b9a4eda8f4c6e644cb3ebc05390cd7e3b5f6f Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Tue, 23 May 2023 19:37:44 +0000
Subject: [PATCH 48/75] Automated website build

---
 doc/relational-databases/h2/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/relational-databases/h2/index.html b/doc/relational-databases/h2/index.html
index 432f38c..1e44746 100644
--- a/doc/relational-databases/h2/index.html
+++ b/doc/relational-databases/h2/index.html
@@ -7,7 +7,7 @@
     <version>1.8.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.h2.webPort the listen port of the H2 console. The default value is 9002.
voidframework.h2.webAdminPassword the password to access preferences and tools of H2 console. The default value is sa.
voidframework.h2.webAllowOthers specifies if other computers are allowed to connect. The default value is false.

Open the web console
Once your application has started, you can access the H2 web console by going to http://127.0.0.1:9002.
 
-Note that H2 web console will be started only if the configuration is run in development mode (voidframework.core.runInDevMode = true).

© 2022-2023 Void Framework

+Note that H2 web console will be started only if the application is run in development mode (voidframework.core.runInDevMode = true).

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 

From 95e043ccbe9e8664dc2974df6dbafcdc69ecc373 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Fri, 26 May 2023 17:42:03 +0000
Subject: [PATCH 49/75] Automated website build

---
 doc/cache/using-cache/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index d41d300..1ec614c 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -4,7 +4,7 @@
    
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
-Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

@CachePut
Indicates that the result of the method will be cached regardless value already exists.

Example
@BindClass
+Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

@CachePut
Indicates that the result of the method will be cached regardless value already exists.
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
 
     @CachePut

From 4552ee7f2d78cfbe75e2d357817a5f44fcc931a5 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Fri, 16 Jun 2023 17:49:41 +0000
Subject: [PATCH 50/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/redis-cache/index.html              |  2 +-
 doc/core/configuration/index.html             |  4 +-
 .../new-application/index.html                |  4 +-
 doc/index.xml                                 | 44 +++++++++---------
 .../using-i18n/index.html                     |  2 +-
 doc/nosql-databases/redis/index.html          |  4 +-
 .../datasource/index.html                     |  4 +-
 doc/relational-databases/h2/index.html        |  2 +-
 .../persistence-hibernate/index.html          |  2 +-
 .../persistence-jooq/index.html               |  2 +-
 doc/scheduler/scheduling-job-cron/index.html  |  2 +-
 .../mailer-apache-commons-email/index.html    |  2 +-
 doc/sendmail/sending-emails/index.html        |  2 +-
 doc/template/freemarker/index.html            |  2 +-
 doc/testing/junit-extension/index.html        |  2 +-
 doc/vfs/using-vfs/index.html                  |  2 +-
 doc/web/using-web/index.html                  |  2 +-
 index.xml                                     | 46 +++++++++----------
 releasenotes/index.html                       |  5 +-
 20 files changed, 69 insertions(+), 68 deletions(-)

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index b4122f8..e51ea91 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index dada2fb..e31b4e7 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index 1593bd7..c2d8824 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -25,7 +25,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.8.0</version>
+  <version>1.8.1</version>
 </dependency>
 
voidframework {
     code {
@@ -60,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.8.0</version>
+  <version>1.8.1</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index f4fe264..7c942be 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/index.xml b/doc/index.xml
index 89da28b..f24689a 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,13 +1,13 @@
 Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -34,16 +34,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -51,9 +51,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -64,19 +64,19 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -94,8 +94,8 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -107,19 +107,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 7febf2b..f352240 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index dbc965c..54afcee 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 

Example
@Service
 public final class ExampleService {
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index 32af6da..5c0f43b 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -5,12 +5,12 @@
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/relational-databases/h2/index.html b/doc/relational-databases/h2/index.html
index 1e44746..98eb06f 100644
--- a/doc/relational-databases/h2/index.html
+++ b/doc/relational-databases/h2/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

H2
H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-h2</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.h2.webPort the listen port of the H2 console. The default value is 9002.
voidframework.h2.webAdminPassword the password to access preferences and tools of H2 console. The default value is sa.
voidframework.h2.webAllowOthers specifies if other computers are allowed to connect. The default value is false.

Open the web console
Once your application has started, you can access the H2 web console by going to http://127.0.0.1:9002.
 
 Note that H2 web console will be started only if the application is run in development mode (voidframework.core.runInDevMode = true).

© 2022-2023 Void Framework

diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index bd9366d..6b43b79 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -6,7 +6,7 @@
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 

Working with transaction manually
final EntityManager entityManager = this.entityManagerProvider.get();
 final EntityTransaction transaction = entityManager.getTransaction();
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index 6e6ca41..ec5c83d 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-jooq</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 

Generator
To work, jOOQ needs files generated during the compilation of the project. It is possible to generate the required classes in different ways (scan database, scan entity, …). For more information, please visit the official jOOQ website.
To enable code generation, add & customize the code below.
pom.xml
<build>
     <plugins>
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index 0d7ee29..7817fc7 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-scheduler</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron a CRON-like expression. The default value is empty (disabled).
cronZone the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
 public final class Ping {
diff --git a/doc/sendmail/mailer-apache-commons-email/index.html b/doc/sendmail/mailer-apache-commons-email/index.html
index b8a0e96..1ec8148 100644
--- a/doc/sendmail/mailer-apache-commons-email/index.html
+++ b/doc/sendmail/mailer-apache-commons-email/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Mailer : Apache Commons Email
This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail-commonsemail</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.commonsemail.username user name for authentication. The default value is null.
voidframework.sendmail.commonsemail.password password for authentication. The default value is null.
This module also includes many of the configuration keys of the Java Mail properties. To use it, simply prefix them with voidframework.sendmail.commonsemail.. Here is the list of possible properties:
https://javaee.github.io/javamail/docs/api/javax/mail/internet/package-summary.html
mail.mime.address.usecanonicalhostname
mail.mime.allowencodedmessages
mail.mime.applefilenames
mail.mime.base64.ignoreerrors
mail.mime.charset
mail.mime.contenttypehandler
mail.mime.decodefilename
mail.mime.decodeparameters
mail.mime.decodetext.strict
mail.mime.encodeeol.strict
mail.mime.encodefilename
mail.mime.encodeparameters
mail.mime.foldtext
mail.mime.ignoremultipartencoding
mail.mime.ignoreunknownencoding
mail.mime.ignorewhitespacelines
mail.mime.multipart.allowempty
mail.mime.multipart.ignoreexistingboundaryparameter
mail.mime.multipart.ignoremissingboundaryparameter
mail.mime.multipart.ignoremissingendboundary
mail.mime.parameters.strict
mail.mime.setcontenttypefilename
mail.mime.setdefaulttextcharset
mail.mime.uudecode.ignoreerrors
mail.mime.uudecode.ignoremissingbeginend
mail.mime.windowsfilenames
https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html
mail.smtp.user
mail.smtp.host
mail.smtp.port
mail.smtp.connectiontimeout
mail.smtp.timeout
mail.smtp.writetimeout
mail.smtp.from
mail.smtp.localhost
mail.smtp.localaddress
mail.smtp.localport
mail.smtp.ehlo
mail.smtp.auth
mail.smtp.auth.mechanisms
mail.smtp.auth.login.disable
mail.smtp.auth.plain.disable
mail.smtp.auth.digest-md5.disable
mail.smtp.auth.ntlm.disable
mail.smtp.auth.ntlm.domain
mail.smtp.auth.ntlm.flags
mail.smtp.auth.xoauth2.disable
mail.smtp.submitter
mail.smtp.dsn.notify
mail.smtp.dsn.ret
mail.smtp.allow8bitmime
mail.smtp.sendpartial
mail.smtp.sasl.enable
mail.smtp.sasl.mechanisms
mail.smtp.sasl.authorizationid
mail.smtp.sasl.realm
mail.smtp.sasl.usecanonicalhostname
mail.smtp.quitwait
mail.smtp.reportsuccess
mail.smtp.socketFactory
mail.smtp.socketFactory.class
mail.smtp.socketFactory.fallback
mail.smtp.socketFactory.port
mail.smtp.ssl.enable
mail.smtp.ssl.checkserveridentity
mail.smtp.ssl.trust
mail.smtp.ssl.socketFactory
mail.smtp.ssl.socketFactory.class
mail.smtp.ssl.socketFactory.port
mail.smtp.ssl.protocols
mail.smtp.ssl.ciphersuites
mail.smtp.starttls.enable
mail.smtp.starttls.required
mail.smtp.proxy.host
mail.smtp.proxy.port
mail.smtp.proxy.user
mail.smtp.proxy.password
mail.smtp.socks.host
mail.smtp.socks.port
mail.smtp.mailextension
mail.smtp.userset
mail.smtp.noop.strict

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/sendmail/sending-emails/index.html b/doc/sendmail/sending-emails/index.html
index 383f61c..0ca9756 100644
--- a/doc/sendmail/sending-emails/index.html
+++ b/doc/sendmail/sending-emails/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Sending emails
If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 
In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail module

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.engine the mailer implementation to use. The default value is null.
voidframework.sendmail.mailQueuePollTimeout the time to wait before giving up when retrieving a mail to be sent from the queue of mail waiting to be sent when the queue is empty. The default value is 2 seconds.
voidframework.sendmail.gracefulStopTimeout the time for the daemon to shut down properly before it was terminated. The default value is 15 seconds.

Examples
@BindClass
 public final class Service {
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index 6c7b148..0b53141 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index 78160c1..4f9a14d 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
 @ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
diff --git a/doc/vfs/using-vfs/index.html b/doc/vfs/using-vfs/index.html
index 0ec006e..14d15d8 100644
--- a/doc/vfs/using-vfs/index.html
+++ b/doc/vfs/using-vfs/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 

Configuration
Different VirtualFileStorage implementations must be configured in voidframework.vfs namespace. The following configuration keys can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
 Note that each implementation can have extra configuration keys.

Example
voidframework {
diff --git a/doc/web/using-web/index.html b/doc/web/using-web/index.html
index 4cf7014..edabb1c 100644
--- a/doc/web/using-web/index.html
+++ b/doc/web/using-web/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.8.0</version>
+    <version>1.8.1</version>
 </dependency>
 

Configuration
The following configuration keys can be used.
Base
voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly. The default value is 15 seconds.
voidframework.web.errorHandler the implementation of the error handler to use in case of http error. The default value is dev.voidframework.web.http.errorhandler.DefaultErrorHandler.
voidframework.web.contextPath the default context path root. The default value is /.
voidframework.web.routes a list of routing definition classes (must implement the interface AppRoutesDefinition). The default value is [].
voidframework.web.globalFilters a list of routing global filter classes (must implement the interface Filter). The default value is [].
voidframework.web.baseAssetResourcesDirectory the default location of static files in the “resources” directory. The default value is static.
Server
voidframework.web.server.idleTimeout the time without any request to wait before the connection is closed. The default value is 30 seconds.
voidframework.web.server.extraWebServerConfiguration the implementation of the interface ExtraWebServerConfiguration to apply a custom configuration to the Undertow web server. The default value is null.
voidframework.web.server.ioThreads the number of I/O threads. If not specified (value = null or 0), Math.max(Runtime.getRuntime().availableProcessors(), 2) value will be used. The default value is null.
voidframework.web.server.workerThreads the number of Worker threads. If not specified (value = null or 0), ioThreadsNumber * 8 value will be used. The default value is null.
voidframework.web.server.maxBodySize the max body content size. The default value is 1 MiB.
voidframework.web.server.fileSizeThreshold the maximum size allowed in memory before the uploaded file was stored on the disk rather than in memory. The default value is 256 KiB.
voidframework.web.server.tempFileLocation the location where temporary files will be stored. The default value is null (default Java temporary folder).
HTTP
voidframework.web.server.http.listenHost the interface on which the server will listen for non-secure HTTP requests. The default value is 127.0.0.1.
voidframework.web.server.http.listenPort the port on which the server will listen for non-secure HTTP requests. The default value is 9000.
HTTPS
voidframework.web.server.https.listenHost the interface on which the server will listen for HTTPS requests. The default value is 127.0.0.1.
voidframework.web.server.https.listenPort the port on which the server will listen for HTTPS requests. The default value is 9001.
voidframework.web.server.https.ssl.protocols the protocols to use. The default value is ["TLSv1.2", "TLSv1.3"].
voidframework.web.server.https.ssl.ciphers the allowed ciphers. If list is empty, all ciphers will be allowed. The default value is [].
voidframework.web.server.https.ssl.keyStorePath the path where is located the key store. Could be a “resources” path, a URL or a simple path. The default value is null.
voidframework.web.server.https.ssl.keyStoreType the type of the key store. The default value is JKS.
voidframework.web.server.https.ssl.keyStorePassword the password to use to open the key store. The default value is null.
voidframework.web.server.https.ssl.keyAlias the alias of the key to use. If “null” the key will be choosen automatically. The default value is null.
voidframework.web.server.https.ssl.keyPassword the key password. The default value is ${voidframework.web.server.https.ssl.keyStorePassword}.
Language
voidframework.web.language.availableLanguages the available languages. The default value is ["en", "fr"].
voidframework.web.language.cookieName the name of the cookie containing the current language. The default value is VOID_LANG.
voidframework.web.language.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.language.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Flash messages
voidframework.web.flashMessages.cookieName the name of the cookie containing the current flash messages. The default value is VOID_FLASH.
voidframework.web.flashMessages.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.flashMessages.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Session
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.
CSRF
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.
Security headers
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/index.xml b/index.xml
index 72f9d50..fd8ec16 100644
--- a/index.xml
+++ b/index.xml
@@ -1,13 +1,13 @@
 Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -34,16 +34,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -51,9 +51,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -64,22 +64,22 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
@@ -94,8 +94,8 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -107,19 +107,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index aa87447..359e315 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,7 +1,8 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.8.0

+Release notes
1.8.1

+2023-16-16
Improved Add exception AppLauncherException.ModuleConstructorNotFound

1.8.0

 2023-05-18
New Proxyable interface
New H2 web console
Improved Bind automatically interface with single implementation
Improved Updated version of all dependencies
Fixed Guice module implementing interface not recognized

1.7.0

 2023-04-12
Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492)
New Conditional feature RunInDevModeConditionalFeature
New Sendmail module
New Sendmail module implementation Apache Commons Email
New Add @CachePut annotation
Improved Javadoc
Improved HttpClient is now used instead of raw URL connection (Remote Configuration)
Improved Result: method badRequest(final String content, final String contentType)
Improved Updated version of all dependencies
Fixed Transactional annotation multiple calls

1.6.1

 2023-02-24
Fixed HTTP webserver graceful shutdown not honored

1.6.0


From 48c3dc6d327fa714a08853a5fdd5ee44e245ec9d Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Fri, 16 Jun 2023 17:58:23 +0000
Subject: [PATCH 51/75] Automated website build

---
 doc/core/class-scanning/index.html | 4 ++--
 doc/index.xml                      | 4 ++--
 index.xml                          | 4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index 99b3f65..739c34d 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -1,9 +1,9 @@
-Void Framework – Class scanning

 Void Framework
Documentation
    
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
-3 types of elements are recognised during the scan:
Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule
Classes annotated with Bindable familly annotation
Classes implementing defined interface
Interfaces annotated with Proxyable annotation

Guice module
Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.
 
+4 types of elements are recognised during the scan:
Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule
Classes annotated with Bindable familly annotation
Classes implementing defined interface
Interfaces annotated with Proxyable annotation

Guice module
Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.
 
 If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@Bindable 
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Defined interface
The configuration key voidframework.core.bindExtraInterfaces is used to define a set of interfaces for which to bind the found implementations. For example, converters are automatically detected in this way via the TypeConverter interface.

Proxyable interface
The @Proxyable annotation indicates that the implementation of the annotated interface is a proxy that will be configured by one of the modules that will be loaded when the application starts. The module can retrieve the interface(s) it is interested in via the ScannedClassesToLoad variable provided in the module constructor.

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
diff --git a/doc/index.xml b/doc/index.xml
index f24689a..341724e 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -8,8 +8,8 @@ Configuration The following configuration key can be used in the configuration f
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
-Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 4 types of elements are recognised during the scan:
+Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 4 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
 @ConditionalFeature The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
 The annotation accepts the following parameter:
diff --git a/index.xml b/index.xml
index fd8ec16..ced9d8f 100644
--- a/index.xml
+++ b/index.xml
@@ -8,8 +8,8 @@ Configuration The following configuration key can be used in the configuration f
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
-Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
-Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 3 types of elements are recognised during the scan:
+Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 4 types of elements are recognised during the scan:
+Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 4 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
 @ConditionalFeature The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
 The annotation accepts the following parameter:

From 713d2c6a8e28bd6c3d05b14a61b9e23fdebf0dac Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 13 Jul 2023 18:15:49 +0000
Subject: [PATCH 52/75] Automated website build

---
 doc/advanced/advanced/index.html              |  2 +-
 .../aspect-oriented-programming/index.html    | 44 +++++++++++++++++++
 doc/advanced/creating-module/index.html       |  9 +++-
 doc/advanced/index.html                       |  2 +-
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/index.html                          |  2 +-
 doc/cache/redis-cache/index.html              |  2 +-
 doc/cache/using-cache/index.html              |  2 +-
 doc/core/boot-sequence/index.html             |  2 +-
 doc/core/class-scanning/index.html            |  8 ++--
 doc/core/conditional-feature/index.html       |  2 +-
 doc/core/configuration/index.html             |  2 +-
 doc/core/index.html                           |  2 +-
 doc/core/lang/index.html                      |  2 +-
 doc/core/life-cycle/index.html                |  2 +-
 doc/core/type-conversion/index.html           |  2 +-
 doc/getting-started/index.html                |  2 +-
 .../new-application/index.html                |  2 +-
 doc/getting-started/requirements/index.html   |  2 +-
 .../upgrading-from-old-version/index.html     |  2 +-
 doc/i18n/index.html                           |  2 +-
 doc/index.html                                |  2 +-
 doc/index.xml                                 | 14 +++---
 .../using-i18n/index.html                     |  2 +-
 doc/nosql-databases/index.html                |  2 +-
 doc/nosql-databases/redis/index.html          |  2 +-
 .../datasource/index.html                     |  2 +-
 doc/relational-databases/h2/index.html        |  2 +-
 doc/relational-databases/index.html           |  2 +-
 .../persistence-hibernate/index.html          |  2 +-
 .../persistence-jooq/index.html               |  2 +-
 .../transactional/index.html                  |  2 +-
 doc/scheduler/index.html                      |  2 +-
 doc/scheduler/scheduling-job-cron/index.html  |  2 +-
 doc/sendmail/index.html                       |  2 +-
 .../mailer-apache-commons-email/index.html    |  2 +-
 doc/sendmail/mailer-dummy/index.html          |  2 +-
 doc/sendmail/sending-emails/index.html        |  2 +-
 doc/template/freemarker/index.html            |  2 +-
 doc/template/index.html                       |  2 +-
 doc/template/using-template/index.html        |  2 +-
 doc/testing/index.html                        |  2 +-
 doc/testing/junit-extension/index.html        |  2 +-
 doc/vfs/index.html                            |  2 +-
 doc/vfs/using-vfs/index.html                  |  2 +-
 doc/web/controller/index.html                 |  2 +-
 doc/web/filters/index.html                    |  2 +-
 doc/web/index.html                            |  2 +-
 doc/web/render-template/index.html            |  2 +-
 doc/web/security-csrf/index.html              |  2 +-
 doc/web/security-headers/index.html           |  2 +-
 doc/web/session/index.html                    |  2 +-
 doc/web/using-web/index.html                  |  2 +-
 index.xml                                     | 16 ++++---
 releasenotes/index.html                       |  7 +--
 sitemap.xml                                   |  2 +-
 56 files changed, 126 insertions(+), 72 deletions(-)
 create mode 100644 doc/advanced/aspect-oriented-programming/index.html

diff --git a/doc/advanced/advanced/index.html b/doc/advanced/advanced/index.html
index 31e4e64..50e71c4 100644
--- a/doc/advanced/advanced/index.html
+++ b/doc/advanced/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – reference.conf
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-sendmail reference.conf
voidframework-sendmail-commonsemail reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-sendmail reference.conf
voidframework-sendmail-commonsemail reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/advanced/aspect-oriented-programming/index.html b/doc/advanced/aspect-oriented-programming/index.html
new file mode 100644
index 0000000..3fd750e
--- /dev/null
+++ b/doc/advanced/aspect-oriented-programming/index.html
@@ -0,0 +1,44 @@
+Void Framework – Aspect Oriented Programming
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Aspect Oriented Programming
Aspect Oriented Programming (AOP) includes programming methods and tools that support the modularization of concerns at the level of the source code. Void Framework manages the AOP via the AspectJ and Guice libraries. The first library is more powerful but also more complicated to use, while the latter has fewer capabilities but is simple to use.

AspectJ
AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.
<plugin>
+    <!-- https://mvnrepository.com/artifact/org.codehaus.mojo/aspectj-maven-plugin -->
+    <groupId>org.codehaus.mojo</groupId>
+    <artifactId>aspectj-maven-plugin</artifactId>
+    <version>1.14.0</version>
+    <inherited>true</inherited>
+    
+    <dependencies>
+        <dependency>
+            <groupId>org.aspectj</groupId>
+            <artifactId>aspectjtools</artifactId>
+            <version>1.9.19</version> <!-- Min. version to handle Java 17 -->
+        </dependency>
+    </dependencies>
+    
+    <configuration>
+        <complianceLevel>${java.version}</complianceLevel>
+        <source>${maven.compiler.source}</source>
+        <target>${maven.compiler.target}</target>
+        <showWeaveInfo>true</showWeaveInfo>
+        <verbose>true</verbose>
+        <Xlint>ignore</Xlint>
+        <encoding>UTF-8</encoding>
+    </configuration>
+
+    <executions>
+        <execution>
+            <goals>
+                <goal>compile</goal>
+                <goal>test-compile</goal>
+            </goals>
+        </execution>
+    </executions>
+</plugin>
+
 
+If you are using an IDE, remember to configure it so that it executes the goal aspectj:compile before running your application. In IntelliJ, go to Maven tab, plugin, aspectj, left-click on aspectj:compile, choose "Execute before Run/Debug".
 
+Direct injection via constructor can't be used on classes annotated with @Aspect.
Read more about AspectJ at:
https://www.eclipse.org/aspectj/doc/released/progguide/index.html
https://www.baeldung.com/aspectj

Guice
Read more about Guice AOP at:
https://github.com/google/guice/wiki/AOP
https://www.baeldung.com/guice

© 2022-2023 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/advanced/creating-module/index.html b/doc/advanced/creating-module/index.html
index 202af3b..b4fd1b4 100644
--- a/doc/advanced/creating-module/index.html
+++ b/doc/advanced/creating-module/index.html
@@ -2,8 +2,7 @@
 To meet all needs, the Void Framework provid">Void Framework – Creating Module
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Creating Module
Do you want to create a Guice module that will be loaded when your application starts? Nothing could be simpler than creating an implementation of the abstract class AbstractModule or the interface Module.
To meet all needs, the Void Framework provides the ability to obtain additional information via the module’s constructor. As a constructor’s parameter, you could optionally use the following elements:
Config the current configuration of the application
ScannedClassesToLoad the classes that were scanned when the application started
In the event that one module needs to be loaded before another, you can use the OrderedModule annotation.

Example
@OrderedModule(priority = 50)
-public final class MyCustomModule extends AbstractModule {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Creating Module
Do you want to create a Guice module that will be loaded when your application starts? Nothing could be simpler than creating an implementation of the abstract class AbstractModule or the interface Module.
To meet all needs, the Void Framework provides the ability to obtain additional information via the module’s constructor. As a constructor’s parameter, you could optionally use the following elements:
Config the current configuration of the application
ScannedClassesToLoad the classes that were scanned when the application started
if a module needs to be loaded before another, you can use the OrderedModule interface.

Example
public final class MyCustomModule extends AbstractModule implements OrderedModule {
 
     private final Config configuration;
     private final ScannedClassesToLoad scannedClassesToLoad;
@@ -20,6 +19,12 @@
     
         // Place your module code here
     }
+
+    @Override
+    public int priority() {
+
+        return 50;
+    }
 }
 
 
 Remember that the module must be in a path that is scanned when the application starts. If this is not the case, you can add a new path via the configuration key voidframework.core.acceptedScanPaths.

© 2022-2023 Void Framework

diff --git a/doc/advanced/index.html b/doc/advanced/index.html
index b608455..aab2d64 100644
--- a/doc/advanced/index.html
+++ b/doc/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – Advanced
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Advanced

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Advanced

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index e51ea91..4e31ef6 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,7 +2,7 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
     <version>1.8.1</version>
diff --git a/doc/cache/index.html b/doc/cache/index.html
index bc2bdf9..f9093bf 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Cache

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index e31b4e7..c41db66 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
     <version>1.8.1</version>
diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index 1ec614c..67334c5 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,7 +2,7 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
 Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

@CachePut
Indicates that the result of the method will be cached regardless value already exists.
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index 183c0e9..ca8af48 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c . t o u e y a h d i r c l P . u c l r b">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index 739c34d..92bc7ab 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -1,11 +1,11 @@
-Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
-4 types of elements are recognised during the scan:
Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule
Classes annotated with Bindable familly annotation
Classes implementing defined interface
Interfaces annotated with Proxyable annotation

Guice module
Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+5 types of elements are recognised during the scan:
Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule
Classes annotated with Bindable familly annotation
Classes implementing defined interface
Classes annotated with Aspect annotation
Interfaces annotated with Proxyable annotation

Guice module
Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.
 
 If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
-Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@Bindable 
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Defined interface
The configuration key voidframework.core.bindExtraInterfaces is used to define a set of interfaces for which to bind the found implementations. For example, converters are automatically detected in this way via the TypeConverter interface.

Proxyable interface
The @Proxyable annotation indicates that the implementation of the annotated interface is a proxy that will be configured by one of the modules that will be loaded when the application starts. The module can retrieve the interface(s) it is interested in via the ScannedClassesToLoad variable provided in the module constructor.

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
+Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@Bindable 
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Defined interface
The configuration key voidframework.core.bindExtraInterfaces is used to define a set of interfaces for which to bind the found implementations. For example, converters are automatically detected in this way via the TypeConverter interface.

Aspect Oriented Programming
Aspect Oriented Programming (AOP) can be used with Void Framework, see chapter “Advanced / Aspect Oriented Programming” section for more information.

Proxyable interface
The @Proxyable annotation indicates that the implementation of the annotated interface is a proxy that will be configured by one of the modules that will be loaded when the application starts. The module can retrieve the interface(s) it is interested in via the ScannedClassesToLoad variable provided in the module constructor.

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
     <groupId>org.codehaus.mojo</groupId>
     <artifactId>exec-maven-plugin</artifactId>
     <version>3.0.0</version>
diff --git a/doc/core/conditional-feature/index.html b/doc/core/conditional-feature/index.html
index d16c92f..9778caf 100644
--- a/doc/core/conditional-feature/index.html
+++ b/doc/core/conditional-feature/index.html
@@ -2,7 +2,7 @@
 @ConditionalFeature The @ConditionalFeature annotation allows a feature to be enabled or">Void Framework – Conditional feature
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Conditional feature
Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.

@ConditionalFeature
The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
The annotation accepts the following parameter:
value is used to define the implementation of Condition interface to use.
Exemple
@WebController
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Conditional feature
Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.

@ConditionalFeature
The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
The annotation accepts the following parameter:
value is used to define the implementation of Condition interface to use.
Exemple
@WebController
 @ConditionalFeature(MyCustomCondition.class)
 public final class SampleController {
 }
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index c2d8824..ad1575b 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -1,7 +1,7 @@
 Void Framework – Configuration
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
 

Retrieve configuration value from Java
@Service
 public class MyService {
 
diff --git a/doc/core/index.html b/doc/core/index.html
index 9080906..70424c9 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Core

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Core

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/lang/index.html b/doc/core/lang/index.html
index fcd99e4..e114752 100644
--- a/doc/core/lang/index.html
+++ b/doc/core/lang/index.html
@@ -2,7 +2,7 @@
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get mor">Void Framework – Lang
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Lang
The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.

CUID
CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
// Random CUID
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Lang
The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.

CUID
CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.// Random CUID
 final CUID cuid = CUID.randomCUID();
 
 // CUID from String representating a CUID
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index 7b168cf..0767454 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time (duration or milliseconds) to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index cc54b39..8281243 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index 7aa4fee..47afb6e 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Getting Started

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Getting Started

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 7c942be..15cf5c9 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,7 +2,7 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
     <version>1.8.1</version>
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index 0901f12..2df3e14 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index 5e001d8..72e4c92 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.0.0 Initial relea">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.0.0
Initial release

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

1.6.0
Configuration keys voidframework.web.server.listenHost and voidframework.web.server.listenPort have been renamed to voidframework.web.server.http.listenHost and voidframework.web.server.http.listenPort

1.8.0
Guice 7.0 only supports the jakarta.inject, jakarta.servlet and jakarta.persistence namespaces. Read more at https://github.com/google/guice/wiki/Guice700

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.0.0
Initial release

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

1.6.0
Configuration keys voidframework.web.server.listenHost and voidframework.web.server.listenPort have been renamed to voidframework.web.server.http.listenHost and voidframework.web.server.http.listenPort

1.8.0
Guice 7.0 only supports the jakarta.inject, jakarta.servlet and jakarta.persistence namespaces. Read more at https://github.com/google/guice/wiki/Guice700

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index b095112..cf33b31 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Internationalization

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Internationalization

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index 9eb6537..e6f16df 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Documentation

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Documentation

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 341724e..f78845a 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,4 +1,6 @@
-Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Aspect Oriented Programminghttps://voidframework.dev/doc/advanced/aspect-oriented-programming/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/aspect-oriented-programming/Aspect Oriented Programming (AOP) includes programming methods and tools that support the modularization of concerns at the level of the source code. Void Framework manages the AOP via the AspectJ and Guice libraries. The first library is more powerful but also more complicated to use, while the latter has fewer capabilities but is simple to use.
+AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Aspect Oriented Programminghttps://voidframework.dev/doc/advanced/aspect-oriented-programming/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/aspect-oriented-programming/Aspect Oriented Programming (AOP) includes programming methods and tools that support the modularization of concerns at the level of the source code. Void Framework manages the AOP via the AspectJ and Guice libraries. The first library is more powerful but also more complicated to use, while the latter has fewer capabilities but is simple to use.
+AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
@@ -8,9 +10,9 @@ Configuration The following configuration key can be used in the configuration f
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
-Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 4 types of elements are recognised during the scan:
-Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 4 types of elements are recognised during the scan:
-Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
+Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
+Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
+Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
 @ConditionalFeature The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
 The annotation accepts the following parameter:
 value is used to define the implementation of Condition interface to use.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -24,9 +26,9 @@ Example
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Creating Modulehttps://voidframework.dev/doc/advanced/creating-module/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/creating-module/Do you want to create a Guice module that will be loaded when your application starts? Nothing could be simpler than creating an implementation of the abstract class AbstractModule or the interface Module.
 To meet all needs, the Void Framework provides the ability to obtain additional information via the module&rsquo;s constructor. As a constructor&rsquo;s parameter, you could optionally use the following elements:
-Config the current configuration of the application ScannedClassesToLoad the classes that were scanned when the application started In the event that one module needs to be loaded before another, you can use the OrderedModule annotation.Creating Modulehttps://voidframework.dev/doc/advanced/creating-module/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/creating-module/Do you want to create a Guice module that will be loaded when your application starts? Nothing could be simpler than creating an implementation of the abstract class AbstractModule or the interface Module.
+Config the current configuration of the application ScannedClassesToLoad the classes that were scanned when the application started if a module needs to be loaded before another, you can use the OrderedModule interface.Creating Modulehttps://voidframework.dev/doc/advanced/creating-module/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/creating-module/Do you want to create a Guice module that will be loaded when your application starts? Nothing could be simpler than creating an implementation of the abstract class AbstractModule or the interface Module.
 To meet all needs, the Void Framework provides the ability to obtain additional information via the module&rsquo;s constructor. As a constructor&rsquo;s parameter, you could optionally use the following elements:
-Config the current configuration of the application ScannedClassesToLoad the classes that were scanned when the application started In the event that one module needs to be loaded before another, you can use the OrderedModule annotation.CSRFhttps://voidframework.dev/doc/web/security-csrf/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-csrf/Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
+Config the current configuration of the application ScannedClassesToLoad the classes that were scanned when the application started if a module needs to be loaded before another, you can use the OrderedModule interface.CSRFhttps://voidframework.dev/doc/web/security-csrf/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-csrf/Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 &nbsp; It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP. Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.Data sourcehttps://voidframework.dev/doc/relational-databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Installation Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Data sourcehttps://voidframework.dev/doc/relational-databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Installation Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index f352240..314814d 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
     <version>1.8.1</version>
diff --git a/doc/nosql-databases/index.html b/doc/nosql-databases/index.html
index a79cee9..8a08d19 100644
--- a/doc/nosql-databases/index.html
+++ b/doc/nosql-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – NoSQL Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

NoSQL Databases

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

NoSQL Databases

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index 54afcee..70bf078 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -2,7 +2,7 @@
 Installation To enable this module, just add following lines to ">Void Framework – Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notesGetting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
     <version>1.8.1</version>
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index 5c0f43b..f2d3290 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -1,7 +1,7 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
diff --git a/doc/relational-databases/h2/index.html b/doc/relational-databases/h2/index.html
index 98eb06f..7d5063a 100644
--- a/doc/relational-databases/h2/index.html
+++ b/doc/relational-databases/h2/index.html
@@ -1,7 +1,7 @@
 Void Framework – H2
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

H2
H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

H2
H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-h2</artifactId>
     <version>1.8.1</version>
diff --git a/doc/relational-databases/index.html b/doc/relational-databases/index.html
index f140a7e..08a7812 100644
--- a/doc/relational-databases/index.html
+++ b/doc/relational-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Relational Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Relational Databases

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Relational Databases

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index 6b43b79..1a91c8c 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -2,7 +2,7 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index ec5c83d..e3190c5 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -2,7 +2,7 @@
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provid">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-jooq</artifactId>
     <version>1.8.1</version>
diff --git a/doc/relational-databases/transactional/index.html b/doc/relational-databases/transactional/index.html
index dac609b..076e95d 100644
--- a/doc/relational-databases/transactional/index.html
+++ b/doc/relational-databases/transactional/index.html
@@ -1,7 +1,7 @@
 Void Framework – Transactional
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Transactional
It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional (Jakarta) annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Transactional
It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional (Jakarta) annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
 Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
diff --git a/doc/scheduler/index.html b/doc/scheduler/index.html
index 8d32ecc..6a758be 100644
--- a/doc/scheduler/index.html
+++ b/doc/scheduler/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduler
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Scheduler

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Scheduler

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index 7817fc7..8d9ac15 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduling a local job
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-scheduler</artifactId>
     <version>1.8.1</version>
diff --git a/doc/sendmail/index.html b/doc/sendmail/index.html
index 53eb75c..823bf0f 100644
--- a/doc/sendmail/index.html
+++ b/doc/sendmail/index.html
@@ -1,7 +1,7 @@
 Void Framework – Sendmail
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Sendmail

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Sendmail

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/sendmail/mailer-apache-commons-email/index.html b/doc/sendmail/mailer-apache-commons-email/index.html
index 1ec8148..5362d7b 100644
--- a/doc/sendmail/mailer-apache-commons-email/index.html
+++ b/doc/sendmail/mailer-apache-commons-email/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsema">Void Framework – Mailer : Apache Commons Email
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Mailer : Apache Commons Email
This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Mailer : Apache Commons Email
This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail-commonsemail</artifactId>
     <version>1.8.1</version>
diff --git a/doc/sendmail/mailer-dummy/index.html b/doc/sendmail/mailer-dummy/index.html
index 3e5ba7e..53ea122 100644
--- a/doc/sendmail/mailer-dummy/index.html
+++ b/doc/sendmail/mailer-dummy/index.html
@@ -2,7 +2,7 @@
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframewor">Void Framework – Mailer : Dummy
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Mailer : Dummy
This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.

Installation
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Mailer : Dummy
This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.

Installation
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/sendmail/sending-emails/index.html b/doc/sendmail/sending-emails/index.html
index 0ca9756..77d1dbb 100644
--- a/doc/sendmail/sending-emails/index.html
+++ b/doc/sendmail/sending-emails/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&">Void Framework – Sending emails
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Sending emails
If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Sending emails
If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail</artifactId>
     <version>1.8.1</version>
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index 0b53141..e930e33 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -2,7 +2,7 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifact">Void Framework – FreeMarker
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
     <version>1.8.1</version>
diff --git a/doc/template/index.html b/doc/template/index.html
index 83ff9e2..0e43fc3 100644
--- a/doc/template/index.html
+++ b/doc/template/index.html
@@ -1,7 +1,7 @@
 Void Framework – Template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Template

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Template

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/template/using-template/index.html b/doc/template/using-template/index.html
index 4cf1a67..0420696 100644
--- a/doc/template/using-template/index.html
+++ b/doc/template/using-template/index.html
@@ -2,7 +2,7 @@
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final Temp">Void Framework – Using template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using template
Sooner or later you will need to generate documents (HTML, PDF…). Void Framework provides all the tools you need!

Example
public class TemplateExample {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using template
Sooner or later you will need to generate documents (HTML, PDF…). Void Framework provides all the tools you need!

Example
public class TemplateExample {
 
     private final TemplateRenderer templateRenderer;
 
diff --git a/doc/testing/index.html b/doc/testing/index.html
index 1a71538..fec63a4 100644
--- a/doc/testing/index.html
+++ b/doc/testing/index.html
@@ -1,7 +1,7 @@
 Void Framework – Testing
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Testing

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Testing

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index 4f9a14d..1b3edbd 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -2,7 +2,7 @@
 To enable this module, just add following lines to th">Void Framework – JUnit's extension
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
     <version>1.8.1</version>
diff --git a/doc/vfs/index.html b/doc/vfs/index.html
index 083fc7e..c48b8d5 100644
--- a/doc/vfs/index.html
+++ b/doc/vfs/index.html
@@ -1,7 +1,7 @@
 Void Framework – Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Virtual File Storage

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Virtual File Storage

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/vfs/using-vfs/index.html b/doc/vfs/using-vfs/index.html
index 14d15d8..5b4a9f8 100644
--- a/doc/vfs/using-vfs/index.html
+++ b/doc/vfs/using-vfs/index.html
@@ -1,7 +1,7 @@
 Void Framework – Using Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
     <version>1.8.1</version>
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index 1f72ea7..a2eb541 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index e5a92ff..f24bf5a 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the">Void Framework – Filters
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
 Note that the use of dependencies direct injection is possible in filters.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
 @Singleton
 @WebController
diff --git a/doc/web/index.html b/doc/web/index.html
index 9ab5a8a..9589c7c 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Web

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Web

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/render-template/index.html b/doc/web/render-template/index.html
index 81fcec6..51c8363 100644
--- a/doc/web/render-template/index.html
+++ b/doc/web/render-template/index.html
@@ -2,7 +2,7 @@
 Although you can manually use the template engine, in most cases this would not be handy. Howev">Void Framework – Render template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Static files
If you need to include static files in your HTML page (e.g. css, javascript, image, …), you can use the urlfor method with the first parameter static_file or static_webjar and the second parameter the path to the file.

Example
controller/HomeController.java
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Static files
If you need to include static files in your HTML page (e.g. css, javascript, image, …), you can use the urlfor method with the first parameter static_file or static_webjar and the second parameter the path to the file.

Example
controller/HomeController.java
@Singleton
 @WebController
 public class HomeController {
 
diff --git a/doc/web/security-csrf/index.html b/doc/web/security-csrf/index.html
index 9710af1..01fdf06 100644
--- a/doc/web/security-csrf/index.html
+++ b/doc/web/security-csrf/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is recommended tha">Void Framework – CSRF
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
 It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP.
Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/security-headers/index.html b/doc/web/security-headers/index.html
index 53c9857..943ab89 100644
--- a/doc/web/security-headers/index.html
+++ b/doc/web/security-headers/index.html
@@ -2,7 +2,7 @@
 Configuration The following configuration keys can be used in the configuration">Void Framework – Security headers
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
 You can disable one of the headers by assigning the value null. The header will then not be sent.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/session/index.html b/doc/web/session/index.html
index 271e561..a5943a1 100644
--- a/doc/web/session/index.html
+++ b/doc/web/session/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the session is not stored on the server side, but on the client side v">Void Framework – Session
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
 Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie.

Because session is implemented using cookies, there are some implications.The data size is limited to 4 KiB
Only string can be stored

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.

Read value
You can access the session data via the Context. Methods get or getOrDefault can be used.
@Singleton
 @WebController
 public class Controller {
diff --git a/doc/web/using-web/index.html b/doc/web/using-web/index.html
index edabb1c..58b5d39 100644
--- a/doc/web/using-web/index.html
+++ b/doc/web/using-web/index.html
@@ -2,7 +2,7 @@
 Installation To enable this module, just add following lines to the pom.xml ">Void Framework – Using Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
     <version>1.8.1</version>
diff --git a/index.xml b/index.xml
index ced9d8f..bf79f27 100644
--- a/index.xml
+++ b/index.xml
@@ -1,4 +1,6 @@
-Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
+Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Aspect Oriented Programminghttps://voidframework.dev/doc/advanced/aspect-oriented-programming/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/aspect-oriented-programming/Aspect Oriented Programming (AOP) includes programming methods and tools that support the modularization of concerns at the level of the source code. Void Framework manages the AOP via the AspectJ and Guice libraries. The first library is more powerful but also more complicated to use, while the latter has fewer capabilities but is simple to use.
+AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Aspect Oriented Programminghttps://voidframework.dev/doc/advanced/aspect-oriented-programming/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/aspect-oriented-programming/Aspect Oriented Programming (AOP) includes programming methods and tools that support the modularization of concerns at the level of the source code. Void Framework manages the AOP via the AspectJ and Guice libraries. The first library is more powerful but also more complicated to use, while the latter has fewer capabilities but is simple to use.
+AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
@@ -8,9 +10,9 @@ Configuration The following configuration key can be used in the configuration f
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
-Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 4 types of elements are recognised during the scan:
-Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 4 types of elements are recognised during the scan:
-Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
+Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
+Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
+Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
 @ConditionalFeature The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
 The annotation accepts the following parameter:
 value is used to define the implementation of Condition interface to use.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -24,9 +26,9 @@ Example
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Creating a new applicationhttps://voidframework.dev/doc/getting-started/new-application/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/new-application/To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.Creating Modulehttps://voidframework.dev/doc/advanced/creating-module/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/creating-module/Do you want to create a Guice module that will be loaded when your application starts? Nothing could be simpler than creating an implementation of the abstract class AbstractModule or the interface Module.
 To meet all needs, the Void Framework provides the ability to obtain additional information via the module&rsquo;s constructor. As a constructor&rsquo;s parameter, you could optionally use the following elements:
-Config the current configuration of the application ScannedClassesToLoad the classes that were scanned when the application started In the event that one module needs to be loaded before another, you can use the OrderedModule annotation.Creating Modulehttps://voidframework.dev/doc/advanced/creating-module/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/creating-module/Do you want to create a Guice module that will be loaded when your application starts? Nothing could be simpler than creating an implementation of the abstract class AbstractModule or the interface Module.
+Config the current configuration of the application ScannedClassesToLoad the classes that were scanned when the application started if a module needs to be loaded before another, you can use the OrderedModule interface.Creating Modulehttps://voidframework.dev/doc/advanced/creating-module/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/creating-module/Do you want to create a Guice module that will be loaded when your application starts? Nothing could be simpler than creating an implementation of the abstract class AbstractModule or the interface Module.
 To meet all needs, the Void Framework provides the ability to obtain additional information via the module&rsquo;s constructor. As a constructor&rsquo;s parameter, you could optionally use the following elements:
-Config the current configuration of the application ScannedClassesToLoad the classes that were scanned when the application started In the event that one module needs to be loaded before another, you can use the OrderedModule annotation.CSRFhttps://voidframework.dev/doc/web/security-csrf/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-csrf/Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
+Config the current configuration of the application ScannedClassesToLoad the classes that were scanned when the application started if a module needs to be loaded before another, you can use the OrderedModule interface.CSRFhttps://voidframework.dev/doc/web/security-csrf/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-csrf/Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 &nbsp; It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP. Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.Data sourcehttps://voidframework.dev/doc/relational-databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Installation Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Data sourcehttps://voidframework.dev/doc/relational-databases/datasource/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/datasource/Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.
 Installation Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change.Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Documentationhttps://voidframework.dev/doc/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
@@ -79,7 +81,7 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.9.0 2023-XX-XX New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.9.0 2023-XX-XX New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 359e315..8aff02a 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,8 +1,9 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.8.1

-2023-16-16
Improved Add exception AppLauncherException.ModuleConstructorNotFound

1.8.0

+Release notes
1.9.0

+2023-XX-XX
New AspectJ
New REST client
New Bucket4J (rate-limiting)
New Add ConfigurationUtils class
Improved Upgrade dependencies
Improved New constant value: CharConstants.TAB and StringConstants.TAB

1.8.1

+2023-16-16
Improved Add exception AppLauncherException.ModuleConstructorNotFound

1.8.0

 2023-05-18
New Proxyable interface
New H2 web console
Improved Bind automatically interface with single implementation
Improved Updated version of all dependencies
Fixed Guice module implementing interface not recognized

1.7.0

 2023-04-12
Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492)
New Conditional feature RunInDevModeConditionalFeature
New Sendmail module
New Sendmail module implementation Apache Commons Email
New Add @CachePut annotation
Improved Javadoc
Improved HttpClient is now used instead of raw URL connection (Remote Configuration)
Improved Result: method badRequest(final String content, final String contentType)
Improved Updated version of all dependencies
Fixed Transactional annotation multiple calls

1.6.1

 2023-02-24
Fixed HTTP webserver graceful shutdown not honored

1.6.0

diff --git a/sitemap.xml b/sitemap.xml
index 8947309..557faa9 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/sendmail/https://voidframework.dev/doc/sendmail/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/advanced/creating-module/https://voidframework.dev/doc/advanced/creating-module/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/h2/https://voidframework.dev/doc/relational-databases/h2/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/https://voidframework.dev/doc/sendmail/mailer-dummy/https://voidframework.dev/doc/sendmail/mailer-dummy/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/sendmail/sending-emails/https://voidframework.dev/doc/sendmail/sending-emails/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/template/using-template/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/sendmail/https://voidframework.dev/doc/sendmail/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/aspect-oriented-programming/https://voidframework.dev/doc/advanced/aspect-oriented-programming/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/advanced/creating-module/https://voidframework.dev/doc/advanced/creating-module/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/h2/https://voidframework.dev/doc/relational-databases/h2/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/https://voidframework.dev/doc/sendmail/mailer-dummy/https://voidframework.dev/doc/sendmail/mailer-dummy/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/sendmail/sending-emails/https://voidframework.dev/doc/sendmail/sending-emails/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/template/using-template/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/
\ No newline at end of file

From 4e308722ccdd217ad000093ad93f7a7d8b1b9e13 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 13 Jul 2023 18:17:58 +0000
Subject: [PATCH 53/75] Automated website build

---
 index.xml               | 2 +-
 releasenotes/index.html | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.xml b/index.xml
index bf79f27..ed004d2 100644
--- a/index.xml
+++ b/index.xml
@@ -81,7 +81,7 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.9.0 2023-XX-XX New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.9.0 2023-XX-XX New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 8aff02a..54b736f 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,8 +1,8 @@
-Void Framework – Release notes

+Void Framework – Release notes
 Void Framework
Documentation
    
 Release notes
1.9.0

-2023-XX-XX
New AspectJ
New REST client
New Bucket4J (rate-limiting)
New Add ConfigurationUtils class
Improved Upgrade dependencies
Improved New constant value: CharConstants.TAB and StringConstants.TAB

1.8.1

+2023-07-13
New AspectJ
New REST client
New Bucket4J (rate-limiting)
New Add ConfigurationUtils class
Improved Upgrade dependencies
Improved New constant value: CharConstants.TAB and StringConstants.TAB

1.8.1

 2023-16-16
Improved Add exception AppLauncherException.ModuleConstructorNotFound

1.8.0

 2023-05-18
New Proxyable interface
New H2 web console
Improved Bind automatically interface with single implementation
Improved Updated version of all dependencies
Fixed Guice module implementing interface not recognized

1.7.0

 2023-04-12
Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492)
New Conditional feature RunInDevModeConditionalFeature
New Sendmail module
New Sendmail module implementation Apache Commons Email
New Add @CachePut annotation
Improved Javadoc
Improved HttpClient is now used instead of raw URL connection (Remote Configuration)
Improved Result: method badRequest(final String content, final String contentType)
Improved Updated version of all dependencies
Fixed Transactional annotation multiple calls

1.6.1


From 485b161a36698121d8b62fce67e559fbdeab2e02 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 13 Jul 2023 18:20:20 +0000
Subject: [PATCH 54/75] Automated website build

---
 doc/advanced/advanced/index.html | 2 +-
 doc/index.xml                    | 4 ++--
 index.xml                        | 4 ++--
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/advanced/advanced/index.html b/doc/advanced/advanced/index.html
index 50e71c4..f75dc84 100644
--- a/doc/advanced/advanced/index.html
+++ b/doc/advanced/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – reference.conf

 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-scheduler reference.conf
voidframework-sendmail reference.conf
voidframework-sendmail-commonsemail reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-bucket4j reference.conf
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-restclient reference.conf
voidframework-scheduler reference.conf
voidframework-sendmail reference.conf
voidframework-sendmail-commonsemail reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index f78845a..1d9f583 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -80,8 +80,8 @@ voidframework.redis.host the Redis server host.</item><item><title>reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
+voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
diff --git a/index.xml b/index.xml
index ed004d2..a57609a 100644
--- a/index.xml
+++ b/index.xml
@@ -80,8 +80,8 @@ voidframework.redis.host the Redis server host.</item><item><title>reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.conf voidframework-sendmail-commonsemail reference.conf voidframework-template-freemarker reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
+voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:

From 900a56139db55a62271d59766f45a5753931403c Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 13 Jul 2023 19:23:51 +0000
Subject: [PATCH 55/75] Automated website build

---
 doc/advanced/advanced/index.html              |  2 +-
 .../aspect-oriented-programming/index.html    |  2 +-
 doc/advanced/creating-module/index.html       |  2 +-
 doc/advanced/index.html                       |  2 +-
 doc/cache/in-memory-cache/index.html          |  4 +-
 doc/cache/index.html                          |  2 +-
 doc/cache/redis-cache/index.html              |  6 +-
 doc/cache/using-cache/index.html              |  2 +-
 doc/core/boot-sequence/index.html             |  2 +-
 doc/core/class-scanning/index.html            |  2 +-
 doc/core/conditional-feature/index.html       |  2 +-
 doc/core/configuration/index.html             |  6 +-
 doc/core/index.html                           |  2 +-
 doc/core/lang/index.html                      |  2 +-
 doc/core/life-cycle/index.html                |  2 +-
 doc/core/type-conversion/index.html           |  2 +-
 doc/getting-started/index.html                |  2 +-
 .../new-application/index.html                |  6 +-
 doc/getting-started/requirements/index.html   |  2 +-
 .../upgrading-from-old-version/index.html     |  2 +-
 doc/i18n/index.html                           |  2 +-
 doc/index.html                                |  2 +-
 doc/index.xml                                 | 56 +++++++++++--------
 .../using-i18n/index.html                     |  4 +-
 doc/nosql-databases/index.html                |  2 +-
 doc/nosql-databases/redis/index.html          |  6 +-
 .../datasource/index.html                     |  6 +-
 doc/relational-databases/h2/index.html        |  4 +-
 doc/relational-databases/index.html           |  2 +-
 .../persistence-hibernate/index.html          |  4 +-
 .../persistence-jooq/index.html               |  4 +-
 .../transactional/index.html                  |  2 +-
 doc/rest-client/index.html                    |  8 +++
 doc/rest-client/retrofit2/index.html          | 54 ++++++++++++++++++
 doc/scheduler/index.html                      |  2 +-
 doc/scheduler/scheduling-job-cron/index.html  |  4 +-
 doc/sendmail/index.html                       |  2 +-
 .../mailer-apache-commons-email/index.html    |  4 +-
 doc/sendmail/mailer-dummy/index.html          |  2 +-
 doc/sendmail/sending-emails/index.html        |  4 +-
 doc/template/freemarker/index.html            |  4 +-
 doc/template/index.html                       |  2 +-
 doc/template/using-template/index.html        |  2 +-
 doc/testing/index.html                        |  2 +-
 doc/testing/junit-extension/index.html        |  4 +-
 doc/vfs/index.html                            |  2 +-
 doc/vfs/using-vfs/index.html                  |  4 +-
 doc/web/controller/index.html                 |  2 +-
 doc/web/filters/index.html                    |  2 +-
 doc/web/index.html                            |  2 +-
 doc/web/render-template/index.html            |  2 +-
 doc/web/security-csrf/index.html              |  2 +-
 doc/web/security-headers/index.html           |  2 +-
 doc/web/session/index.html                    |  2 +-
 doc/web/using-web/index.html                  |  4 +-
 index.xml                                     | 56 +++++++++++--------
 sitemap.xml                                   |  2 +-
 57 files changed, 201 insertions(+), 123 deletions(-)
 create mode 100644 doc/rest-client/index.html
 create mode 100644 doc/rest-client/retrofit2/index.html

diff --git a/doc/advanced/advanced/index.html b/doc/advanced/advanced/index.html
index f75dc84..931f8a6 100644
--- a/doc/advanced/advanced/index.html
+++ b/doc/advanced/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – reference.conf
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-bucket4j reference.conf
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-restclient reference.conf
voidframework-scheduler reference.conf
voidframework-sendmail reference.conf
voidframework-sendmail-commonsemail reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-bucket4j reference.conf
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-restclient reference.conf
voidframework-scheduler reference.conf
voidframework-sendmail reference.conf
voidframework-sendmail-commonsemail reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/advanced/aspect-oriented-programming/index.html b/doc/advanced/aspect-oriented-programming/index.html
index 3fd750e..b50499e 100644
--- a/doc/advanced/aspect-oriented-programming/index.html
+++ b/doc/advanced/aspect-oriented-programming/index.html
@@ -1,7 +1,7 @@
 Void Framework – Aspect Oriented Programming
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Aspect Oriented Programming
Aspect Oriented Programming (AOP) includes programming methods and tools that support the modularization of concerns at the level of the source code. Void Framework manages the AOP via the AspectJ and Guice libraries. The first library is more powerful but also more complicated to use, while the latter has fewer capabilities but is simple to use.

AspectJ
AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.
<plugin>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Aspect Oriented Programming
Aspect Oriented Programming (AOP) includes programming methods and tools that support the modularization of concerns at the level of the source code. Void Framework manages the AOP via the AspectJ and Guice libraries. The first library is more powerful but also more complicated to use, while the latter has fewer capabilities but is simple to use.

AspectJ
AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.
<plugin>
     <!-- https://mvnrepository.com/artifact/org.codehaus.mojo/aspectj-maven-plugin -->
     <groupId>org.codehaus.mojo</groupId>
     <artifactId>aspectj-maven-plugin</artifactId>
diff --git a/doc/advanced/creating-module/index.html b/doc/advanced/creating-module/index.html
index b4fd1b4..6913bcd 100644
--- a/doc/advanced/creating-module/index.html
+++ b/doc/advanced/creating-module/index.html
@@ -2,7 +2,7 @@
 To meet all needs, the Void Framework provid">Void Framework – Creating Module
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Creating Module
Do you want to create a Guice module that will be loaded when your application starts? Nothing could be simpler than creating an implementation of the abstract class AbstractModule or the interface Module.
To meet all needs, the Void Framework provides the ability to obtain additional information via the module’s constructor. As a constructor’s parameter, you could optionally use the following elements:
Config the current configuration of the application
ScannedClassesToLoad the classes that were scanned when the application started
if a module needs to be loaded before another, you can use the OrderedModule interface.

Example
public final class MyCustomModule extends AbstractModule implements OrderedModule {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Creating Module
Do you want to create a Guice module that will be loaded when your application starts? Nothing could be simpler than creating an implementation of the abstract class AbstractModule or the interface Module.
To meet all needs, the Void Framework provides the ability to obtain additional information via the module’s constructor. As a constructor’s parameter, you could optionally use the following elements:
Config the current configuration of the application
ScannedClassesToLoad the classes that were scanned when the application started
if a module needs to be loaded before another, you can use the OrderedModule interface.

Example
public final class MyCustomModule extends AbstractModule implements OrderedModule {
 
     private final Config configuration;
     private final ScannedClassesToLoad scannedClassesToLoad;
diff --git a/doc/advanced/index.html b/doc/advanced/index.html
index aab2d64..28af2b0 100644
--- a/doc/advanced/index.html
+++ b/doc/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – Advanced
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Advanced

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Advanced

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 4e31ef6..b034f25 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -2,10 +2,10 @@
 Insta">Void Framework – Cache engine : In-memory
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/index.html b/doc/cache/index.html
index f9093bf..000d106 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index c41db66..ed97892 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -1,11 +1,11 @@
 Void Framework – Cache engine : Redis
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.9.">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index 67334c5..eff6f9e 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -2,7 +2,7 @@
 &nbsp; If no CacheEngine implementation was specified, the cache will n">Void Framework – Using cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
 Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

@CachePut
Indicates that the result of the method will be cached regardless value already exists.
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
 public class CacheExample {
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index ca8af48..25a016d 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c . t o u e y a h d i r c l P . u c l r b">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index 92bc7ab..797eb50 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -2,7 +2,7 @@
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule C">Void Framework – Class scanning
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Class scanning
The core of the Void Framework is based on the scanning of different paths to discover elements to load.
 5 types of elements are recognised during the scan:
Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule
Classes annotated with Bindable familly annotation
Classes implementing defined interface
Classes annotated with Aspect annotation
Interfaces annotated with Proxyable annotation

Guice module
Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts. Unless the module is explicitly disabled by the voidframework.core.disabledModules configuration.
 
 If you want to manage a priority on Guices modules, you can implement the OrderedModule interface.

Bindable
@Bindable is a specific annotation that allows annotated classes to be considered as candidates for auto-detection during classpath scan.
 Other class-level specialized annotations can also be considered as identifying a bindable and provide a clearer identification of the purpose of the class.
Annotation Description
@Bindable 
@Controller Indicates that an annotated class is a “Controller”
@Repository Indicates that an annotated class is a “Repository”
@Service Indicates that an annotated class is a “Service”

Defined interface
The configuration key voidframework.core.bindExtraInterfaces is used to define a set of interfaces for which to bind the found implementations. For example, converters are automatically detected in this way via the TypeConverter interface.

Aspect Oriented Programming
Aspect Oriented Programming (AOP) can be used with Void Framework, see chapter “Advanced / Aspect Oriented Programming” section for more information.

Proxyable interface
The @Proxyable annotation indicates that the implementation of the annotated interface is a proxy that will be configured by one of the modules that will be loaded when the application starts. The module can retrieve the interface(s) it is interested in via the ScannedClassesToLoad variable provided in the module constructor.

Bootstrap file generator
Scanning classes can, for several reasons, drastically increase the start-up time of the application. To mitigate this phenomenon, it is possible to use a bootstrap file, generated in advance, containing the useful classes detected during the scan. At compile time, the file resources/classpath.bootstrap will be created.
To activate the generator, simply add the following lines to the pom.xml file.
<plugin>
diff --git a/doc/core/conditional-feature/index.html b/doc/core/conditional-feature/index.html
index 9778caf..5fbdee0 100644
--- a/doc/core/conditional-feature/index.html
+++ b/doc/core/conditional-feature/index.html
@@ -2,7 +2,7 @@
 @ConditionalFeature The @ConditionalFeature annotation allows a feature to be enabled or">Void Framework – Conditional feature
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Conditional feature
Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.

@ConditionalFeature
The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
The annotation accepts the following parameter:
value is used to define the implementation of Condition interface to use.
Exemple
@WebController
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Conditional feature
Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.

@ConditionalFeature
The @ConditionalFeature annotation allows a feature to be enabled or disabled depending on the processing performed by the class supplied as a parameter. This class must implement the Condition interface.
The annotation accepts the following parameter:
value is used to define the implementation of Condition interface to use.
Exemple
@WebController
 @ConditionalFeature(MyCustomCondition.class)
 public final class SampleController {
 }
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index ad1575b..e342e99 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -1,7 +1,7 @@
 Void Framework – Configuration
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
These are the default filenames that the Config library looks for on the classpath:
application.conf
application.json
application.properties
reference.conf

JVM properties
It is sometimes useful to be able to override or simply set specific configuration values from the parameters provided at JVM startup. To do this, all properties defined via -D flag are accessible from the Configuration object.

Use another configuration file
If you need to use a custom/external configuration file, especially when your application is deployed on a server. You can use the flag -Dconfig.file to specify location of the configuration file to use.
-Dconfig.file=/path/to/your/application.conf
 

Retrieve configuration value from Java
@Service
 public class MyService {
 
@@ -25,7 +25,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.8.1</version>
+  <version>1.9.0</version>
 </dependency>
 
voidframework {
     code {
@@ -60,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.8.1</version>
+  <version>1.9.0</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/core/index.html b/doc/core/index.html
index 70424c9..7806f8c 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Core

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Core

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/lang/index.html b/doc/core/lang/index.html
index e114752..202dd2a 100644
--- a/doc/core/lang/index.html
+++ b/doc/core/lang/index.html
@@ -2,7 +2,7 @@
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get mor">Void Framework – Lang
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Lang
The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.

CUID
CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
// Random CUID
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Lang
The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.

CUID
CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
// Random CUID
 final CUID cuid = CUID.randomCUID();
 
 // CUID from String representating a CUID
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index 0767454..0916a28 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is possible to have ">Void Framework – Life cycle
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Life cycle
Void Framework provides a way to manage the life of a component. The @LifeCycleStart and @LifeCycleStop annotations allow you to define the methods to be called automatically when the application is started and stopped.
 
 It is possible to have several methods of a class annotated with the same annotation.

@LifeCycleStart
Indicates that this method should be called when the application starts.
The annotation accepts the following parameter:
priority is used to define when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.

@LifeCycleStop
Indicates that this method should be called when the application is stopped.
The annotation accepts the following parameters:
priority defines when the method will be called in relation to the others. The lower the priority, the higher the priority of the method. The default value is 1000.
gracefulStopTimeoutConfigKey allows you to provide a configuration key to retrieve the maximum time (duration or milliseconds) to wait before giving up and continuing to stop the application. If no key is specified, the default value 0 will be used.

Example
@BindClass
 @Singleton
 public final class ExampleLifeCycle {
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index 8281243..7f36a23 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -1,7 +1,7 @@
 Void Framework – Type conversion
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Type conversion
Type conversion is a mechanism for converting data from one type to another. For example, convert the string “1234” to an integer. The conversion is very useful when moving from one layer to another in DDD-based architectures. It is also used in the web feature to convert path param to typed values in the controller.

Using conversion
The conversion is used via the Conversion service which is accessible via direct injection.
public final class ExampleConversionService {
 
     private final Conversion conversion;
 
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index 47afb6e..89ebcd9 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Getting Started

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Getting Started

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 15cf5c9..88dd2e0 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -2,15 +2,15 @@
 Maven The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the">Void Framework – Creating a new application
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index 2df3e14..15499ac 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -2,7 +2,7 @@
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter th">Void Framework – Requirements
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Requirements
To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.

Verifying and installing Java
To check that you have Java JDK 17 or higher, enter the following in a shell:
#> java -version
 
You should see something like:
openjdk version "17.0.2" 2022-01-18
 OpenJDK Runtime Environment (build 17.0.2+8-86)
 OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index 72e4c92..983fe3e 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.0.0 Initial relea">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.0.0
Initial release

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

1.6.0
Configuration keys voidframework.web.server.listenHost and voidframework.web.server.listenPort have been renamed to voidframework.web.server.http.listenHost and voidframework.web.server.http.listenPort

1.8.0
Guice 7.0 only supports the jakarta.inject, jakarta.servlet and jakarta.persistence namespaces. Read more at https://github.com/google/guice/wiki/Guice700

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.0.0
Initial release

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

1.6.0
Configuration keys voidframework.web.server.listenHost and voidframework.web.server.listenPort have been renamed to voidframework.web.server.http.listenHost and voidframework.web.server.http.listenPort

1.8.0
Guice 7.0 only supports the jakarta.inject, jakarta.servlet and jakarta.persistence namespaces. Read more at https://github.com/google/guice/wiki/Guice700

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index cf33b31..9ed3d4a 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Internationalization

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Internationalization

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index e6f16df..729d186 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Documentation

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Documentation

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 1d9f583..3dcab04 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -1,15 +1,15 @@
-Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Aspect Oriented Programminghttps://voidframework.dev/doc/advanced/aspect-oriented-programming/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/aspect-oriented-programming/Aspect Oriented Programming (AOP) includes programming methods and tools that support the modularization of concerns at the level of the source code. Void Framework manages the AOP via the AspectJ and Guice libraries. The first library is more powerful but also more complicated to use, while the latter has fewer capabilities but is simple to use.
+Docs on Void Frameworkhttps://voidframework.dev/doc/Recent content in Docs on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/REST Clienthttps://voidframework.dev/doc/rest-client/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/REST Clienthttps://voidframework.dev/doc/rest-client/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Aspect Oriented Programminghttps://voidframework.dev/doc/advanced/aspect-oriented-programming/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/aspect-oriented-programming/Aspect Oriented Programming (AOP) includes programming methods and tools that support the modularization of concerns at the level of the source code. Void Framework manages the AOP via the AspectJ and Guice libraries. The first library is more powerful but also more complicated to use, while the latter has fewer capabilities but is simple to use.
 AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Aspect Oriented Programminghttps://voidframework.dev/doc/advanced/aspect-oriented-programming/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/aspect-oriented-programming/Aspect Oriented Programming (AOP) includes programming methods and tools that support the modularization of concerns at the level of the source code. Void Framework manages the AOP via the AspectJ and Guice libraries. The first library is more powerful but also more complicated to use, while the latter has fewer capabilities but is simple to use.
 AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -36,16 +36,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -53,9 +53,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -66,19 +66,19 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -89,15 +89,23 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
-openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
+openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+Configuration The following configuration key can be used in the configuration file of your application
+voidframework.restclient.maxIdleConnections the number of connection to keep idle.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+Configuration The following configuration key can be used in the configuration file of your application
+voidframework.restclient.maxIdleConnections the number of connection to keep idle.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -109,19 +117,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 314814d..a3f6f51 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -1,10 +1,10 @@
 Void Framework – Using internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/index.html b/doc/nosql-databases/index.html
index 8a08d19..2983ffa 100644
--- a/doc/nosql-databases/index.html
+++ b/doc/nosql-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – NoSQL Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

NoSQL Databases

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

NoSQL Databases

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index 70bf078..d4d7eb8 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -2,15 +2,15 @@
 Installation To enable this module, just add following lines to ">Void Framework – Redis
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 

Example
@Service
 public final class ExampleService {
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index f2d3290..354feb1 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -1,16 +1,16 @@
 Void Framework – Data source
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Data source
Your application needs to connect to one or more databases? Void Framework is capable of handling multiple data sources at the same time through the use of DataSourceManager. It will provide all the necessary methods to obtain a connection from the desired data source. Each data source can be configured independently. Your application can, for example, be connected to PostgreSQL and Oracle at the same time.

Installation
Void Framework offers different implementations, depending on the implementation chosen, the configuration keys may change. Here you will find all the information to fully configure each implementation.
 
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/relational-databases/h2/index.html b/doc/relational-databases/h2/index.html
index 7d5063a..2f7cc29 100644
--- a/doc/relational-databases/h2/index.html
+++ b/doc/relational-databases/h2/index.html
@@ -1,10 +1,10 @@
 Void Framework – H2
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

H2
H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

H2
H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-h2</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.h2.webPort the listen port of the H2 console. The default value is 9002.
voidframework.h2.webAdminPassword the password to access preferences and tools of H2 console. The default value is sa.
voidframework.h2.webAllowOthers specifies if other computers are allowed to connect. The default value is false.

Open the web console
Once your application has started, you can access the H2 web console by going to http://127.0.0.1:9002.
 
 Note that H2 web console will be started only if the application is run in development mode (voidframework.core.runInDevMode = true).

© 2022-2023 Void Framework

diff --git a/doc/relational-databases/index.html b/doc/relational-databases/index.html
index 08a7812..0018263 100644
--- a/doc/relational-databases/index.html
+++ b/doc/relational-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Relational Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Relational Databases

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Relational Databases

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index 1a91c8c..9a6b31d 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -2,11 +2,11 @@
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined b">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Hibernate
Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 

Working with transaction manually
final EntityManager entityManager = this.entityManagerProvider.get();
 final EntityTransaction transaction = entityManager.getTransaction();
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index e3190c5..eeda456 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -2,10 +2,10 @@
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provid">Void Framework – Hibernate
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-jooq</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 

Generator
To work, jOOQ needs files generated during the compilation of the project. It is possible to generate the required classes in different ways (scan database, scan entity, …). For more information, please visit the official jOOQ website.
To enable code generation, add & customize the code below.
pom.xml
<build>
     <plugins>
diff --git a/doc/relational-databases/transactional/index.html b/doc/relational-databases/transactional/index.html
index 076e95d..3479cf0 100644
--- a/doc/relational-databases/transactional/index.html
+++ b/doc/relational-databases/transactional/index.html
@@ -1,7 +1,7 @@
 Void Framework – Transactional
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Transactional
It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional (Jakarta) annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Transactional
It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional (Jakarta) annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
 Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
diff --git a/doc/rest-client/index.html b/doc/rest-client/index.html
new file mode 100644
index 0000000..a9f1927
--- /dev/null
+++ b/doc/rest-client/index.html
@@ -0,0 +1,8 @@
+Void Framework – REST Client
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

REST Client

© 2022-2023 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/rest-client/retrofit2/index.html b/doc/rest-client/retrofit2/index.html
new file mode 100644
index 0000000..d73cc7d
--- /dev/null
+++ b/doc/rest-client/retrofit2/index.html
@@ -0,0 +1,54 @@
+Void Framework – Retrofit 2
+Void Framework
Documentation
+   
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Retrofit 2
Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+    <groupId>dev.voidframework</groupId>
+    <artifactId>voidframework-restclient</artifactId>
+    <version>1.9.0</version>
+</dependency>
+

How it work
All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.

Configuration
The following configuration key can be used in the configuration file of your application
voidframework.restclient.maxIdleConnections the number of connection to keep idle. The default value is 5.
voidframework.restclient.keepAliveDuration the duration for which connections will be kept idle before being closed. The default value is 5 minutes.
voidframework.restclient.connectionTimeout the connect timeout duration. The default value is 15 seconds.
voidframework.restclient.readTimeout the read timeout duration. The default value is 35 seconds.
voidframework.restclient.<service-name>.endpoint the URL endpoint of the service to call.
voidframework.restclient.<service-name>.maxIdleConnections the number of connection to keep idle for the given service. The default value is 5.
voidframework.restclient.<service-name>.keepAliveDuration the duration for which connections will be kept idle before being closed for the given service. The default value is 5 minutes.
voidframework.restclient.<service-name>.connectionTimeout the connect timeout duration for the given service. The default value is 15 seconds.
voidframework.restclient.<service-name>.readTimeout the read timeout duration for the given service. The default value is 35 seconds.

Examples
voidframework {
+    restclient {
+
+        maxIdleConnections = 10
+
+        echo-api {
+
+            endpoint = "https://postman-echo.com"
+            maxIdleConnections = 1
+            readTimeout = "15 seconds"
+        }
+    }
+}
+
@RestClient("echo-api")
+private interface EchoApiRestClient {
+
+    @GET("/get")
+    String echo(@Query("msg") final String message);
+
+    @POST("/post")
+    @Headers("Content-Type: application/json")
+    JsonNode postJsonNode(@Body final JsonNode message);
+}
+
@Service
+private class SampleService {
+
+    private final EchoApiRestClient echoApiRestClient;
+
+    @Inject
+    public SampleService(final EchoApiRestClient echoApiRestClient) {
+        
+        this.echoApiRestClient = echoApiRestClient;
+    }
+
+    public String mySample() {
+        
+        return this.echoApiRestClient.echo("Hello World");
+    }
+}
+

© 2022-2023 Void Framework

+Void Framework is released under the MIT License

+
+
+
\ No newline at end of file
diff --git a/doc/scheduler/index.html b/doc/scheduler/index.html
index 6a758be..8cce302 100644
--- a/doc/scheduler/index.html
+++ b/doc/scheduler/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduler
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Scheduler

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Scheduler

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index 8d9ac15..bdcd97d 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -1,10 +1,10 @@
 Void Framework – Scheduling a local job
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-scheduler</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron a CRON-like expression. The default value is empty (disabled).
cronZone the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
 public final class Ping {
diff --git a/doc/sendmail/index.html b/doc/sendmail/index.html
index 823bf0f..b2a7bd7 100644
--- a/doc/sendmail/index.html
+++ b/doc/sendmail/index.html
@@ -1,7 +1,7 @@
 Void Framework – Sendmail
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Sendmail

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Sendmail

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/sendmail/mailer-apache-commons-email/index.html b/doc/sendmail/mailer-apache-commons-email/index.html
index 5362d7b..1eb0203 100644
--- a/doc/sendmail/mailer-apache-commons-email/index.html
+++ b/doc/sendmail/mailer-apache-commons-email/index.html
@@ -2,10 +2,10 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsema">Void Framework – Mailer : Apache Commons Email
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Mailer : Apache Commons Email
This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Mailer : Apache Commons Email
This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail-commonsemail</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.commonsemail.username user name for authentication. The default value is null.
voidframework.sendmail.commonsemail.password password for authentication. The default value is null.
This module also includes many of the configuration keys of the Java Mail properties. To use it, simply prefix them with voidframework.sendmail.commonsemail.. Here is the list of possible properties:
https://javaee.github.io/javamail/docs/api/javax/mail/internet/package-summary.html
mail.mime.address.usecanonicalhostname
mail.mime.allowencodedmessages
mail.mime.applefilenames
mail.mime.base64.ignoreerrors
mail.mime.charset
mail.mime.contenttypehandler
mail.mime.decodefilename
mail.mime.decodeparameters
mail.mime.decodetext.strict
mail.mime.encodeeol.strict
mail.mime.encodefilename
mail.mime.encodeparameters
mail.mime.foldtext
mail.mime.ignoremultipartencoding
mail.mime.ignoreunknownencoding
mail.mime.ignorewhitespacelines
mail.mime.multipart.allowempty
mail.mime.multipart.ignoreexistingboundaryparameter
mail.mime.multipart.ignoremissingboundaryparameter
mail.mime.multipart.ignoremissingendboundary
mail.mime.parameters.strict
mail.mime.setcontenttypefilename
mail.mime.setdefaulttextcharset
mail.mime.uudecode.ignoreerrors
mail.mime.uudecode.ignoremissingbeginend
mail.mime.windowsfilenames
https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html
mail.smtp.user
mail.smtp.host
mail.smtp.port
mail.smtp.connectiontimeout
mail.smtp.timeout
mail.smtp.writetimeout
mail.smtp.from
mail.smtp.localhost
mail.smtp.localaddress
mail.smtp.localport
mail.smtp.ehlo
mail.smtp.auth
mail.smtp.auth.mechanisms
mail.smtp.auth.login.disable
mail.smtp.auth.plain.disable
mail.smtp.auth.digest-md5.disable
mail.smtp.auth.ntlm.disable
mail.smtp.auth.ntlm.domain
mail.smtp.auth.ntlm.flags
mail.smtp.auth.xoauth2.disable
mail.smtp.submitter
mail.smtp.dsn.notify
mail.smtp.dsn.ret
mail.smtp.allow8bitmime
mail.smtp.sendpartial
mail.smtp.sasl.enable
mail.smtp.sasl.mechanisms
mail.smtp.sasl.authorizationid
mail.smtp.sasl.realm
mail.smtp.sasl.usecanonicalhostname
mail.smtp.quitwait
mail.smtp.reportsuccess
mail.smtp.socketFactory
mail.smtp.socketFactory.class
mail.smtp.socketFactory.fallback
mail.smtp.socketFactory.port
mail.smtp.ssl.enable
mail.smtp.ssl.checkserveridentity
mail.smtp.ssl.trust
mail.smtp.ssl.socketFactory
mail.smtp.ssl.socketFactory.class
mail.smtp.ssl.socketFactory.port
mail.smtp.ssl.protocols
mail.smtp.ssl.ciphersuites
mail.smtp.starttls.enable
mail.smtp.starttls.required
mail.smtp.proxy.host
mail.smtp.proxy.port
mail.smtp.proxy.user
mail.smtp.proxy.password
mail.smtp.socks.host
mail.smtp.socks.port
mail.smtp.mailextension
mail.smtp.userset
mail.smtp.noop.strict

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/sendmail/mailer-dummy/index.html b/doc/sendmail/mailer-dummy/index.html
index 53ea122..2ce6834 100644
--- a/doc/sendmail/mailer-dummy/index.html
+++ b/doc/sendmail/mailer-dummy/index.html
@@ -2,7 +2,7 @@
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframewor">Void Framework – Mailer : Dummy
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Mailer : Dummy
This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.

Installation
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Mailer : Dummy
This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.

Installation
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/sendmail/sending-emails/index.html b/doc/sendmail/sending-emails/index.html
index 77d1dbb..11804ea 100644
--- a/doc/sendmail/sending-emails/index.html
+++ b/doc/sendmail/sending-emails/index.html
@@ -2,10 +2,10 @@
 Installation &lt;dependency&">Void Framework – Sending emails
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Sending emails
If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Sending emails
If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 
In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail module

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.engine the mailer implementation to use. The default value is null.
voidframework.sendmail.mailQueuePollTimeout the time to wait before giving up when retrieving a mail to be sent from the queue of mail waiting to be sent when the queue is empty. The default value is 2 seconds.
voidframework.sendmail.gracefulStopTimeout the time for the daemon to shut down properly before it was terminated. The default value is 15 seconds.

Examples
@BindClass
 public final class Service {
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index e930e33..691dcc0 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -2,10 +2,10 @@
 Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifact">Void Framework – FreeMarker
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/doc/template/index.html b/doc/template/index.html
index 0e43fc3..740e8ad 100644
--- a/doc/template/index.html
+++ b/doc/template/index.html
@@ -1,7 +1,7 @@
 Void Framework – Template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Template

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Template

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/template/using-template/index.html b/doc/template/using-template/index.html
index 0420696..387a53f 100644
--- a/doc/template/using-template/index.html
+++ b/doc/template/using-template/index.html
@@ -2,7 +2,7 @@
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final Temp">Void Framework – Using template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using template
Sooner or later you will need to generate documents (HTML, PDF…). Void Framework provides all the tools you need!

Example
public class TemplateExample {
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using template
Sooner or later you will need to generate documents (HTML, PDF…). Void Framework provides all the tools you need!

Example
public class TemplateExample {
 
     private final TemplateRenderer templateRenderer;
 
diff --git a/doc/testing/index.html b/doc/testing/index.html
index fec63a4..41b4db8 100644
--- a/doc/testing/index.html
+++ b/doc/testing/index.html
@@ -1,7 +1,7 @@
 Void Framework – Testing
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Testing

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Testing

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index 1b3edbd..ca51749 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -2,10 +2,10 @@
 To enable this module, just add following lines to th">Void Framework – JUnit's extension
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
 @ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
diff --git a/doc/vfs/index.html b/doc/vfs/index.html
index c48b8d5..04839d0 100644
--- a/doc/vfs/index.html
+++ b/doc/vfs/index.html
@@ -1,7 +1,7 @@
 Void Framework – Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Virtual File Storage

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Virtual File Storage

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/vfs/using-vfs/index.html b/doc/vfs/using-vfs/index.html
index 5b4a9f8..66a760c 100644
--- a/doc/vfs/using-vfs/index.html
+++ b/doc/vfs/using-vfs/index.html
@@ -1,10 +1,10 @@
 Void Framework – Using Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 

Configuration
Different VirtualFileStorage implementations must be configured in voidframework.vfs namespace. The following configuration keys can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
 Note that each implementation can have extra configuration keys.

Example
voidframework {
diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html
index a2eb541..5b0f348 100644
--- a/doc/web/controller/index.html
+++ b/doc/web/controller/index.html
@@ -1,7 +1,7 @@
 Void Framework – Controller
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Controller
Controllers receive incoming web requests, process them and return a result. They are the entry point to your web application. Controllers can return almost any type of data, as long as it is handled by the Result object. It is a convention imposed by Void Framework that methods which handle incoming requests must return a Result.

Example
@Singleton
 @WebController(prefixRoute = "/account")
 public class AccountController {
 
diff --git a/doc/web/filters/index.html b/doc/web/filters/index.html
index f24bf5a..182dd36 100644
--- a/doc/web/filters/index.html
+++ b/doc/web/filters/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the">Void Framework – Filters
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Filters
Filters are the middleware and are individual functions that make up the request processing pipeline.
 
 Note that the use of dependencies direct injection is possible in filters.

Specific filters
The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
@FilterWith({FirstFilter.java, SecondFilter.java})
 @Singleton
 @WebController
diff --git a/doc/web/index.html b/doc/web/index.html
index 9589c7c..49b1598 100644
--- a/doc/web/index.html
+++ b/doc/web/index.html
@@ -1,7 +1,7 @@
 Void Framework – Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Web

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Web

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/web/render-template/index.html b/doc/web/render-template/index.html
index 51c8363..c01fbea 100644
--- a/doc/web/render-template/index.html
+++ b/doc/web/render-template/index.html
@@ -2,7 +2,7 @@
 Although you can manually use the template engine, in most cases this would not be handy. Howev">Void Framework – Render template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Static files
If you need to include static files in your HTML page (e.g. css, javascript, image, …), you can use the urlfor method with the first parameter static_file or static_webjar and the second parameter the path to the file.

Example
controller/HomeController.java
@Singleton
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Render template
The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.

Built-in methods & variables
By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
flash Contains temporary messages
session Contains the current session data
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
csrfToken Contains the CSRF token
voidFrameworkVersion Contains the current Void Framework version

Templates location
Templates should be placed in the resources/views directory.

Static files
If you need to include static files in your HTML page (e.g. css, javascript, image, …), you can use the urlfor method with the first parameter static_file or static_webjar and the second parameter the path to the file.

Example
controller/HomeController.java
@Singleton
 @WebController
 public class HomeController {
 
diff --git a/doc/web/security-csrf/index.html b/doc/web/security-csrf/index.html
index 01fdf06..1de4e5f 100644
--- a/doc/web/security-csrf/index.html
+++ b/doc/web/security-csrf/index.html
@@ -2,7 +2,7 @@
 &nbsp; It is recommended tha">Void Framework – CSRF
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

CSRF
Cross-site request forgery (CSRF), also known as one-click attack or session riding, is a type of malicious vector attack of a website where unauthorized commands are submitted from a user that the web application trusts.
 
 It is recommended that you familiarize yourself with CSRF. We recommend starting with this information from OWASP.
Void Framework provides a CSRF filter that can be applied globally to all requests or only on specific endpoints.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/security-headers/index.html b/doc/web/security-headers/index.html
index 943ab89..c5bd996 100644
--- a/doc/web/security-headers/index.html
+++ b/doc/web/security-headers/index.html
@@ -2,7 +2,7 @@
 Configuration The following configuration keys can be used in the configuration">Void Framework – Security headers
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Security headers
Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.
 
 You can disable one of the headers by assigning the value null. The header will then not be sent.

Enable
The activation of the CSRF filter is done via the configuration key voidframework.web.globalFilters. Read more about Filters.
voidframework {
 
     web {
diff --git a/doc/web/session/index.html b/doc/web/session/index.html
index a5943a1..5471a73 100644
--- a/doc/web/session/index.html
+++ b/doc/web/session/index.html
@@ -2,7 +2,7 @@
 &nbsp; Note that the session is not stored on the server side, but on the client side v">Void Framework – Session
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Session
If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user’s session.
 
 Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie.

Because session is implemented using cookies, there are some implications.The data size is limited to 4 KiB
Only string can be stored

Configuration
The following configuration keys can be used in the configuration file of your application.
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.

Read value
You can access the session data via the Context. Methods get or getOrDefault can be used.
@Singleton
 @WebController
 public class Controller {
diff --git a/doc/web/using-web/index.html b/doc/web/using-web/index.html
index 58b5d39..c26d651 100644
--- a/doc/web/using-web/index.html
+++ b/doc/web/using-web/index.html
@@ -2,10 +2,10 @@
 Installation To enable this module, just add following lines to the pom.xml ">Void Framework – Using Web
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.8.1</version>
+    <version>1.9.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used.
Base
voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly. The default value is 15 seconds.
voidframework.web.errorHandler the implementation of the error handler to use in case of http error. The default value is dev.voidframework.web.http.errorhandler.DefaultErrorHandler.
voidframework.web.contextPath the default context path root. The default value is /.
voidframework.web.routes a list of routing definition classes (must implement the interface AppRoutesDefinition). The default value is [].
voidframework.web.globalFilters a list of routing global filter classes (must implement the interface Filter). The default value is [].
voidframework.web.baseAssetResourcesDirectory the default location of static files in the “resources” directory. The default value is static.
Server
voidframework.web.server.idleTimeout the time without any request to wait before the connection is closed. The default value is 30 seconds.
voidframework.web.server.extraWebServerConfiguration the implementation of the interface ExtraWebServerConfiguration to apply a custom configuration to the Undertow web server. The default value is null.
voidframework.web.server.ioThreads the number of I/O threads. If not specified (value = null or 0), Math.max(Runtime.getRuntime().availableProcessors(), 2) value will be used. The default value is null.
voidframework.web.server.workerThreads the number of Worker threads. If not specified (value = null or 0), ioThreadsNumber * 8 value will be used. The default value is null.
voidframework.web.server.maxBodySize the max body content size. The default value is 1 MiB.
voidframework.web.server.fileSizeThreshold the maximum size allowed in memory before the uploaded file was stored on the disk rather than in memory. The default value is 256 KiB.
voidframework.web.server.tempFileLocation the location where temporary files will be stored. The default value is null (default Java temporary folder).
HTTP
voidframework.web.server.http.listenHost the interface on which the server will listen for non-secure HTTP requests. The default value is 127.0.0.1.
voidframework.web.server.http.listenPort the port on which the server will listen for non-secure HTTP requests. The default value is 9000.
HTTPS
voidframework.web.server.https.listenHost the interface on which the server will listen for HTTPS requests. The default value is 127.0.0.1.
voidframework.web.server.https.listenPort the port on which the server will listen for HTTPS requests. The default value is 9001.
voidframework.web.server.https.ssl.protocols the protocols to use. The default value is ["TLSv1.2", "TLSv1.3"].
voidframework.web.server.https.ssl.ciphers the allowed ciphers. If list is empty, all ciphers will be allowed. The default value is [].
voidframework.web.server.https.ssl.keyStorePath the path where is located the key store. Could be a “resources” path, a URL or a simple path. The default value is null.
voidframework.web.server.https.ssl.keyStoreType the type of the key store. The default value is JKS.
voidframework.web.server.https.ssl.keyStorePassword the password to use to open the key store. The default value is null.
voidframework.web.server.https.ssl.keyAlias the alias of the key to use. If “null” the key will be choosen automatically. The default value is null.
voidframework.web.server.https.ssl.keyPassword the key password. The default value is ${voidframework.web.server.https.ssl.keyStorePassword}.
Language
voidframework.web.language.availableLanguages the available languages. The default value is ["en", "fr"].
voidframework.web.language.cookieName the name of the cookie containing the current language. The default value is VOID_LANG.
voidframework.web.language.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.language.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Flash messages
voidframework.web.flashMessages.cookieName the name of the cookie containing the current flash messages. The default value is VOID_FLASH.
voidframework.web.flashMessages.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.flashMessages.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Session
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.
CSRF
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.
Security headers
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/index.xml b/index.xml
index a57609a..11295a2 100644
--- a/index.xml
+++ b/index.xml
@@ -1,15 +1,15 @@
-Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Aspect Oriented Programminghttps://voidframework.dev/doc/advanced/aspect-oriented-programming/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/aspect-oriented-programming/Aspect Oriented Programming (AOP) includes programming methods and tools that support the modularization of concerns at the level of the source code. Void Framework manages the AOP via the AspectJ and Guice libraries. The first library is more powerful but also more complicated to use, while the latter has fewer capabilities but is simple to use.
+Void Frameworkhttps://voidframework.dev/Recent content on Void FrameworkHugo -- gohugo.ioGetting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Getting Startedhttps://voidframework.dev/doc/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Corehttps://voidframework.dev/doc/core/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/Relational Databaseshttps://voidframework.dev/doc/relational-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/NoSQL Databaseshttps://voidframework.dev/doc/nosql-databases/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Cachehttps://voidframework.dev/doc/cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/Internationalizationhttps://voidframework.dev/doc/i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/i18n/REST Clienthttps://voidframework.dev/doc/rest-client/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/REST Clienthttps://voidframework.dev/doc/rest-client/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Schedulerhttps://voidframework.dev/doc/scheduler/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Sendmailhttps://voidframework.dev/doc/sendmail/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/Templatehttps://voidframework.dev/doc/template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Virtual File Storagehttps://voidframework.dev/doc/vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Webhttps://voidframework.dev/doc/web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Testinghttps://voidframework.dev/doc/testing/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Advancedhttps://voidframework.dev/doc/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/Aspect Oriented Programminghttps://voidframework.dev/doc/advanced/aspect-oriented-programming/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/aspect-oriented-programming/Aspect Oriented Programming (AOP) includes programming methods and tools that support the modularization of concerns at the level of the source code. Void Framework manages the AOP via the AspectJ and Guice libraries. The first library is more powerful but also more complicated to use, while the latter has fewer capabilities but is simple to use.
 AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Aspect Oriented Programminghttps://voidframework.dev/doc/advanced/aspect-oriented-programming/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/aspect-oriented-programming/Aspect Oriented Programming (AOP) includes programming methods and tools that support the modularization of concerns at the level of the source code. Void Framework manages the AOP via the AspectJ and Guice libraries. The first library is more powerful but also more complicated to use, while the latter has fewer capabilities but is simple to use.
 AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -36,16 +36,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -53,9 +53,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -66,19 +66,19 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -89,15 +89,23 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
 #&gt; java -version You should see something like:
-openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
+openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+Configuration The following configuration key can be used in the configuration file of your application
+voidframework.restclient.maxIdleConnections the number of connection to keep idle.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
+Installation To enable this module, just add following lines to the pom.xml file of your project.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+Configuration The following configuration key can be used in the configuration file of your application
+voidframework.restclient.maxIdleConnections the number of connection to keep idle.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -109,19 +117,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.8.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/sitemap.xml b/sitemap.xml
index 557faa9..a7bf303 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/sendmail/https://voidframework.dev/doc/sendmail/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/aspect-oriented-programming/https://voidframework.dev/doc/advanced/aspect-oriented-programming/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/advanced/creating-module/https://voidframework.dev/doc/advanced/creating-module/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/h2/https://voidframework.dev/doc/relational-databases/h2/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/https://voidframework.dev/doc/sendmail/mailer-dummy/https://voidframework.dev/doc/sendmail/mailer-dummy/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/sendmail/sending-emails/https://voidframework.dev/doc/sendmail/sending-emails/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/template/using-template/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/
\ No newline at end of file
+https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/getting-started/https://voidframework.dev/doc/core/https://voidframework.dev/doc/core/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/relational-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/nosql-databases/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/cache/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/i18n/https://voidframework.dev/doc/rest-client/https://voidframework.dev/doc/rest-client/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/scheduler/https://voidframework.dev/doc/sendmail/https://voidframework.dev/doc/sendmail/https://voidframework.dev/doc/template/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/vfs/https://voidframework.dev/doc/web/https://voidframework.dev/doc/web/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/testing/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/https://voidframework.dev/doc/advanced/aspect-oriented-programming/https://voidframework.dev/doc/advanced/aspect-oriented-programming/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/core/boot-sequence/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/in-memory-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/doc/cache/redis-cache/https://voidframework.dev/categories/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/class-scanning/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/conditional-feature/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/core/configuration/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/web/controller/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/getting-started/new-application/https://voidframework.dev/doc/advanced/creating-module/https://voidframework.dev/doc/advanced/creating-module/https://voidframework.dev/doc/web/security-csrf/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/relational-databases/datasource/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/web/filters/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/template/freemarker/https://voidframework.dev/doc/relational-databases/h2/https://voidframework.dev/doc/relational-databases/h2/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-hibernate/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/relational-databases/persistence-jooq/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/testing/junit-extension/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/lang/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/core/life-cycle/https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/https://voidframework.dev/doc/sendmail/mailer-dummy/https://voidframework.dev/doc/sendmail/mailer-dummy/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/nosql-databases/redis/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/doc/advanced/advanced/https://voidframework.dev/releasenotes/https://voidframework.dev/releasenotes/https://voidframework.dev/doc/web/render-template/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/getting-started/requirements/https://voidframework.dev/doc/rest-client/retrofit2/https://voidframework.dev/doc/rest-client/retrofit2/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/scheduler/scheduling-job-cron/https://voidframework.dev/doc/web/security-headers/https://voidframework.dev/doc/sendmail/sending-emails/https://voidframework.dev/doc/sendmail/sending-emails/https://voidframework.dev/doc/web/session/https://voidframework.dev/doc/web/session/https://voidframework.dev/tags/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/relational-databases/transactional/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/core/type-conversion/https://voidframework.dev/doc/getting-started/upgrading-from-old-version/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/cache/using-cache/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/internationalization/using-i18n/https://voidframework.dev/doc/template/using-template/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/vfs/using-vfs/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/doc/web/using-web/https://voidframework.dev/
\ No newline at end of file

From 3a5b728707b3cbc33befe949ae2849076b615c4e Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Sat, 9 Sep 2023 05:58:24 +0000
Subject: [PATCH 56/75] Automated website build

---
 doc/index.xml                                        | 4 ++--
 doc/relational-databases/persistence-jooq/index.html | 6 +++---
 index.xml                                            | 4 ++--
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/doc/index.xml b/doc/index.xml
index 3dcab04..85f8cfe 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -47,9 +47,9 @@ Installation To enable this module, just add following lines to the pom.xml file
 Installation To enable this module, just add following lines to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.jOOQ ORMhttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.jOOQ ORMhttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index eeda456..3d4076e 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -1,8 +1,8 @@
-Void Framework – Hibernate
+Void Framework – jOOQ ORM
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Hibernate
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

jOOQ ORM
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-jooq</artifactId>
     <version>1.9.0</version>
diff --git a/index.xml b/index.xml
index 11295a2..ea8235b 100644
--- a/index.xml
+++ b/index.xml
@@ -47,9 +47,9 @@ Installation To enable this module, just add following lines to the pom.xml file
 Installation To enable this module, just add following lines to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
-&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.jOOQ ORMhttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.jOOQ ORMhttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.

From f7663ede57eb102022841cb45b6d5829efa5eeb8 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Mon, 11 Sep 2023 07:20:27 +0000
Subject: [PATCH 57/75] Automated website build

---
 doc/advanced/aspect-oriented-programming/index.html | 2 +-
 doc/rest-client/retrofit2/index.html                | 4 +++-
 index.xml                                           | 2 +-
 releasenotes/index.html                             | 5 +++--
 4 files changed, 8 insertions(+), 5 deletions(-)

diff --git a/doc/advanced/aspect-oriented-programming/index.html b/doc/advanced/aspect-oriented-programming/index.html
index b50499e..d51efb3 100644
--- a/doc/advanced/aspect-oriented-programming/index.html
+++ b/doc/advanced/aspect-oriented-programming/index.html
@@ -12,7 +12,7 @@
         <dependency>
             <groupId>org.aspectj</groupId>
             <artifactId>aspectjtools</artifactId>
-            <version>1.9.19</version> <!-- Min. version to handle Java 17 -->
+            <version>1.9.20.1</version> <!-- Min. version to handle Java 17 is 1.9.19 -->
         </dependency>
     </dependencies>
     
diff --git a/doc/rest-client/retrofit2/index.html b/doc/rest-client/retrofit2/index.html
index d73cc7d..90e8e73 100644
--- a/doc/rest-client/retrofit2/index.html
+++ b/doc/rest-client/retrofit2/index.html
@@ -8,7 +8,9 @@
     <artifactId>voidframework-restclient</artifactId>
     <version>1.9.0</version>
 </dependency>
-

How it work
All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.

Configuration
The following configuration key can be used in the configuration file of your application
voidframework.restclient.maxIdleConnections the number of connection to keep idle. The default value is 5.
voidframework.restclient.keepAliveDuration the duration for which connections will be kept idle before being closed. The default value is 5 minutes.
voidframework.restclient.connectionTimeout the connect timeout duration. The default value is 15 seconds.
voidframework.restclient.readTimeout the read timeout duration. The default value is 35 seconds.
voidframework.restclient.<service-name>.endpoint the URL endpoint of the service to call.
voidframework.restclient.<service-name>.maxIdleConnections the number of connection to keep idle for the given service. The default value is 5.
voidframework.restclient.<service-name>.keepAliveDuration the duration for which connections will be kept idle before being closed for the given service. The default value is 5 minutes.
voidframework.restclient.<service-name>.connectionTimeout the connect timeout duration for the given service. The default value is 15 seconds.
voidframework.restclient.<service-name>.readTimeout the read timeout duration for the given service. The default value is 35 seconds.

Examples
voidframework {
+

How it work
All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.

Configuration
The following configuration key can be used in the configuration file of your application
voidframework.restclient.maxIdleConnections the number of connection to keep idle. The default value is 5.
voidframework.restclient.keepAliveDuration the duration for which connections will be kept idle before being closed. The default value is 5 minutes.
voidframework.restclient.connectionTimeout the connect timeout duration. The default value is 15 seconds.
voidframework.restclient.readTimeout the read timeout duration. The default value is 35 seconds.
voidframework.restclient.authentication.type the authentication type to use (API_KEY, BASIC or BEARER). The default value is null (disabled).
voidframework.restclient.authentication.apiKeyName the API key variable name. This setting is only used if the authentication type is set to API_KEY. The default value is null.
voidframework.restclient.authentication.apiKeyValue the API key variable value. This setting is only used if the authentication type is set to API_KEY. The default value is null.
voidframework.restclient.authentication.apiKeyAddTo where to add the API key (COOKIE, HEADER, QUERY_PARAMETER). This setting is only used if the authentication type is set to API_KEY. The default value is HEADER.
voidframework.restclient.authentication.basicUsername the basic authentication username. This setting is only used if the authentication type is set to BASIC. The default value is null.
voidframework.restclient.authentication.basicPassword the basic authentication password. This setting is only used if the authentication type is set to BASIC. The default value is null.
voidframework.restclient.authentication.basicUseISO88591Encoding use ISO-8859-1 encoding rather than UTF-8. This setting is only used if the authentication type is set to BASIC. The default value is false.
voidframework.restclient.authentication.bearerPrefix the bearer prefix to use in the request header. This setting is only used if the authentication type is set to BEARER. The default value is Bearer.
voidframework.restclient.authentication.bearerToken the bearer token to use in the request header. This setting is only used if the authentication type is set to BEARER. The default value is null.
 
+You can override the global configuration for a specific service by using the following configuration key:
+voidframework.restclient.<service-name>.xxx

ie: voidframework.restclient.echo-api.readTimeout

Examples
voidframework {
     restclient {
 
         maxIdleConnections = 10
diff --git a/index.xml b/index.xml
index ea8235b..4a866d1 100644
--- a/index.xml
+++ b/index.xml
@@ -81,7 +81,7 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.7.0 2023-04-12 Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492) New Conditional feature RunInDevModeConditionalFeature New Sendmail module New Sendmail module implementation Apache Commons Email New Add @CachePut annotation Improved Javadoc Improved HttpClient is now used instead of raw URL connection (Remote Configuration) Improved Result: method badRequest(final String content, final String contentType) Improved Updated version of all dependencies Fixed Transactional annotation multiple calls 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.10.0 2023-09-11 New REST Client authentication (API Key, Basic, Bearer) Improved New constant values: CharConstants.EXCLAMATION_MARK, CharConstants.PIPE, StringConstants.EXCLAMATION_MARK and StringConstants.PIPE Improved Upgrade dependencies 1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.10.0 2023-09-11 New REST Client authentication (API Key, Basic, Bearer) Improved New constant values: CharConstants.EXCLAMATION_MARK, CharConstants.PIPE, StringConstants.EXCLAMATION_MARK and StringConstants.PIPE Improved Upgrade dependencies 1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 54b736f..917c09d 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,7 +1,8 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.9.0

+Release notes
1.10.0

+2023-09-11
New REST Client authentication (API Key, Basic, Bearer)
Improved New constant values: CharConstants.EXCLAMATION_MARK, CharConstants.PIPE, StringConstants.EXCLAMATION_MARK and StringConstants.PIPE
Improved Upgrade dependencies

1.9.0

 2023-07-13
New AspectJ
New REST client
New Bucket4J (rate-limiting)
New Add ConfigurationUtils class
Improved Upgrade dependencies
Improved New constant value: CharConstants.TAB and StringConstants.TAB

1.8.1

 2023-16-16
Improved Add exception AppLauncherException.ModuleConstructorNotFound

1.8.0

 2023-05-18
New Proxyable interface
New H2 web console
Improved Bind automatically interface with single implementation
Improved Updated version of all dependencies
Fixed Guice module implementing interface not recognized

1.7.0


From 1034c36b554282f98a7fa41913c4eef280ca9d2e Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Mon, 11 Sep 2023 07:21:08 +0000
Subject: [PATCH 58/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/redis-cache/index.html              |  4 +-
 doc/core/configuration/index.html             |  4 +-
 .../new-application/index.html                |  4 +-
 doc/index.xml                                 | 48 +++++++++----------
 .../using-i18n/index.html                     |  2 +-
 doc/nosql-databases/redis/index.html          |  4 +-
 .../datasource/index.html                     |  4 +-
 doc/relational-databases/h2/index.html        |  2 +-
 .../persistence-hibernate/index.html          |  2 +-
 .../persistence-jooq/index.html               |  2 +-
 doc/rest-client/retrofit2/index.html          |  2 +-
 doc/scheduler/scheduling-job-cron/index.html  |  2 +-
 .../mailer-apache-commons-email/index.html    |  2 +-
 doc/sendmail/sending-emails/index.html        |  2 +-
 doc/template/freemarker/index.html            |  2 +-
 doc/testing/junit-extension/index.html        |  2 +-
 doc/vfs/using-vfs/index.html                  |  2 +-
 doc/web/using-web/index.html                  |  2 +-
 index.xml                                     | 48 +++++++++----------
 20 files changed, 71 insertions(+), 71 deletions(-)

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index b034f25..da63908 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index ed97892..ee71650 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -1,11 +1,11 @@
 Void Framework – Cache engine : Redis
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.10">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index e342e99..7e1b4fa 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -25,7 +25,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.9.0</version>
+  <version>1.10.0</version>
 </dependency>
 
voidframework {
     code {
@@ -60,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.9.0</version>
+  <version>1.10.0</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 88dd2e0..5891962 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/index.xml b/doc/index.xml
index 85f8cfe..1de63e1 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -3,13 +3,13 @@ AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframew
 AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -36,16 +36,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.jOOQ ORMhttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -53,9 +53,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -66,19 +66,19 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -91,11 +91,11 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
@@ -104,8 +104,8 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -117,19 +117,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index a3f6f51..14753fa 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index d4d7eb8..69bc5a4 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 

Example
@Service
 public final class ExampleService {
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index 354feb1..28eb1c8 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -5,12 +5,12 @@
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/relational-databases/h2/index.html b/doc/relational-databases/h2/index.html
index 2f7cc29..955bc1d 100644
--- a/doc/relational-databases/h2/index.html
+++ b/doc/relational-databases/h2/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

H2
H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-h2</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.h2.webPort the listen port of the H2 console. The default value is 9002.
voidframework.h2.webAdminPassword the password to access preferences and tools of H2 console. The default value is sa.
voidframework.h2.webAllowOthers specifies if other computers are allowed to connect. The default value is false.

Open the web console
Once your application has started, you can access the H2 web console by going to http://127.0.0.1:9002.
 
 Note that H2 web console will be started only if the application is run in development mode (voidframework.core.runInDevMode = true).

© 2022-2023 Void Framework

diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index 9a6b31d..6fe0840 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -6,7 +6,7 @@
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 

Working with transaction manually
final EntityManager entityManager = this.entityManagerProvider.get();
 final EntityTransaction transaction = entityManager.getTransaction();
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index 3d4076e..1d8d0cd 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

jOOQ ORM
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-jooq</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 

Generator
To work, jOOQ needs files generated during the compilation of the project. It is possible to generate the required classes in different ways (scan database, scan entity, …). For more information, please visit the official jOOQ website.
To enable code generation, add & customize the code below.
pom.xml
<build>
     <plugins>
diff --git a/doc/rest-client/retrofit2/index.html b/doc/rest-client/retrofit2/index.html
index 90e8e73..a0d70ec 100644
--- a/doc/rest-client/retrofit2/index.html
+++ b/doc/rest-client/retrofit2/index.html
@@ -6,7 +6,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Retrofit 2
Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-restclient</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 

How it work
All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.

Configuration
The following configuration key can be used in the configuration file of your application
voidframework.restclient.maxIdleConnections the number of connection to keep idle. The default value is 5.
voidframework.restclient.keepAliveDuration the duration for which connections will be kept idle before being closed. The default value is 5 minutes.
voidframework.restclient.connectionTimeout the connect timeout duration. The default value is 15 seconds.
voidframework.restclient.readTimeout the read timeout duration. The default value is 35 seconds.
voidframework.restclient.authentication.type the authentication type to use (API_KEY, BASIC or BEARER). The default value is null (disabled).
voidframework.restclient.authentication.apiKeyName the API key variable name. This setting is only used if the authentication type is set to API_KEY. The default value is null.
voidframework.restclient.authentication.apiKeyValue the API key variable value. This setting is only used if the authentication type is set to API_KEY. The default value is null.
voidframework.restclient.authentication.apiKeyAddTo where to add the API key (COOKIE, HEADER, QUERY_PARAMETER). This setting is only used if the authentication type is set to API_KEY. The default value is HEADER.
voidframework.restclient.authentication.basicUsername the basic authentication username. This setting is only used if the authentication type is set to BASIC. The default value is null.
voidframework.restclient.authentication.basicPassword the basic authentication password. This setting is only used if the authentication type is set to BASIC. The default value is null.
voidframework.restclient.authentication.basicUseISO88591Encoding use ISO-8859-1 encoding rather than UTF-8. This setting is only used if the authentication type is set to BASIC. The default value is false.
voidframework.restclient.authentication.bearerPrefix the bearer prefix to use in the request header. This setting is only used if the authentication type is set to BEARER. The default value is Bearer.
voidframework.restclient.authentication.bearerToken the bearer token to use in the request header. This setting is only used if the authentication type is set to BEARER. The default value is null.
 
 You can override the global configuration for a specific service by using the following configuration key:
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index bdcd97d..b7da69a 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-scheduler</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron a CRON-like expression. The default value is empty (disabled).
cronZone the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
 public final class Ping {
diff --git a/doc/sendmail/mailer-apache-commons-email/index.html b/doc/sendmail/mailer-apache-commons-email/index.html
index 1eb0203..1448a93 100644
--- a/doc/sendmail/mailer-apache-commons-email/index.html
+++ b/doc/sendmail/mailer-apache-commons-email/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Mailer : Apache Commons Email
This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail-commonsemail</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.commonsemail.username user name for authentication. The default value is null.
voidframework.sendmail.commonsemail.password password for authentication. The default value is null.
This module also includes many of the configuration keys of the Java Mail properties. To use it, simply prefix them with voidframework.sendmail.commonsemail.. Here is the list of possible properties:
https://javaee.github.io/javamail/docs/api/javax/mail/internet/package-summary.html
mail.mime.address.usecanonicalhostname
mail.mime.allowencodedmessages
mail.mime.applefilenames
mail.mime.base64.ignoreerrors
mail.mime.charset
mail.mime.contenttypehandler
mail.mime.decodefilename
mail.mime.decodeparameters
mail.mime.decodetext.strict
mail.mime.encodeeol.strict
mail.mime.encodefilename
mail.mime.encodeparameters
mail.mime.foldtext
mail.mime.ignoremultipartencoding
mail.mime.ignoreunknownencoding
mail.mime.ignorewhitespacelines
mail.mime.multipart.allowempty
mail.mime.multipart.ignoreexistingboundaryparameter
mail.mime.multipart.ignoremissingboundaryparameter
mail.mime.multipart.ignoremissingendboundary
mail.mime.parameters.strict
mail.mime.setcontenttypefilename
mail.mime.setdefaulttextcharset
mail.mime.uudecode.ignoreerrors
mail.mime.uudecode.ignoremissingbeginend
mail.mime.windowsfilenames
https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html
mail.smtp.user
mail.smtp.host
mail.smtp.port
mail.smtp.connectiontimeout
mail.smtp.timeout
mail.smtp.writetimeout
mail.smtp.from
mail.smtp.localhost
mail.smtp.localaddress
mail.smtp.localport
mail.smtp.ehlo
mail.smtp.auth
mail.smtp.auth.mechanisms
mail.smtp.auth.login.disable
mail.smtp.auth.plain.disable
mail.smtp.auth.digest-md5.disable
mail.smtp.auth.ntlm.disable
mail.smtp.auth.ntlm.domain
mail.smtp.auth.ntlm.flags
mail.smtp.auth.xoauth2.disable
mail.smtp.submitter
mail.smtp.dsn.notify
mail.smtp.dsn.ret
mail.smtp.allow8bitmime
mail.smtp.sendpartial
mail.smtp.sasl.enable
mail.smtp.sasl.mechanisms
mail.smtp.sasl.authorizationid
mail.smtp.sasl.realm
mail.smtp.sasl.usecanonicalhostname
mail.smtp.quitwait
mail.smtp.reportsuccess
mail.smtp.socketFactory
mail.smtp.socketFactory.class
mail.smtp.socketFactory.fallback
mail.smtp.socketFactory.port
mail.smtp.ssl.enable
mail.smtp.ssl.checkserveridentity
mail.smtp.ssl.trust
mail.smtp.ssl.socketFactory
mail.smtp.ssl.socketFactory.class
mail.smtp.ssl.socketFactory.port
mail.smtp.ssl.protocols
mail.smtp.ssl.ciphersuites
mail.smtp.starttls.enable
mail.smtp.starttls.required
mail.smtp.proxy.host
mail.smtp.proxy.port
mail.smtp.proxy.user
mail.smtp.proxy.password
mail.smtp.socks.host
mail.smtp.socks.port
mail.smtp.mailextension
mail.smtp.userset
mail.smtp.noop.strict

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/sendmail/sending-emails/index.html b/doc/sendmail/sending-emails/index.html
index 11804ea..0c9c47f 100644
--- a/doc/sendmail/sending-emails/index.html
+++ b/doc/sendmail/sending-emails/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Sending emails
If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 
In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail module

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.engine the mailer implementation to use. The default value is null.
voidframework.sendmail.mailQueuePollTimeout the time to wait before giving up when retrieving a mail to be sent from the queue of mail waiting to be sent when the queue is empty. The default value is 2 seconds.
voidframework.sendmail.gracefulStopTimeout the time for the daemon to shut down properly before it was terminated. The default value is 15 seconds.

Examples
@BindClass
 public final class Service {
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index 691dcc0..4abbf3c 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index ca51749..9e9fc87 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
 @ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
diff --git a/doc/vfs/using-vfs/index.html b/doc/vfs/using-vfs/index.html
index 66a760c..f1197a8 100644
--- a/doc/vfs/using-vfs/index.html
+++ b/doc/vfs/using-vfs/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 

Configuration
Different VirtualFileStorage implementations must be configured in voidframework.vfs namespace. The following configuration keys can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
 Note that each implementation can have extra configuration keys.

Example
voidframework {
diff --git a/doc/web/using-web/index.html b/doc/web/using-web/index.html
index c26d651..5dd9f12 100644
--- a/doc/web/using-web/index.html
+++ b/doc/web/using-web/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.9.0</version>
+    <version>1.10.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used.
Base
voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly. The default value is 15 seconds.
voidframework.web.errorHandler the implementation of the error handler to use in case of http error. The default value is dev.voidframework.web.http.errorhandler.DefaultErrorHandler.
voidframework.web.contextPath the default context path root. The default value is /.
voidframework.web.routes a list of routing definition classes (must implement the interface AppRoutesDefinition). The default value is [].
voidframework.web.globalFilters a list of routing global filter classes (must implement the interface Filter). The default value is [].
voidframework.web.baseAssetResourcesDirectory the default location of static files in the “resources” directory. The default value is static.
Server
voidframework.web.server.idleTimeout the time without any request to wait before the connection is closed. The default value is 30 seconds.
voidframework.web.server.extraWebServerConfiguration the implementation of the interface ExtraWebServerConfiguration to apply a custom configuration to the Undertow web server. The default value is null.
voidframework.web.server.ioThreads the number of I/O threads. If not specified (value = null or 0), Math.max(Runtime.getRuntime().availableProcessors(), 2) value will be used. The default value is null.
voidframework.web.server.workerThreads the number of Worker threads. If not specified (value = null or 0), ioThreadsNumber * 8 value will be used. The default value is null.
voidframework.web.server.maxBodySize the max body content size. The default value is 1 MiB.
voidframework.web.server.fileSizeThreshold the maximum size allowed in memory before the uploaded file was stored on the disk rather than in memory. The default value is 256 KiB.
voidframework.web.server.tempFileLocation the location where temporary files will be stored. The default value is null (default Java temporary folder).
HTTP
voidframework.web.server.http.listenHost the interface on which the server will listen for non-secure HTTP requests. The default value is 127.0.0.1.
voidframework.web.server.http.listenPort the port on which the server will listen for non-secure HTTP requests. The default value is 9000.
HTTPS
voidframework.web.server.https.listenHost the interface on which the server will listen for HTTPS requests. The default value is 127.0.0.1.
voidframework.web.server.https.listenPort the port on which the server will listen for HTTPS requests. The default value is 9001.
voidframework.web.server.https.ssl.protocols the protocols to use. The default value is ["TLSv1.2", "TLSv1.3"].
voidframework.web.server.https.ssl.ciphers the allowed ciphers. If list is empty, all ciphers will be allowed. The default value is [].
voidframework.web.server.https.ssl.keyStorePath the path where is located the key store. Could be a “resources” path, a URL or a simple path. The default value is null.
voidframework.web.server.https.ssl.keyStoreType the type of the key store. The default value is JKS.
voidframework.web.server.https.ssl.keyStorePassword the password to use to open the key store. The default value is null.
voidframework.web.server.https.ssl.keyAlias the alias of the key to use. If “null” the key will be choosen automatically. The default value is null.
voidframework.web.server.https.ssl.keyPassword the key password. The default value is ${voidframework.web.server.https.ssl.keyStorePassword}.
Language
voidframework.web.language.availableLanguages the available languages. The default value is ["en", "fr"].
voidframework.web.language.cookieName the name of the cookie containing the current language. The default value is VOID_LANG.
voidframework.web.language.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.language.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Flash messages
voidframework.web.flashMessages.cookieName the name of the cookie containing the current flash messages. The default value is VOID_FLASH.
voidframework.web.flashMessages.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.flashMessages.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Session
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.
CSRF
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.
Security headers
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/index.xml b/index.xml
index 4a866d1..f46ee24 100644
--- a/index.xml
+++ b/index.xml
@@ -3,13 +3,13 @@ AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframew
 AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -36,16 +36,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.jOOQ ORMhttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -53,9 +53,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -66,19 +66,19 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.10.0 2023-09-11 New REST Client authentication (API Key, Basic, Bearer) Improved New constant values: CharConstants.EXCLAMATION_MARK, CharConstants.PIPE, StringConstants.EXCLAMATION_MARK and StringConstants.PIPE Improved Upgrade dependencies 1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.10.0 2023-09-11 New REST Client authentication (API Key, Basic, Bearer) Improved New constant values: CharConstants.EXCLAMATION_MARK, CharConstants.PIPE, StringConstants.EXCLAMATION_MARK and StringConstants.PIPE Improved Upgrade dependencies 1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -91,11 +91,11 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
@@ -104,8 +104,8 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -117,19 +117,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.9.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file

From 91861785a55c8bf6a65eb5fea7878631d0173528 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Mon, 25 Sep 2023 17:43:44 +0000
Subject: [PATCH 59/75] Automated website build

---
 doc/cache/using-cache/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index eff6f9e..f2cbe5b 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -4,7 +4,7 @@
    
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using cache
Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 
 If no CacheEngine implementation was specified, the cache will not be active.
 
-Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

@CachePut
Indicates that the result of the method will be cached regardless value already exists.
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive allows you to provide a configuration key to retrieve the maximum time in milliseconds to wait before giving up and continuing to stop the application. If no key is specified, the default value -1 (no expiration) will be used.

Example
@BindClass
+Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.

Using Cache with annotations
The cache can be used with the following annotations:

@CacheRemove
Indicates that the cache must be evicted.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
evictOn allows you to provide the exception types that must cause a cache eviction. If classes are specified, the cache will only be evicted if the specified exceptions are thrown. The default value is {}.
noEvictOn allows you to provide the exception types that must not cause a cache eviction. The default value is {}.

@CacheResult
Indicates that the result of the method will be cached and reused in future calls.
The annotation accepts the following parameters:
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive the maximum time to live in milliseconds. The default value is -1 (no expiration).

@CachePut
Indicates that the result of the method will be cached regardless value already exists.
key the cache key. It can contains dynamic information via the usage of {class}, {method} and {n} (with n the method argument position). The default value is {class}.{name}.
timeToLive the maximum time to live in milliseconds. The default value is -1 (no expiration).

Example
@BindClass
 public class CacheExample {
 
     @CachePut

From 2010d2bc2c0050bf26533fc5630ae0782909efec Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 19 Oct 2023 19:09:01 +0000
Subject: [PATCH 60/75] Automated website build

---
 doc/nosql-databases/redis/index.html   | 2 +-
 doc/relational-databases/h2/index.html | 2 +-
 index.xml                              | 2 +-
 releasenotes/index.html                | 5 +++--
 4 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index 69bc5a4..2bc9dc2 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -7,7 +7,7 @@
     <artifactId>voidframework-redis</artifactId>
     <version>1.10.0</version>
 </dependency>
-

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
+

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.username the authentication username (Redis 6 ACL). By default, this value is empty.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
     <version>1.10.0</version>
diff --git a/doc/relational-databases/h2/index.html b/doc/relational-databases/h2/index.html
index 955bc1d..050ab48 100644
--- a/doc/relational-databases/h2/index.html
+++ b/doc/relational-databases/h2/index.html
@@ -6,7 +6,7 @@
     <artifactId>voidframework-h2</artifactId>
     <version>1.10.0</version>
 </dependency>
-

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.h2.webPort the listen port of the H2 console. The default value is 9002.
voidframework.h2.webAdminPassword the password to access preferences and tools of H2 console. The default value is sa.
voidframework.h2.webAllowOthers specifies if other computers are allowed to connect. The default value is false.

Open the web console
Once your application has started, you can access the H2 web console by going to http://127.0.0.1:9002. 
+

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.h2.webPort the listen port of the H2 console. The default value is 9002.
voidframework.h2.webAdminPassword the password to access preferences and tools of H2 console. The default value is null (disabled).
voidframework.h2.webAllowOthers specifies if other computers are allowed to connect. The default value is false.

Open the web console
Once your application has started, you can access the H2 web console by going to http://127.0.0.1:9002.
 
 Note that H2 web console will be started only if the application is run in development mode (voidframework.core.runInDevMode = true).

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
diff --git a/index.xml b/index.xml
index f46ee24..925deed 100644
--- a/index.xml
+++ b/index.xml
@@ -81,7 +81,7 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.10.0 2023-09-11 New REST Client authentication (API Key, Basic, Bearer) Improved New constant values: CharConstants.EXCLAMATION_MARK, CharConstants.PIPE, StringConstants.EXCLAMATION_MARK and StringConstants.PIPE Improved Upgrade dependencies 1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.10.0 2023-09-11 New REST Client authentication (API Key, Basic, Bearer) Improved New constant values: CharConstants.EXCLAMATION_MARK, CharConstants.PIPE, StringConstants.EXCLAMATION_MARK and StringConstants.PIPE Improved Upgrade dependencies 1.9.0 2023-07-13 New AspectJ New REST client New Bucket4J (rate-limiting) New Add ConfigurationUtils class Improved Upgrade dependencies Improved New constant value: CharConstants.TAB and StringConstants.TAB 1.8.1 2023-16-16 Improved Add exception AppLauncherException.ModuleConstructorNotFound 1.8.0 2023-05-18 New Proxyable interface New H2 web console Improved Bind automatically interface with single implementation Improved Updated version of all dependencies Fixed Guice module implementing interface not recognized 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.0 2023-20-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "start" lifecycle failure Fixed H2 web console fail to start because password not encoded 1.10.0 2023-09-11 New REST Client authentication (API Key, Basic, Bearer) Improved New constant values: CharConstants.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.0 2023-20-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "start" lifecycle failure Fixed H2 web console fail to start because password not encoded 1.10.0 2023-09-11 New REST Client authentication (API Key, Basic, Bearer) Improved New constant values: CharConstants.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 917c09d..b79425b 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,7 +1,8 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.10.0

+Release notes
1.11.0

+2023-20-19
New Add KryoUtils class
New Add new method ClassResolverUtils::isClassAvailable
New Add new Kryo serializers
New Add MockitoUtils class (spy lambda)
Improved AbstractCacheEngine now using KryoUtils
Improved Add TypedMap static "constructor" methods
Improved Redis ACL authentication (username/password)
Improved Upgrade dependencies
Fixed Application must shutdown on "start" lifecycle failure
Fixed H2 web console fail to start because password not encoded

1.10.0

 2023-09-11
New REST Client authentication (API Key, Basic, Bearer)
Improved New constant values: CharConstants.EXCLAMATION_MARK, CharConstants.PIPE, StringConstants.EXCLAMATION_MARK and StringConstants.PIPE
Improved Upgrade dependencies

1.9.0

 2023-07-13
New AspectJ
New REST client
New Bucket4J (rate-limiting)
New Add ConfigurationUtils class
Improved Upgrade dependencies
Improved New constant value: CharConstants.TAB and StringConstants.TAB

1.8.1

 2023-16-16
Improved Add exception AppLauncherException.ModuleConstructorNotFound

1.8.0


From e41ca635eea53fea443e3a1f6edaaa8c6e97c32f Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 19 Oct 2023 19:11:12 +0000
Subject: [PATCH 61/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/redis-cache/index.html              |  4 +-
 doc/core/configuration/index.html             |  4 +-
 .../new-application/index.html                |  4 +-
 doc/index.xml                                 | 48 +++++++++----------
 .../using-i18n/index.html                     |  2 +-
 doc/nosql-databases/redis/index.html          |  4 +-
 .../datasource/index.html                     |  4 +-
 doc/relational-databases/h2/index.html        |  2 +-
 .../persistence-hibernate/index.html          |  2 +-
 .../persistence-jooq/index.html               |  2 +-
 doc/rest-client/retrofit2/index.html          |  2 +-
 doc/scheduler/scheduling-job-cron/index.html  |  2 +-
 .../mailer-apache-commons-email/index.html    |  2 +-
 doc/sendmail/sending-emails/index.html        |  2 +-
 doc/template/freemarker/index.html            |  2 +-
 doc/testing/junit-extension/index.html        |  2 +-
 doc/vfs/using-vfs/index.html                  |  2 +-
 doc/web/using-web/index.html                  |  2 +-
 index.xml                                     | 48 +++++++++----------
 20 files changed, 71 insertions(+), 71 deletions(-)

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index da63908..b9b7344 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index ee71650..69c5dd2 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -1,11 +1,11 @@
 Void Framework – Cache engine : Redis
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index 7e1b4fa..9030f1d 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -25,7 +25,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.10.0</version>
+  <version>1.11.0</version>
 </dependency>
 
voidframework {
     code {
@@ -60,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.10.0</version>
+  <version>1.11.0</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 5891962..3eeb5e4 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/index.xml b/doc/index.xml
index 1de63e1..0fe942d 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -3,13 +3,13 @@ AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframew
 AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -36,16 +36,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.jOOQ ORMhttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -53,9 +53,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -66,19 +66,19 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -91,11 +91,11 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
@@ -104,8 +104,8 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -117,19 +117,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 14753fa..a3cebd1 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index 2bc9dc2..b7faff8 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.username the authentication username (Redis 6 ACL). By default, this value is empty.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 

Example
@Service
 public final class ExampleService {
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index 28eb1c8..2117ce3 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -5,12 +5,12 @@
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/relational-databases/h2/index.html b/doc/relational-databases/h2/index.html
index 050ab48..0455899 100644
--- a/doc/relational-databases/h2/index.html
+++ b/doc/relational-databases/h2/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

H2
H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-h2</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.h2.webPort the listen port of the H2 console. The default value is 9002.
voidframework.h2.webAdminPassword the password to access preferences and tools of H2 console. The default value is null (disabled).
voidframework.h2.webAllowOthers specifies if other computers are allowed to connect. The default value is false.

Open the web console
Once your application has started, you can access the H2 web console by going to http://127.0.0.1:9002.
 
 Note that H2 web console will be started only if the application is run in development mode (voidframework.core.runInDevMode = true).

© 2022-2023 Void Framework

diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index 6fe0840..b5075cb 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -6,7 +6,7 @@
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 

Working with transaction manually
final EntityManager entityManager = this.entityManagerProvider.get();
 final EntityTransaction transaction = entityManager.getTransaction();
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index 1d8d0cd..3157a45 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

jOOQ ORM
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-jooq</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 

Generator
To work, jOOQ needs files generated during the compilation of the project. It is possible to generate the required classes in different ways (scan database, scan entity, …). For more information, please visit the official jOOQ website.
To enable code generation, add & customize the code below.
pom.xml
<build>
     <plugins>
diff --git a/doc/rest-client/retrofit2/index.html b/doc/rest-client/retrofit2/index.html
index a0d70ec..c634aaa 100644
--- a/doc/rest-client/retrofit2/index.html
+++ b/doc/rest-client/retrofit2/index.html
@@ -6,7 +6,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Retrofit 2
Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-restclient</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 

How it work
All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.

Configuration
The following configuration key can be used in the configuration file of your application
voidframework.restclient.maxIdleConnections the number of connection to keep idle. The default value is 5.
voidframework.restclient.keepAliveDuration the duration for which connections will be kept idle before being closed. The default value is 5 minutes.
voidframework.restclient.connectionTimeout the connect timeout duration. The default value is 15 seconds.
voidframework.restclient.readTimeout the read timeout duration. The default value is 35 seconds.
voidframework.restclient.authentication.type the authentication type to use (API_KEY, BASIC or BEARER). The default value is null (disabled).
voidframework.restclient.authentication.apiKeyName the API key variable name. This setting is only used if the authentication type is set to API_KEY. The default value is null.
voidframework.restclient.authentication.apiKeyValue the API key variable value. This setting is only used if the authentication type is set to API_KEY. The default value is null.
voidframework.restclient.authentication.apiKeyAddTo where to add the API key (COOKIE, HEADER, QUERY_PARAMETER). This setting is only used if the authentication type is set to API_KEY. The default value is HEADER.
voidframework.restclient.authentication.basicUsername the basic authentication username. This setting is only used if the authentication type is set to BASIC. The default value is null.
voidframework.restclient.authentication.basicPassword the basic authentication password. This setting is only used if the authentication type is set to BASIC. The default value is null.
voidframework.restclient.authentication.basicUseISO88591Encoding use ISO-8859-1 encoding rather than UTF-8. This setting is only used if the authentication type is set to BASIC. The default value is false.
voidframework.restclient.authentication.bearerPrefix the bearer prefix to use in the request header. This setting is only used if the authentication type is set to BEARER. The default value is Bearer.
voidframework.restclient.authentication.bearerToken the bearer token to use in the request header. This setting is only used if the authentication type is set to BEARER. The default value is null.
 
 You can override the global configuration for a specific service by using the following configuration key:
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index b7da69a..1f6b8bc 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-scheduler</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron a CRON-like expression. The default value is empty (disabled).
cronZone the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
 public final class Ping {
diff --git a/doc/sendmail/mailer-apache-commons-email/index.html b/doc/sendmail/mailer-apache-commons-email/index.html
index 1448a93..90f9554 100644
--- a/doc/sendmail/mailer-apache-commons-email/index.html
+++ b/doc/sendmail/mailer-apache-commons-email/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Mailer : Apache Commons Email
This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail-commonsemail</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.commonsemail.username user name for authentication. The default value is null.
voidframework.sendmail.commonsemail.password password for authentication. The default value is null.
This module also includes many of the configuration keys of the Java Mail properties. To use it, simply prefix them with voidframework.sendmail.commonsemail.. Here is the list of possible properties:
https://javaee.github.io/javamail/docs/api/javax/mail/internet/package-summary.html
mail.mime.address.usecanonicalhostname
mail.mime.allowencodedmessages
mail.mime.applefilenames
mail.mime.base64.ignoreerrors
mail.mime.charset
mail.mime.contenttypehandler
mail.mime.decodefilename
mail.mime.decodeparameters
mail.mime.decodetext.strict
mail.mime.encodeeol.strict
mail.mime.encodefilename
mail.mime.encodeparameters
mail.mime.foldtext
mail.mime.ignoremultipartencoding
mail.mime.ignoreunknownencoding
mail.mime.ignorewhitespacelines
mail.mime.multipart.allowempty
mail.mime.multipart.ignoreexistingboundaryparameter
mail.mime.multipart.ignoremissingboundaryparameter
mail.mime.multipart.ignoremissingendboundary
mail.mime.parameters.strict
mail.mime.setcontenttypefilename
mail.mime.setdefaulttextcharset
mail.mime.uudecode.ignoreerrors
mail.mime.uudecode.ignoremissingbeginend
mail.mime.windowsfilenames
https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html
mail.smtp.user
mail.smtp.host
mail.smtp.port
mail.smtp.connectiontimeout
mail.smtp.timeout
mail.smtp.writetimeout
mail.smtp.from
mail.smtp.localhost
mail.smtp.localaddress
mail.smtp.localport
mail.smtp.ehlo
mail.smtp.auth
mail.smtp.auth.mechanisms
mail.smtp.auth.login.disable
mail.smtp.auth.plain.disable
mail.smtp.auth.digest-md5.disable
mail.smtp.auth.ntlm.disable
mail.smtp.auth.ntlm.domain
mail.smtp.auth.ntlm.flags
mail.smtp.auth.xoauth2.disable
mail.smtp.submitter
mail.smtp.dsn.notify
mail.smtp.dsn.ret
mail.smtp.allow8bitmime
mail.smtp.sendpartial
mail.smtp.sasl.enable
mail.smtp.sasl.mechanisms
mail.smtp.sasl.authorizationid
mail.smtp.sasl.realm
mail.smtp.sasl.usecanonicalhostname
mail.smtp.quitwait
mail.smtp.reportsuccess
mail.smtp.socketFactory
mail.smtp.socketFactory.class
mail.smtp.socketFactory.fallback
mail.smtp.socketFactory.port
mail.smtp.ssl.enable
mail.smtp.ssl.checkserveridentity
mail.smtp.ssl.trust
mail.smtp.ssl.socketFactory
mail.smtp.ssl.socketFactory.class
mail.smtp.ssl.socketFactory.port
mail.smtp.ssl.protocols
mail.smtp.ssl.ciphersuites
mail.smtp.starttls.enable
mail.smtp.starttls.required
mail.smtp.proxy.host
mail.smtp.proxy.port
mail.smtp.proxy.user
mail.smtp.proxy.password
mail.smtp.socks.host
mail.smtp.socks.port
mail.smtp.mailextension
mail.smtp.userset
mail.smtp.noop.strict

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/sendmail/sending-emails/index.html b/doc/sendmail/sending-emails/index.html
index 0c9c47f..5751bb6 100644
--- a/doc/sendmail/sending-emails/index.html
+++ b/doc/sendmail/sending-emails/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Sending emails
If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 
In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail module

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.engine the mailer implementation to use. The default value is null.
voidframework.sendmail.mailQueuePollTimeout the time to wait before giving up when retrieving a mail to be sent from the queue of mail waiting to be sent when the queue is empty. The default value is 2 seconds.
voidframework.sendmail.gracefulStopTimeout the time for the daemon to shut down properly before it was terminated. The default value is 15 seconds.

Examples
@BindClass
 public final class Service {
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index 4abbf3c..de41b48 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index 9e9fc87..e2633b1 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
 @ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
diff --git a/doc/vfs/using-vfs/index.html b/doc/vfs/using-vfs/index.html
index f1197a8..851d427 100644
--- a/doc/vfs/using-vfs/index.html
+++ b/doc/vfs/using-vfs/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 

Configuration
Different VirtualFileStorage implementations must be configured in voidframework.vfs namespace. The following configuration keys can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
 Note that each implementation can have extra configuration keys.

Example
voidframework {
diff --git a/doc/web/using-web/index.html b/doc/web/using-web/index.html
index 5dd9f12..cf4829c 100644
--- a/doc/web/using-web/index.html
+++ b/doc/web/using-web/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.10.0</version>
+    <version>1.11.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used.
Base
voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly. The default value is 15 seconds.
voidframework.web.errorHandler the implementation of the error handler to use in case of http error. The default value is dev.voidframework.web.http.errorhandler.DefaultErrorHandler.
voidframework.web.contextPath the default context path root. The default value is /.
voidframework.web.routes a list of routing definition classes (must implement the interface AppRoutesDefinition). The default value is [].
voidframework.web.globalFilters a list of routing global filter classes (must implement the interface Filter). The default value is [].
voidframework.web.baseAssetResourcesDirectory the default location of static files in the “resources” directory. The default value is static.
Server
voidframework.web.server.idleTimeout the time without any request to wait before the connection is closed. The default value is 30 seconds.
voidframework.web.server.extraWebServerConfiguration the implementation of the interface ExtraWebServerConfiguration to apply a custom configuration to the Undertow web server. The default value is null.
voidframework.web.server.ioThreads the number of I/O threads. If not specified (value = null or 0), Math.max(Runtime.getRuntime().availableProcessors(), 2) value will be used. The default value is null.
voidframework.web.server.workerThreads the number of Worker threads. If not specified (value = null or 0), ioThreadsNumber * 8 value will be used. The default value is null.
voidframework.web.server.maxBodySize the max body content size. The default value is 1 MiB.
voidframework.web.server.fileSizeThreshold the maximum size allowed in memory before the uploaded file was stored on the disk rather than in memory. The default value is 256 KiB.
voidframework.web.server.tempFileLocation the location where temporary files will be stored. The default value is null (default Java temporary folder).
HTTP
voidframework.web.server.http.listenHost the interface on which the server will listen for non-secure HTTP requests. The default value is 127.0.0.1.
voidframework.web.server.http.listenPort the port on which the server will listen for non-secure HTTP requests. The default value is 9000.
HTTPS
voidframework.web.server.https.listenHost the interface on which the server will listen for HTTPS requests. The default value is 127.0.0.1.
voidframework.web.server.https.listenPort the port on which the server will listen for HTTPS requests. The default value is 9001.
voidframework.web.server.https.ssl.protocols the protocols to use. The default value is ["TLSv1.2", "TLSv1.3"].
voidframework.web.server.https.ssl.ciphers the allowed ciphers. If list is empty, all ciphers will be allowed. The default value is [].
voidframework.web.server.https.ssl.keyStorePath the path where is located the key store. Could be a “resources” path, a URL or a simple path. The default value is null.
voidframework.web.server.https.ssl.keyStoreType the type of the key store. The default value is JKS.
voidframework.web.server.https.ssl.keyStorePassword the password to use to open the key store. The default value is null.
voidframework.web.server.https.ssl.keyAlias the alias of the key to use. If “null” the key will be choosen automatically. The default value is null.
voidframework.web.server.https.ssl.keyPassword the key password. The default value is ${voidframework.web.server.https.ssl.keyStorePassword}.
Language
voidframework.web.language.availableLanguages the available languages. The default value is ["en", "fr"].
voidframework.web.language.cookieName the name of the cookie containing the current language. The default value is VOID_LANG.
voidframework.web.language.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.language.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Flash messages
voidframework.web.flashMessages.cookieName the name of the cookie containing the current flash messages. The default value is VOID_FLASH.
voidframework.web.flashMessages.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.flashMessages.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Session
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.
CSRF
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.
Security headers
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/index.xml b/index.xml
index 925deed..0cb365a 100644
--- a/index.xml
+++ b/index.xml
@@ -3,13 +3,13 @@ AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframew
 AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -36,16 +36,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.jOOQ ORMhttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -53,9 +53,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -66,19 +66,19 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.0 2023-20-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "start" lifecycle failure Fixed H2 web console fail to start because password not encoded 1.10.0 2023-09-11 New REST Client authentication (API Key, Basic, Bearer) Improved New constant values: CharConstants.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.0 2023-20-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "start" lifecycle failure Fixed H2 web console fail to start because password not encoded 1.10.0 2023-09-11 New REST Client authentication (API Key, Basic, Bearer) Improved New constant values: CharConstants.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -91,11 +91,11 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
@@ -104,8 +104,8 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -117,19 +117,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.10.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file

From 3a2c974af47aacc65ee3c405dfdafd63d3ade5da Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 23 Nov 2023 19:53:04 +0000
Subject: [PATCH 62/75] Automated website build

---
 doc/relational-databases/persistence-hibernate/index.html | 3 ++-
 index.xml                                                 | 2 +-
 releasenotes/index.html                                   | 7 ++++---
 3 files changed, 7 insertions(+), 5 deletions(-)

diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index b5075cb..3f7dd80 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -8,7 +8,8 @@
     <artifactId>voidframework-persistence-hibernate</artifactId>
     <version>1.11.0</version>
 </dependency>
-

Working with transaction manually
final EntityManager entityManager = this.entityManagerProvider.get();
+

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.persistence.modelsJarUrlPattern Pattern to select Jar to scan to find models. For more information, see below the section “Speed-up PersistenceEntityFactory initialization time”. Default value is auto.
voidframework.datasource.default.dialect the Redis server host. Default value is null.
 
+The third segment named "default" represents the name of the data source. Any name can be used as long as it does not contain spaces or special characters.

Working with transaction manually
final EntityManager entityManager = this.entityManagerProvider.get();
 final EntityTransaction transaction = entityManager.getTransaction();
 
 transaction.begin();
diff --git a/index.xml b/index.xml
index 0cb365a..4b196e9 100644
--- a/index.xml
+++ b/index.xml
@@ -81,7 +81,7 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.0 2023-20-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "start" lifecycle failure Fixed H2 web console fail to start because password not encoded 1.10.0 2023-09-11 New REST Client authentication (API Key, Basic, Bearer) Improved New constant values: CharConstants.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.0 2023-20-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "start" lifecycle failure Fixed H2 web console fail to start because password not encoded 1.10.0 2023-09-11 New REST Client authentication (API Key, Basic, Bearer) Improved New constant values: CharConstants.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "start" lifecycle failure Fixed H2 web console fail to start because password not encoded 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "start" lifecycle failure Fixed H2 web console fail to start because password not encoded 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
diff --git a/releasenotes/index.html b/releasenotes/index.html
index b79425b..fa08bff 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,8 +1,9 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.11.0

-2023-20-19
New Add KryoUtils class
New Add new method ClassResolverUtils::isClassAvailable
New Add new Kryo serializers
New Add MockitoUtils class (spy lambda)
Improved AbstractCacheEngine now using KryoUtils
Improved Add TypedMap static "constructor" methods
Improved Redis ACL authentication (username/password)
Improved Upgrade dependencies
Fixed Application must shutdown on "start" lifecycle failure
Fixed H2 web console fail to start because password not encoded

1.10.0

+Release notes
1.11.1

+2023-11-23
Fixed Fix SQLDialect detection KO (jOOQ)
Fixed Fix can't override Hibernate dialect

1.11.0

+2023-10-19
New Add KryoUtils class
New Add new method ClassResolverUtils::isClassAvailable
New Add new Kryo serializers
New Add MockitoUtils class (spy lambda)
Improved AbstractCacheEngine now using KryoUtils
Improved Add TypedMap static "constructor" methods
Improved Redis ACL authentication (username/password)
Improved Upgrade dependencies
Fixed Application must shutdown on "start" lifecycle failure
Fixed H2 web console fail to start because password not encoded

1.10.0

 2023-09-11
New REST Client authentication (API Key, Basic, Bearer)
Improved New constant values: CharConstants.EXCLAMATION_MARK, CharConstants.PIPE, StringConstants.EXCLAMATION_MARK and StringConstants.PIPE
Improved Upgrade dependencies

1.9.0

 2023-07-13
New AspectJ
New REST client
New Bucket4J (rate-limiting)
New Add ConfigurationUtils class
Improved Upgrade dependencies
Improved New constant value: CharConstants.TAB and StringConstants.TAB

1.8.1

 2023-16-16
Improved Add exception AppLauncherException.ModuleConstructorNotFound

1.8.0


From c7ed4f7014b59802456e5b02349cafc0cd71f683 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 23 Nov 2023 19:56:29 +0000
Subject: [PATCH 63/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/redis-cache/index.html              |  2 +-
 doc/core/configuration/index.html             |  4 +-
 .../new-application/index.html                |  4 +-
 doc/index.xml                                 | 48 +++++++++----------
 .../using-i18n/index.html                     |  2 +-
 doc/nosql-databases/redis/index.html          |  4 +-
 .../datasource/index.html                     |  4 +-
 doc/relational-databases/h2/index.html        |  2 +-
 .../persistence-hibernate/index.html          |  2 +-
 .../persistence-jooq/index.html               |  2 +-
 doc/rest-client/retrofit2/index.html          |  2 +-
 doc/scheduler/scheduling-job-cron/index.html  |  2 +-
 .../mailer-apache-commons-email/index.html    |  2 +-
 doc/sendmail/sending-emails/index.html        |  2 +-
 doc/template/freemarker/index.html            |  2 +-
 doc/testing/junit-extension/index.html        |  2 +-
 doc/vfs/using-vfs/index.html                  |  2 +-
 doc/web/using-web/index.html                  |  2 +-
 index.xml                                     | 48 +++++++++----------
 20 files changed, 70 insertions(+), 70 deletions(-)

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index b9b7344..1815421 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 69c5dd2..da42e26 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index 9030f1d..e2eea4b 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -25,7 +25,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.11.0</version>
+  <version>1.11.1</version>
 </dependency>
 
voidframework {
     code {
@@ -60,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.11.0</version>
+  <version>1.11.1</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 3eeb5e4..8534617 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/index.xml b/doc/index.xml
index 0fe942d..adb5f8b 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -3,13 +3,13 @@ AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframew
 AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -36,16 +36,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.jOOQ ORMhttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -53,9 +53,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -66,19 +66,19 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -91,11 +91,11 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
@@ -104,8 +104,8 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -117,19 +117,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index a3cebd1..16a6138 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index b7faff8..930bbdc 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.username the authentication username (Redis 6 ACL). By default, this value is empty.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 

Example
@Service
 public final class ExampleService {
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index 2117ce3..fc3b5fa 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -5,12 +5,12 @@
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/relational-databases/h2/index.html b/doc/relational-databases/h2/index.html
index 0455899..e768d25 100644
--- a/doc/relational-databases/h2/index.html
+++ b/doc/relational-databases/h2/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

H2
H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-h2</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.h2.webPort the listen port of the H2 console. The default value is 9002.
voidframework.h2.webAdminPassword the password to access preferences and tools of H2 console. The default value is null (disabled).
voidframework.h2.webAllowOthers specifies if other computers are allowed to connect. The default value is false.

Open the web console
Once your application has started, you can access the H2 web console by going to http://127.0.0.1:9002.
 
 Note that H2 web console will be started only if the application is run in development mode (voidframework.core.runInDevMode = true).

© 2022-2023 Void Framework

diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index 3f7dd80..f4ce937 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -6,7 +6,7 @@
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.persistence.modelsJarUrlPattern Pattern to select Jar to scan to find models. For more information, see below the section “Speed-up PersistenceEntityFactory initialization time”. Default value is auto.
voidframework.datasource.default.dialect the Redis server host. Default value is null.
 
 The third segment named "default" represents the name of the data source. Any name can be used as long as it does not contain spaces or special characters.

Working with transaction manually
final EntityManager entityManager = this.entityManagerProvider.get();
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index 3157a45..41e2645 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

jOOQ ORM
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-jooq</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 

Generator
To work, jOOQ needs files generated during the compilation of the project. It is possible to generate the required classes in different ways (scan database, scan entity, …). For more information, please visit the official jOOQ website.
To enable code generation, add & customize the code below.
pom.xml
<build>
     <plugins>
diff --git a/doc/rest-client/retrofit2/index.html b/doc/rest-client/retrofit2/index.html
index c634aaa..714ce73 100644
--- a/doc/rest-client/retrofit2/index.html
+++ b/doc/rest-client/retrofit2/index.html
@@ -6,7 +6,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Retrofit 2
Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-restclient</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 

How it work
All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.

Configuration
The following configuration key can be used in the configuration file of your application
voidframework.restclient.maxIdleConnections the number of connection to keep idle. The default value is 5.
voidframework.restclient.keepAliveDuration the duration for which connections will be kept idle before being closed. The default value is 5 minutes.
voidframework.restclient.connectionTimeout the connect timeout duration. The default value is 15 seconds.
voidframework.restclient.readTimeout the read timeout duration. The default value is 35 seconds.
voidframework.restclient.authentication.type the authentication type to use (API_KEY, BASIC or BEARER). The default value is null (disabled).
voidframework.restclient.authentication.apiKeyName the API key variable name. This setting is only used if the authentication type is set to API_KEY. The default value is null.
voidframework.restclient.authentication.apiKeyValue the API key variable value. This setting is only used if the authentication type is set to API_KEY. The default value is null.
voidframework.restclient.authentication.apiKeyAddTo where to add the API key (COOKIE, HEADER, QUERY_PARAMETER). This setting is only used if the authentication type is set to API_KEY. The default value is HEADER.
voidframework.restclient.authentication.basicUsername the basic authentication username. This setting is only used if the authentication type is set to BASIC. The default value is null.
voidframework.restclient.authentication.basicPassword the basic authentication password. This setting is only used if the authentication type is set to BASIC. The default value is null.
voidframework.restclient.authentication.basicUseISO88591Encoding use ISO-8859-1 encoding rather than UTF-8. This setting is only used if the authentication type is set to BASIC. The default value is false.
voidframework.restclient.authentication.bearerPrefix the bearer prefix to use in the request header. This setting is only used if the authentication type is set to BEARER. The default value is Bearer.
voidframework.restclient.authentication.bearerToken the bearer token to use in the request header. This setting is only used if the authentication type is set to BEARER. The default value is null.
 
 You can override the global configuration for a specific service by using the following configuration key:
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index 1f6b8bc..3ac8bbf 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-scheduler</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron a CRON-like expression. The default value is empty (disabled).
cronZone the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
 public final class Ping {
diff --git a/doc/sendmail/mailer-apache-commons-email/index.html b/doc/sendmail/mailer-apache-commons-email/index.html
index 90f9554..e30c647 100644
--- a/doc/sendmail/mailer-apache-commons-email/index.html
+++ b/doc/sendmail/mailer-apache-commons-email/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Mailer : Apache Commons Email
This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail-commonsemail</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.commonsemail.username user name for authentication. The default value is null.
voidframework.sendmail.commonsemail.password password for authentication. The default value is null.
This module also includes many of the configuration keys of the Java Mail properties. To use it, simply prefix them with voidframework.sendmail.commonsemail.. Here is the list of possible properties:
https://javaee.github.io/javamail/docs/api/javax/mail/internet/package-summary.html
mail.mime.address.usecanonicalhostname
mail.mime.allowencodedmessages
mail.mime.applefilenames
mail.mime.base64.ignoreerrors
mail.mime.charset
mail.mime.contenttypehandler
mail.mime.decodefilename
mail.mime.decodeparameters
mail.mime.decodetext.strict
mail.mime.encodeeol.strict
mail.mime.encodefilename
mail.mime.encodeparameters
mail.mime.foldtext
mail.mime.ignoremultipartencoding
mail.mime.ignoreunknownencoding
mail.mime.ignorewhitespacelines
mail.mime.multipart.allowempty
mail.mime.multipart.ignoreexistingboundaryparameter
mail.mime.multipart.ignoremissingboundaryparameter
mail.mime.multipart.ignoremissingendboundary
mail.mime.parameters.strict
mail.mime.setcontenttypefilename
mail.mime.setdefaulttextcharset
mail.mime.uudecode.ignoreerrors
mail.mime.uudecode.ignoremissingbeginend
mail.mime.windowsfilenames
https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html
mail.smtp.user
mail.smtp.host
mail.smtp.port
mail.smtp.connectiontimeout
mail.smtp.timeout
mail.smtp.writetimeout
mail.smtp.from
mail.smtp.localhost
mail.smtp.localaddress
mail.smtp.localport
mail.smtp.ehlo
mail.smtp.auth
mail.smtp.auth.mechanisms
mail.smtp.auth.login.disable
mail.smtp.auth.plain.disable
mail.smtp.auth.digest-md5.disable
mail.smtp.auth.ntlm.disable
mail.smtp.auth.ntlm.domain
mail.smtp.auth.ntlm.flags
mail.smtp.auth.xoauth2.disable
mail.smtp.submitter
mail.smtp.dsn.notify
mail.smtp.dsn.ret
mail.smtp.allow8bitmime
mail.smtp.sendpartial
mail.smtp.sasl.enable
mail.smtp.sasl.mechanisms
mail.smtp.sasl.authorizationid
mail.smtp.sasl.realm
mail.smtp.sasl.usecanonicalhostname
mail.smtp.quitwait
mail.smtp.reportsuccess
mail.smtp.socketFactory
mail.smtp.socketFactory.class
mail.smtp.socketFactory.fallback
mail.smtp.socketFactory.port
mail.smtp.ssl.enable
mail.smtp.ssl.checkserveridentity
mail.smtp.ssl.trust
mail.smtp.ssl.socketFactory
mail.smtp.ssl.socketFactory.class
mail.smtp.ssl.socketFactory.port
mail.smtp.ssl.protocols
mail.smtp.ssl.ciphersuites
mail.smtp.starttls.enable
mail.smtp.starttls.required
mail.smtp.proxy.host
mail.smtp.proxy.port
mail.smtp.proxy.user
mail.smtp.proxy.password
mail.smtp.socks.host
mail.smtp.socks.port
mail.smtp.mailextension
mail.smtp.userset
mail.smtp.noop.strict

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/sendmail/sending-emails/index.html b/doc/sendmail/sending-emails/index.html
index 5751bb6..3fe93d6 100644
--- a/doc/sendmail/sending-emails/index.html
+++ b/doc/sendmail/sending-emails/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Sending emails
If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 
In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail module

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.engine the mailer implementation to use. The default value is null.
voidframework.sendmail.mailQueuePollTimeout the time to wait before giving up when retrieving a mail to be sent from the queue of mail waiting to be sent when the queue is empty. The default value is 2 seconds.
voidframework.sendmail.gracefulStopTimeout the time for the daemon to shut down properly before it was terminated. The default value is 15 seconds.

Examples
@BindClass
 public final class Service {
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index de41b48..d935eb1 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index e2633b1..36cc32d 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
 @ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
diff --git a/doc/vfs/using-vfs/index.html b/doc/vfs/using-vfs/index.html
index 851d427..c069bdc 100644
--- a/doc/vfs/using-vfs/index.html
+++ b/doc/vfs/using-vfs/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 

Configuration
Different VirtualFileStorage implementations must be configured in voidframework.vfs namespace. The following configuration keys can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
 Note that each implementation can have extra configuration keys.

Example
voidframework {
diff --git a/doc/web/using-web/index.html b/doc/web/using-web/index.html
index cf4829c..3b25feb 100644
--- a/doc/web/using-web/index.html
+++ b/doc/web/using-web/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.11.0</version>
+    <version>1.11.1</version>
 </dependency>
 

Configuration
The following configuration keys can be used.
Base
voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly. The default value is 15 seconds.
voidframework.web.errorHandler the implementation of the error handler to use in case of http error. The default value is dev.voidframework.web.http.errorhandler.DefaultErrorHandler.
voidframework.web.contextPath the default context path root. The default value is /.
voidframework.web.routes a list of routing definition classes (must implement the interface AppRoutesDefinition). The default value is [].
voidframework.web.globalFilters a list of routing global filter classes (must implement the interface Filter). The default value is [].
voidframework.web.baseAssetResourcesDirectory the default location of static files in the “resources” directory. The default value is static.
Server
voidframework.web.server.idleTimeout the time without any request to wait before the connection is closed. The default value is 30 seconds.
voidframework.web.server.extraWebServerConfiguration the implementation of the interface ExtraWebServerConfiguration to apply a custom configuration to the Undertow web server. The default value is null.
voidframework.web.server.ioThreads the number of I/O threads. If not specified (value = null or 0), Math.max(Runtime.getRuntime().availableProcessors(), 2) value will be used. The default value is null.
voidframework.web.server.workerThreads the number of Worker threads. If not specified (value = null or 0), ioThreadsNumber * 8 value will be used. The default value is null.
voidframework.web.server.maxBodySize the max body content size. The default value is 1 MiB.
voidframework.web.server.fileSizeThreshold the maximum size allowed in memory before the uploaded file was stored on the disk rather than in memory. The default value is 256 KiB.
voidframework.web.server.tempFileLocation the location where temporary files will be stored. The default value is null (default Java temporary folder).
HTTP
voidframework.web.server.http.listenHost the interface on which the server will listen for non-secure HTTP requests. The default value is 127.0.0.1.
voidframework.web.server.http.listenPort the port on which the server will listen for non-secure HTTP requests. The default value is 9000.
HTTPS
voidframework.web.server.https.listenHost the interface on which the server will listen for HTTPS requests. The default value is 127.0.0.1.
voidframework.web.server.https.listenPort the port on which the server will listen for HTTPS requests. The default value is 9001.
voidframework.web.server.https.ssl.protocols the protocols to use. The default value is ["TLSv1.2", "TLSv1.3"].
voidframework.web.server.https.ssl.ciphers the allowed ciphers. If list is empty, all ciphers will be allowed. The default value is [].
voidframework.web.server.https.ssl.keyStorePath the path where is located the key store. Could be a “resources” path, a URL or a simple path. The default value is null.
voidframework.web.server.https.ssl.keyStoreType the type of the key store. The default value is JKS.
voidframework.web.server.https.ssl.keyStorePassword the password to use to open the key store. The default value is null.
voidframework.web.server.https.ssl.keyAlias the alias of the key to use. If “null” the key will be choosen automatically. The default value is null.
voidframework.web.server.https.ssl.keyPassword the key password. The default value is ${voidframework.web.server.https.ssl.keyStorePassword}.
Language
voidframework.web.language.availableLanguages the available languages. The default value is ["en", "fr"].
voidframework.web.language.cookieName the name of the cookie containing the current language. The default value is VOID_LANG.
voidframework.web.language.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.language.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Flash messages
voidframework.web.flashMessages.cookieName the name of the cookie containing the current flash messages. The default value is VOID_FLASH.
voidframework.web.flashMessages.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.flashMessages.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Session
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.
CSRF
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.
Security headers
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/index.xml b/index.xml
index 4b196e9..b70ea36 100644
--- a/index.xml
+++ b/index.xml
@@ -3,13 +3,13 @@ AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframew
 AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -36,16 +36,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.jOOQ ORMhttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -53,9 +53,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -66,19 +66,19 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "start" lifecycle failure Fixed H2 web console fail to start because password not encoded 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "start" lifecycle failure Fixed H2 web console fail to start because password not encoded 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -91,11 +91,11 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
@@ -104,8 +104,8 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -117,19 +117,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file

From 7fe9e67194ddfa622c0829cc9d8a9786557b96d7 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Tue, 5 Dec 2023 19:36:13 +0000
Subject: [PATCH 64/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/redis-cache/index.html              |  2 +-
 doc/core/configuration/index.html             |  4 +-
 .../new-application/index.html                |  4 +-
 doc/index.xml                                 | 48 +++++++++---------
 .../using-i18n/index.html                     |  2 +-
 doc/nosql-databases/redis/index.html          |  4 +-
 .../datasource/index.html                     |  4 +-
 doc/relational-databases/h2/index.html        |  2 +-
 .../persistence-hibernate/index.html          |  2 +-
 .../persistence-jooq/index.html               |  2 +-
 doc/rest-client/retrofit2/index.html          |  2 +-
 doc/scheduler/scheduling-job-cron/index.html  |  2 +-
 .../mailer-apache-commons-email/index.html    |  2 +-
 doc/sendmail/sending-emails/index.html        |  2 +-
 doc/template/freemarker/index.html            |  2 +-
 doc/testing/junit-extension/index.html        |  2 +-
 doc/vfs/using-vfs/index.html                  |  2 +-
 doc/web/using-web/index.html                  |  2 +-
 index.xml                                     | 50 +++++++++----------
 releasenotes/index.html                       |  3 +-
 21 files changed, 73 insertions(+), 72 deletions(-)

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 1815421..4529b08 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index da42e26..193594d 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index e2eea4b..939a73c 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -25,7 +25,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.11.1</version>
+  <version>1.11.2</version>
 </dependency>
 
voidframework {
     code {
@@ -60,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.11.1</version>
+  <version>1.11.2</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 8534617..45ea363 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/index.xml b/doc/index.xml
index adb5f8b..9d4dfe3 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -3,13 +3,13 @@ AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframew
 AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -36,16 +36,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.jOOQ ORMhttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -53,9 +53,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -66,19 +66,19 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -91,11 +91,11 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
@@ -104,8 +104,8 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -117,19 +117,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index 16a6138..cbedf46 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index 930bbdc..7831153 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.username the authentication username (Redis 6 ACL). By default, this value is empty.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 

Example
@Service
 public final class ExampleService {
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index fc3b5fa..44bf766 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -5,12 +5,12 @@
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/relational-databases/h2/index.html b/doc/relational-databases/h2/index.html
index e768d25..8b3846b 100644
--- a/doc/relational-databases/h2/index.html
+++ b/doc/relational-databases/h2/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

H2
H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-h2</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.h2.webPort the listen port of the H2 console. The default value is 9002.
voidframework.h2.webAdminPassword the password to access preferences and tools of H2 console. The default value is null (disabled).
voidframework.h2.webAllowOthers specifies if other computers are allowed to connect. The default value is false.

Open the web console
Once your application has started, you can access the H2 web console by going to http://127.0.0.1:9002.
 
 Note that H2 web console will be started only if the application is run in development mode (voidframework.core.runInDevMode = true).

© 2022-2023 Void Framework

diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index f4ce937..ff6836f 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -6,7 +6,7 @@
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.persistence.modelsJarUrlPattern Pattern to select Jar to scan to find models. For more information, see below the section “Speed-up PersistenceEntityFactory initialization time”. Default value is auto.
voidframework.datasource.default.dialect the Redis server host. Default value is null.
 
 The third segment named "default" represents the name of the data source. Any name can be used as long as it does not contain spaces or special characters.

Working with transaction manually
final EntityManager entityManager = this.entityManagerProvider.get();
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index 41e2645..f426a48 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

jOOQ ORM
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-jooq</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 

Generator
To work, jOOQ needs files generated during the compilation of the project. It is possible to generate the required classes in different ways (scan database, scan entity, …). For more information, please visit the official jOOQ website.
To enable code generation, add & customize the code below.
pom.xml
<build>
     <plugins>
diff --git a/doc/rest-client/retrofit2/index.html b/doc/rest-client/retrofit2/index.html
index 714ce73..416cb02 100644
--- a/doc/rest-client/retrofit2/index.html
+++ b/doc/rest-client/retrofit2/index.html
@@ -6,7 +6,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Retrofit 2
Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-restclient</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 

How it work
All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.

Configuration
The following configuration key can be used in the configuration file of your application
voidframework.restclient.maxIdleConnections the number of connection to keep idle. The default value is 5.
voidframework.restclient.keepAliveDuration the duration for which connections will be kept idle before being closed. The default value is 5 minutes.
voidframework.restclient.connectionTimeout the connect timeout duration. The default value is 15 seconds.
voidframework.restclient.readTimeout the read timeout duration. The default value is 35 seconds.
voidframework.restclient.authentication.type the authentication type to use (API_KEY, BASIC or BEARER). The default value is null (disabled).
voidframework.restclient.authentication.apiKeyName the API key variable name. This setting is only used if the authentication type is set to API_KEY. The default value is null.
voidframework.restclient.authentication.apiKeyValue the API key variable value. This setting is only used if the authentication type is set to API_KEY. The default value is null.
voidframework.restclient.authentication.apiKeyAddTo where to add the API key (COOKIE, HEADER, QUERY_PARAMETER). This setting is only used if the authentication type is set to API_KEY. The default value is HEADER.
voidframework.restclient.authentication.basicUsername the basic authentication username. This setting is only used if the authentication type is set to BASIC. The default value is null.
voidframework.restclient.authentication.basicPassword the basic authentication password. This setting is only used if the authentication type is set to BASIC. The default value is null.
voidframework.restclient.authentication.basicUseISO88591Encoding use ISO-8859-1 encoding rather than UTF-8. This setting is only used if the authentication type is set to BASIC. The default value is false.
voidframework.restclient.authentication.bearerPrefix the bearer prefix to use in the request header. This setting is only used if the authentication type is set to BEARER. The default value is Bearer.
voidframework.restclient.authentication.bearerToken the bearer token to use in the request header. This setting is only used if the authentication type is set to BEARER. The default value is null.
 
 You can override the global configuration for a specific service by using the following configuration key:
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index 3ac8bbf..33c75cb 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-scheduler</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron a CRON-like expression. The default value is empty (disabled).
cronZone the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
 public final class Ping {
diff --git a/doc/sendmail/mailer-apache-commons-email/index.html b/doc/sendmail/mailer-apache-commons-email/index.html
index e30c647..cd645fa 100644
--- a/doc/sendmail/mailer-apache-commons-email/index.html
+++ b/doc/sendmail/mailer-apache-commons-email/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Mailer : Apache Commons Email
This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail-commonsemail</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.commonsemail.username user name for authentication. The default value is null.
voidframework.sendmail.commonsemail.password password for authentication. The default value is null.
This module also includes many of the configuration keys of the Java Mail properties. To use it, simply prefix them with voidframework.sendmail.commonsemail.. Here is the list of possible properties:
https://javaee.github.io/javamail/docs/api/javax/mail/internet/package-summary.html
mail.mime.address.usecanonicalhostname
mail.mime.allowencodedmessages
mail.mime.applefilenames
mail.mime.base64.ignoreerrors
mail.mime.charset
mail.mime.contenttypehandler
mail.mime.decodefilename
mail.mime.decodeparameters
mail.mime.decodetext.strict
mail.mime.encodeeol.strict
mail.mime.encodefilename
mail.mime.encodeparameters
mail.mime.foldtext
mail.mime.ignoremultipartencoding
mail.mime.ignoreunknownencoding
mail.mime.ignorewhitespacelines
mail.mime.multipart.allowempty
mail.mime.multipart.ignoreexistingboundaryparameter
mail.mime.multipart.ignoremissingboundaryparameter
mail.mime.multipart.ignoremissingendboundary
mail.mime.parameters.strict
mail.mime.setcontenttypefilename
mail.mime.setdefaulttextcharset
mail.mime.uudecode.ignoreerrors
mail.mime.uudecode.ignoremissingbeginend
mail.mime.windowsfilenames
https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html
mail.smtp.user
mail.smtp.host
mail.smtp.port
mail.smtp.connectiontimeout
mail.smtp.timeout
mail.smtp.writetimeout
mail.smtp.from
mail.smtp.localhost
mail.smtp.localaddress
mail.smtp.localport
mail.smtp.ehlo
mail.smtp.auth
mail.smtp.auth.mechanisms
mail.smtp.auth.login.disable
mail.smtp.auth.plain.disable
mail.smtp.auth.digest-md5.disable
mail.smtp.auth.ntlm.disable
mail.smtp.auth.ntlm.domain
mail.smtp.auth.ntlm.flags
mail.smtp.auth.xoauth2.disable
mail.smtp.submitter
mail.smtp.dsn.notify
mail.smtp.dsn.ret
mail.smtp.allow8bitmime
mail.smtp.sendpartial
mail.smtp.sasl.enable
mail.smtp.sasl.mechanisms
mail.smtp.sasl.authorizationid
mail.smtp.sasl.realm
mail.smtp.sasl.usecanonicalhostname
mail.smtp.quitwait
mail.smtp.reportsuccess
mail.smtp.socketFactory
mail.smtp.socketFactory.class
mail.smtp.socketFactory.fallback
mail.smtp.socketFactory.port
mail.smtp.ssl.enable
mail.smtp.ssl.checkserveridentity
mail.smtp.ssl.trust
mail.smtp.ssl.socketFactory
mail.smtp.ssl.socketFactory.class
mail.smtp.ssl.socketFactory.port
mail.smtp.ssl.protocols
mail.smtp.ssl.ciphersuites
mail.smtp.starttls.enable
mail.smtp.starttls.required
mail.smtp.proxy.host
mail.smtp.proxy.port
mail.smtp.proxy.user
mail.smtp.proxy.password
mail.smtp.socks.host
mail.smtp.socks.port
mail.smtp.mailextension
mail.smtp.userset
mail.smtp.noop.strict

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/sendmail/sending-emails/index.html b/doc/sendmail/sending-emails/index.html
index 3fe93d6..2202624 100644
--- a/doc/sendmail/sending-emails/index.html
+++ b/doc/sendmail/sending-emails/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Sending emails
If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 
In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail module

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.engine the mailer implementation to use. The default value is null.
voidframework.sendmail.mailQueuePollTimeout the time to wait before giving up when retrieving a mail to be sent from the queue of mail waiting to be sent when the queue is empty. The default value is 2 seconds.
voidframework.sendmail.gracefulStopTimeout the time for the daemon to shut down properly before it was terminated. The default value is 15 seconds.

Examples
@BindClass
 public final class Service {
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index d935eb1..d27bba2 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index 36cc32d..042555c 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
 @ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
diff --git a/doc/vfs/using-vfs/index.html b/doc/vfs/using-vfs/index.html
index c069bdc..4d8f274 100644
--- a/doc/vfs/using-vfs/index.html
+++ b/doc/vfs/using-vfs/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 

Configuration
Different VirtualFileStorage implementations must be configured in voidframework.vfs namespace. The following configuration keys can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
 Note that each implementation can have extra configuration keys.

Example
voidframework {
diff --git a/doc/web/using-web/index.html b/doc/web/using-web/index.html
index 3b25feb..a621c91 100644
--- a/doc/web/using-web/index.html
+++ b/doc/web/using-web/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.11.1</version>
+    <version>1.11.2</version>
 </dependency>
 

Configuration
The following configuration keys can be used.
Base
voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly. The default value is 15 seconds.
voidframework.web.errorHandler the implementation of the error handler to use in case of http error. The default value is dev.voidframework.web.http.errorhandler.DefaultErrorHandler.
voidframework.web.contextPath the default context path root. The default value is /.
voidframework.web.routes a list of routing definition classes (must implement the interface AppRoutesDefinition). The default value is [].
voidframework.web.globalFilters a list of routing global filter classes (must implement the interface Filter). The default value is [].
voidframework.web.baseAssetResourcesDirectory the default location of static files in the “resources” directory. The default value is static.
Server
voidframework.web.server.idleTimeout the time without any request to wait before the connection is closed. The default value is 30 seconds.
voidframework.web.server.extraWebServerConfiguration the implementation of the interface ExtraWebServerConfiguration to apply a custom configuration to the Undertow web server. The default value is null.
voidframework.web.server.ioThreads the number of I/O threads. If not specified (value = null or 0), Math.max(Runtime.getRuntime().availableProcessors(), 2) value will be used. The default value is null.
voidframework.web.server.workerThreads the number of Worker threads. If not specified (value = null or 0), ioThreadsNumber * 8 value will be used. The default value is null.
voidframework.web.server.maxBodySize the max body content size. The default value is 1 MiB.
voidframework.web.server.fileSizeThreshold the maximum size allowed in memory before the uploaded file was stored on the disk rather than in memory. The default value is 256 KiB.
voidframework.web.server.tempFileLocation the location where temporary files will be stored. The default value is null (default Java temporary folder).
HTTP
voidframework.web.server.http.listenHost the interface on which the server will listen for non-secure HTTP requests. The default value is 127.0.0.1.
voidframework.web.server.http.listenPort the port on which the server will listen for non-secure HTTP requests. The default value is 9000.
HTTPS
voidframework.web.server.https.listenHost the interface on which the server will listen for HTTPS requests. The default value is 127.0.0.1.
voidframework.web.server.https.listenPort the port on which the server will listen for HTTPS requests. The default value is 9001.
voidframework.web.server.https.ssl.protocols the protocols to use. The default value is ["TLSv1.2", "TLSv1.3"].
voidframework.web.server.https.ssl.ciphers the allowed ciphers. If list is empty, all ciphers will be allowed. The default value is [].
voidframework.web.server.https.ssl.keyStorePath the path where is located the key store. Could be a “resources” path, a URL or a simple path. The default value is null.
voidframework.web.server.https.ssl.keyStoreType the type of the key store. The default value is JKS.
voidframework.web.server.https.ssl.keyStorePassword the password to use to open the key store. The default value is null.
voidframework.web.server.https.ssl.keyAlias the alias of the key to use. If “null” the key will be choosen automatically. The default value is null.
voidframework.web.server.https.ssl.keyPassword the key password. The default value is ${voidframework.web.server.https.ssl.keyStorePassword}.
Language
voidframework.web.language.availableLanguages the available languages. The default value is ["en", "fr"].
voidframework.web.language.cookieName the name of the cookie containing the current language. The default value is VOID_LANG.
voidframework.web.language.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.language.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Flash messages
voidframework.web.flashMessages.cookieName the name of the cookie containing the current flash messages. The default value is VOID_FLASH.
voidframework.web.flashMessages.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.flashMessages.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Session
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.
CSRF
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.
Security headers
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/index.xml b/index.xml
index b70ea36..70ed485 100644
--- a/index.xml
+++ b/index.xml
@@ -3,13 +3,13 @@ AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframew
 AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -36,16 +36,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.jOOQ ORMhttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -53,9 +53,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -66,22 +66,22 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "start" lifecycle failure Fixed H2 web console fail to start because password not encoded 1.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "start" lifecycle failure Fixed H2 web console fail to start because password not encoded 1.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.1 2023-11-23 Security Upgrade logback-classic version to 1.4.14 ( CVE-2023-6378) 1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.1 2023-11-23 Security Upgrade logback-classic version to 1.4.14 ( CVE-2023-6378) 1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
@@ -91,11 +91,11 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
@@ -104,8 +104,8 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -117,19 +117,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.1&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index fa08bff..43a7cfb 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,7 +1,8 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
 Release notes
1.11.1

+2023-11-23
Security Upgrade logback-classic version to 1.4.14 ( CVE-2023-6378)

1.11.1

 2023-11-23
Fixed Fix SQLDialect detection KO (jOOQ)
Fixed Fix can't override Hibernate dialect

1.11.0

 2023-10-19
New Add KryoUtils class
New Add new method ClassResolverUtils::isClassAvailable
New Add new Kryo serializers
New Add MockitoUtils class (spy lambda)
Improved AbstractCacheEngine now using KryoUtils
Improved Add TypedMap static "constructor" methods
Improved Redis ACL authentication (username/password)
Improved Upgrade dependencies
Fixed Application must shutdown on "start" lifecycle failure
Fixed H2 web console fail to start because password not encoded

1.10.0

 2023-09-11
New REST Client authentication (API Key, Basic, Bearer)
Improved New constant values: CharConstants.EXCLAMATION_MARK, CharConstants.PIPE, StringConstants.EXCLAMATION_MARK and StringConstants.PIPE
Improved Upgrade dependencies

1.9.0


From bfae8e0059204183ee0a0393d0f31cc03994b92d Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Tue, 5 Dec 2023 19:36:59 +0000
Subject: [PATCH 65/75] Automated website build

---
 index.xml               | 2 +-
 releasenotes/index.html | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.xml b/index.xml
index 70ed485..156ce81 100644
--- a/index.xml
+++ b/index.xml
@@ -81,7 +81,7 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.1 2023-11-23 Security Upgrade logback-classic version to 1.4.14 ( CVE-2023-6378) 1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.1 2023-11-23 Security Upgrade logback-classic version to 1.4.14 ( CVE-2023-6378) 1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.1 2023-12-05 Security Upgrade logback-classic version to 1.4.14 ( CVE-2023-6378) 1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.1 2023-12-05 Security Upgrade logback-classic version to 1.4.14 ( CVE-2023-6378) 1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 43a7cfb..005af1b 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,8 +1,8 @@
-Void Framework – Release notes

+Void Framework – Release notes
 Void Framework
Documentation
    
 Release notes
1.11.1

-2023-11-23
Security Upgrade logback-classic version to 1.4.14 ( CVE-2023-6378)

1.11.1

+2023-12-05
Security Upgrade logback-classic version to 1.4.14 ( CVE-2023-6378)

1.11.1

 2023-11-23
Fixed Fix SQLDialect detection KO (jOOQ)
Fixed Fix can't override Hibernate dialect

1.11.0

 2023-10-19
New Add KryoUtils class
New Add new method ClassResolverUtils::isClassAvailable
New Add new Kryo serializers
New Add MockitoUtils class (spy lambda)
Improved AbstractCacheEngine now using KryoUtils
Improved Add TypedMap static "constructor" methods
Improved Redis ACL authentication (username/password)
Improved Upgrade dependencies
Fixed Application must shutdown on "start" lifecycle failure
Fixed H2 web console fail to start because password not encoded

1.10.0

 2023-09-11
New REST Client authentication (API Key, Basic, Bearer)
Improved New constant values: CharConstants.EXCLAMATION_MARK, CharConstants.PIPE, StringConstants.EXCLAMATION_MARK and StringConstants.PIPE
Improved Upgrade dependencies

1.9.0


From 53654c1c69fc59865877c53d7486744f74175d9d Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Tue, 2 Jan 2024 07:36:56 +0000
Subject: [PATCH 66/75] Automated website build

---
 doc/cache/in-memory-cache/index.html          |  2 +-
 doc/cache/redis-cache/index.html              |  4 +-
 doc/core/configuration/index.html             |  4 +-
 .../new-application/index.html                |  4 +-
 .../upgrading-from-old-version/index.html     |  2 +-
 doc/index.xml                                 | 48 +++++++++---------
 .../using-i18n/index.html                     |  2 +-
 doc/nosql-databases/redis/index.html          |  4 +-
 .../datasource/index.html                     |  4 +-
 doc/relational-databases/h2/index.html        |  2 +-
 .../persistence-hibernate/index.html          |  2 +-
 .../persistence-jooq/index.html               |  2 +-
 doc/rest-client/retrofit2/index.html          |  2 +-
 doc/scheduler/scheduling-job-cron/index.html  |  2 +-
 .../mailer-apache-commons-email/index.html    |  2 +-
 doc/sendmail/sending-emails/index.html        |  2 +-
 doc/template/freemarker/index.html            |  2 +-
 doc/testing/junit-extension/index.html        |  2 +-
 doc/vfs/using-vfs/index.html                  |  2 +-
 doc/web/using-web/index.html                  |  2 +-
 index.xml                                     | 50 +++++++++----------
 releasenotes/index.html                       | 11 ++--
 22 files changed, 79 insertions(+), 78 deletions(-)

diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index 4529b08..e465391 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : In-memory
This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 193594d..0c238f5 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -1,11 +1,11 @@
 Void Framework – Cache engine : Redis
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.12">Void Framework – Cache engine : Redis
 Void Framework
Documentation
    
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache engine : Redis
This implementation requires the voidframework-redis module to be properly configured.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-cache-redis</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index 939a73c..c014b86 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -25,7 +25,7 @@
 If more than one provider is declared. They will be used in order of declaration and each will override the configuration retrieved by the previous provider.
Provider “etcd”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-etcd</artifactId>
-  <version>1.11.2</version>
+  <version>1.12.0</version>
 </dependency>
 
voidframework {
     code {
@@ -60,7 +60,7 @@
 
Provider “http”
<dependency>
   <groupId>dev.voidframework</groupId>
   <artifactId>voidframework-remoteconf-http</artifactId>
-  <version>1.11.2</version>
+  <version>1.12.0</version>
 </dependency>
 
voidframework {
     code {
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 45ea363..3f7b30f 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Creating a new application
To create a new application with Void Framework, simply create a new Maven project and then add the necessary dependencies.

Maven
The very first dependency to include in your pom.xml is voidframework-core, without it you will not be able to start the application. The dependencies to be added will depend on the features you wish to use on your application, so do not hesitate to consult the different chapters of the documentation.
In this example, we will also use the web feature, so the voidframework-web dependency will also be added.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-core</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 <dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 

Configuration
Void Framework use a configuration file format is HOCON (Human-Optimized Config Object Notation). This format supports types such as integer, long, boolean, double, string, list and object. It is also possible to include other files by using include. There are two ways to write comments: using // or #. Comments can be written in-line at the end of the line or in separate lines. For more information on Typesafe Config, visit the Github project’s page.
The first thing to do is to indicate the paths to scan to find the elements of your application that can be loaded. The default location for the configuration file is resources/application.conf. And to define a key to sign the Session (even if you plan to not use session).
voidframework {
     core {
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index 983fe3e..8342a6d 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.0.0 Initial relea">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.0.0
Initial release

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

1.6.0
Configuration keys voidframework.web.server.listenHost and voidframework.web.server.listenPort have been renamed to voidframework.web.server.http.listenHost and voidframework.web.server.http.listenPort

1.8.0
Guice 7.0 only supports the jakarta.inject, jakarta.servlet and jakarta.persistence namespaces. Read more at https://github.com/google/guice/wiki/Guice700

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.0.0
Initial release

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

1.6.0
Configuration keys voidframework.web.server.listenHost and voidframework.web.server.listenPort have been renamed to voidframework.web.server.http.listenHost and voidframework.web.server.http.listenPort

1.8.0
Guice 7.0 only supports the jakarta.inject, jakarta.servlet and jakarta.persistence namespaces. Read more at https://github.com/google/guice/wiki/Guice700

1.12.0
Constants PARENTHESIS_OPEN and PARENTHESIS_CLOSE are no longer inverted. If you use these two constants, take care to adapt their use

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.xml b/doc/index.xml
index 9d4dfe3..e1bc82d 100644
--- a/doc/index.xml
+++ b/doc/index.xml
@@ -3,13 +3,13 @@ AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframew
 AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -36,16 +36,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.jOOQ ORMhttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -53,9 +53,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -66,19 +66,19 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
@@ -91,11 +91,11 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
@@ -104,8 +104,8 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -117,19 +117,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index cbedf46..fadfc8e 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using internationalization
Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-i18n</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 

Defining messages
Translations should be placed in a file named messages_<LANG>.properties (ie: messages_en.properties) in the resources directory.
resources/messages_fr.properties
lang.fr=Français
 
resources/messages_en.properties
lang.fr=French
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index 7831153..2baedcc 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -5,12 +5,12 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Redis
Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.redis.host the Redis server host. Default value is 127.0.0.1.
voidframework.redis.port the port on which the server is listening. Default value is 6379.
voidframework.redis.username the authentication username (Redis 6 ACL). By default, this value is empty.
voidframework.redis.password the authentication password. By default, this value is empty.
voidframework.redis.defaultDatabase the database to use by default. Default value is 1.
voidframework.redis.connPool.connectionTimeout the connection timeout in milliseconds. Default value is 2000 milliseconds.
voidframework.redis.connPool.maximumWait the maximum time to obtain a connection from the pool. Default value is 2000 milliseconds.
voidframework.redis.connPool.minimumIdle the minimum number of idle connections. Default value is 2.
voidframework.redis.connPool.maximumIdle the maximum number of idle connections. Default value is 8.
voidframework.redis.connPool.maximumPoolSize the maximum number of connections. Default value is 16.

Healthcheck
If you wan to monitoring Redis health, you can enable the healthcheck module by adding the following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-redis-healthcheck</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 

Example
@Service
 public final class ExampleService {
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index 44bf766..043013f 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -5,12 +5,12 @@
 Note that you can only use one implementation at a time.
C3P0
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-c3p0</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 
HikariCP
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-datasource-hikaricp</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
required
 voidframework.datasource.default.driver the driver to be used to communicate with the database.
required
diff --git a/doc/relational-databases/h2/index.html b/doc/relational-databases/h2/index.html
index 8b3846b..9d2f98c 100644
--- a/doc/relational-databases/h2/index.html
+++ b/doc/relational-databases/h2/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

H2
H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-h2</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.h2.webPort the listen port of the H2 console. The default value is 9002.
voidframework.h2.webAdminPassword the password to access preferences and tools of H2 console. The default value is null (disabled).
voidframework.h2.webAllowOthers specifies if other computers are allowed to connect. The default value is false.

Open the web console
Once your application has started, you can access the H2 web console by going to http://127.0.0.1:9002.
 
 Note that H2 web console will be started only if the application is run in development mode (voidframework.core.runInDevMode = true).

© 2022-2023 Void Framework

diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index ff6836f..667d046 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -6,7 +6,7 @@
 Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.persistence package.

Installation
This module adds support for the Transactional annotation as well as setting up an EntityManager provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-hibernate module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-hibernate</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.persistence.modelsJarUrlPattern Pattern to select Jar to scan to find models. For more information, see below the section “Speed-up PersistenceEntityFactory initialization time”. Default value is auto.
voidframework.datasource.default.dialect the Redis server host. Default value is null.
 
 The third segment named "default" represents the name of the data source. Any name can be used as long as it does not contain spaces or special characters.

Working with transaction manually
final EntityManager entityManager = this.entityManagerProvider.get();
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index f426a48..886be23 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

jOOQ ORM
jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.

Installation
This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-persistence-jooq</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 

Generator
To work, jOOQ needs files generated during the compilation of the project. It is possible to generate the required classes in different ways (scan database, scan entity, …). For more information, please visit the official jOOQ website.
To enable code generation, add & customize the code below.
pom.xml
<build>
     <plugins>
diff --git a/doc/rest-client/retrofit2/index.html b/doc/rest-client/retrofit2/index.html
index 416cb02..075f788 100644
--- a/doc/rest-client/retrofit2/index.html
+++ b/doc/rest-client/retrofit2/index.html
@@ -6,7 +6,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Retrofit 2
Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-restclient</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 

How it work
All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.

Configuration
The following configuration key can be used in the configuration file of your application
voidframework.restclient.maxIdleConnections the number of connection to keep idle. The default value is 5.
voidframework.restclient.keepAliveDuration the duration for which connections will be kept idle before being closed. The default value is 5 minutes.
voidframework.restclient.connectionTimeout the connect timeout duration. The default value is 15 seconds.
voidframework.restclient.readTimeout the read timeout duration. The default value is 35 seconds.
voidframework.restclient.authentication.type the authentication type to use (API_KEY, BASIC or BEARER). The default value is null (disabled).
voidframework.restclient.authentication.apiKeyName the API key variable name. This setting is only used if the authentication type is set to API_KEY. The default value is null.
voidframework.restclient.authentication.apiKeyValue the API key variable value. This setting is only used if the authentication type is set to API_KEY. The default value is null.
voidframework.restclient.authentication.apiKeyAddTo where to add the API key (COOKIE, HEADER, QUERY_PARAMETER). This setting is only used if the authentication type is set to API_KEY. The default value is HEADER.
voidframework.restclient.authentication.basicUsername the basic authentication username. This setting is only used if the authentication type is set to BASIC. The default value is null.
voidframework.restclient.authentication.basicPassword the basic authentication password. This setting is only used if the authentication type is set to BASIC. The default value is null.
voidframework.restclient.authentication.basicUseISO88591Encoding use ISO-8859-1 encoding rather than UTF-8. This setting is only used if the authentication type is set to BASIC. The default value is false.
voidframework.restclient.authentication.bearerPrefix the bearer prefix to use in the request header. This setting is only used if the authentication type is set to BEARER. The default value is Bearer.
voidframework.restclient.authentication.bearerToken the bearer token to use in the request header. This setting is only used if the authentication type is set to BEARER. The default value is null.
 
 You can override the global configuration for a specific service by using the following configuration key:
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index 33c75cb..6819ad8 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Scheduling a local job
If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-scheduler</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 

Define a Job
To define a job, simply use the @Scheduled annotation on one or more methods of a bindable class. As a reminder, a class is said to be bindable when it is annotated with, at least, the @Bindable annotation.
The @Scheduled annotation accepts the following parameters:
fixedDelay the time in milliseconds between the end of the last execution and the next execution. The default value is 0 (disabled).
fixedRate the time in milliseconds between each execution. The default value is 0 (disabled).
initialDelay the time in milliseconds to wait before the first execution of “fixedDelay” or “fixedRate”. The default value is 0 (disabled).
cron a CRON-like expression. The default value is empty (disabled).
cronZone the time zone for which the CRON expression will be resolved. The default value is UTC.

CRON expression
The format of the CRON expression have to be composed of : second, minute, hour, day of month, month and day of week.
Unit Value Step Value Details
Second 0 – 59 1 – 60 
Minute 0 – 59 1 – 60 
Hour 0 – 23 1 – 24 
Day of Month 1 – 31 1 – 32 
Month 1 – 12 1 – 13 1: January, 2: February, …, 12: December
Day of Week 0 – 6 1 – 7 0: Sunday, 1: Monday, …, 6: Saturday
To improve readability, you can also replace Month and Day of Week with an abbreviation of the desired value.
Month: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Day of Week: SUN, MON, TUE, WEB, THU, FRI, SAT

Examples
@BindClass
 public final class Ping {
diff --git a/doc/sendmail/mailer-apache-commons-email/index.html b/doc/sendmail/mailer-apache-commons-email/index.html
index cd645fa..f935364 100644
--- a/doc/sendmail/mailer-apache-commons-email/index.html
+++ b/doc/sendmail/mailer-apache-commons-email/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Mailer : Apache Commons Email
This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail-commonsemail</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.commonsemail.username user name for authentication. The default value is null.
voidframework.sendmail.commonsemail.password password for authentication. The default value is null.
This module also includes many of the configuration keys of the Java Mail properties. To use it, simply prefix them with voidframework.sendmail.commonsemail.. Here is the list of possible properties:
https://javaee.github.io/javamail/docs/api/javax/mail/internet/package-summary.html
mail.mime.address.usecanonicalhostname
mail.mime.allowencodedmessages
mail.mime.applefilenames
mail.mime.base64.ignoreerrors
mail.mime.charset
mail.mime.contenttypehandler
mail.mime.decodefilename
mail.mime.decodeparameters
mail.mime.decodetext.strict
mail.mime.encodeeol.strict
mail.mime.encodefilename
mail.mime.encodeparameters
mail.mime.foldtext
mail.mime.ignoremultipartencoding
mail.mime.ignoreunknownencoding
mail.mime.ignorewhitespacelines
mail.mime.multipart.allowempty
mail.mime.multipart.ignoreexistingboundaryparameter
mail.mime.multipart.ignoremissingboundaryparameter
mail.mime.multipart.ignoremissingendboundary
mail.mime.parameters.strict
mail.mime.setcontenttypefilename
mail.mime.setdefaulttextcharset
mail.mime.uudecode.ignoreerrors
mail.mime.uudecode.ignoremissingbeginend
mail.mime.windowsfilenames
https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html
mail.smtp.user
mail.smtp.host
mail.smtp.port
mail.smtp.connectiontimeout
mail.smtp.timeout
mail.smtp.writetimeout
mail.smtp.from
mail.smtp.localhost
mail.smtp.localaddress
mail.smtp.localport
mail.smtp.ehlo
mail.smtp.auth
mail.smtp.auth.mechanisms
mail.smtp.auth.login.disable
mail.smtp.auth.plain.disable
mail.smtp.auth.digest-md5.disable
mail.smtp.auth.ntlm.disable
mail.smtp.auth.ntlm.domain
mail.smtp.auth.ntlm.flags
mail.smtp.auth.xoauth2.disable
mail.smtp.submitter
mail.smtp.dsn.notify
mail.smtp.dsn.ret
mail.smtp.allow8bitmime
mail.smtp.sendpartial
mail.smtp.sasl.enable
mail.smtp.sasl.mechanisms
mail.smtp.sasl.authorizationid
mail.smtp.sasl.realm
mail.smtp.sasl.usecanonicalhostname
mail.smtp.quitwait
mail.smtp.reportsuccess
mail.smtp.socketFactory
mail.smtp.socketFactory.class
mail.smtp.socketFactory.fallback
mail.smtp.socketFactory.port
mail.smtp.ssl.enable
mail.smtp.ssl.checkserveridentity
mail.smtp.ssl.trust
mail.smtp.ssl.socketFactory
mail.smtp.ssl.socketFactory.class
mail.smtp.ssl.socketFactory.port
mail.smtp.ssl.protocols
mail.smtp.ssl.ciphersuites
mail.smtp.starttls.enable
mail.smtp.starttls.required
mail.smtp.proxy.host
mail.smtp.proxy.port
mail.smtp.proxy.user
mail.smtp.proxy.password
mail.smtp.socks.host
mail.smtp.socks.port
mail.smtp.mailextension
mail.smtp.userset
mail.smtp.noop.strict

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/doc/sendmail/sending-emails/index.html b/doc/sendmail/sending-emails/index.html
index 2202624..e72a59a 100644
--- a/doc/sendmail/sending-emails/index.html
+++ b/doc/sendmail/sending-emails/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Sending emails
If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-sendmail</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 
In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail module

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.engine the mailer implementation to use. The default value is null.
voidframework.sendmail.mailQueuePollTimeout the time to wait before giving up when retrieving a mail to be sent from the queue of mail waiting to be sent when the queue is empty. The default value is 2 seconds.
voidframework.sendmail.gracefulStopTimeout the time for the daemon to shut down properly before it was terminated. The default value is 15 seconds.

Examples
@BindClass
 public final class Service {
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index d27bba2..6630504 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

FreeMarker
To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.

Installation
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-template-freemarker</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index 042555c..55de129 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

JUnit's extension
It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-test</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 

JUnit’s extension
The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations. It will also reset the mock between each test. To use it, add the @ExtendWith annotation with the value VoidFrameworkJUnitExtension.class.

Use extra Guice modules
In some situations, you may need to load additional modules for your application to work properly during the unit testing phase. For this, you can use the @ExtraGuiceModule annotation.

Example
@ExtendWith(VoidFrameworkJUnitExtension.class)
 @ExtraGuiceModule({ExtraGuiceModule.class, AnotherExtraGuiceModule.class})
diff --git a/doc/vfs/using-vfs/index.html b/doc/vfs/using-vfs/index.html
index 4d8f274..ea38fed 100644
--- a/doc/vfs/using-vfs/index.html
+++ b/doc/vfs/using-vfs/index.html
@@ -4,7 +4,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Virtual File Storage
When you need to store or retrieve files, you don’t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-vfs</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 

Configuration
Different VirtualFileStorage implementations must be configured in voidframework.vfs namespace. The following configuration keys can be used.
voidframework.vfs.<name>.className the class name of the VFS implementation to use.
voidframework.vfs.<name>.default indicate if the implementation is used by default and can be Guice injected without @Named annotation.
 
 Note that each implementation can have extra configuration keys.

Example
voidframework {
diff --git a/doc/web/using-web/index.html b/doc/web/using-web/index.html
index a621c91..404a97a 100644
--- a/doc/web/using-web/index.html
+++ b/doc/web/using-web/index.html
@@ -5,7 +5,7 @@
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Using Web
Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.

Installation
To enable this module, just add following lines to the pom.xml file of your project.
<dependency>
     <groupId>dev.voidframework</groupId>
     <artifactId>voidframework-web</artifactId>
-    <version>1.11.2</version>
+    <version>1.12.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used.
Base
voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly. The default value is 15 seconds.
voidframework.web.errorHandler the implementation of the error handler to use in case of http error. The default value is dev.voidframework.web.http.errorhandler.DefaultErrorHandler.
voidframework.web.contextPath the default context path root. The default value is /.
voidframework.web.routes a list of routing definition classes (must implement the interface AppRoutesDefinition). The default value is [].
voidframework.web.globalFilters a list of routing global filter classes (must implement the interface Filter). The default value is [].
voidframework.web.baseAssetResourcesDirectory the default location of static files in the “resources” directory. The default value is static.
Server
voidframework.web.server.idleTimeout the time without any request to wait before the connection is closed. The default value is 30 seconds.
voidframework.web.server.extraWebServerConfiguration the implementation of the interface ExtraWebServerConfiguration to apply a custom configuration to the Undertow web server. The default value is null.
voidframework.web.server.ioThreads the number of I/O threads. If not specified (value = null or 0), Math.max(Runtime.getRuntime().availableProcessors(), 2) value will be used. The default value is null.
voidframework.web.server.workerThreads the number of Worker threads. If not specified (value = null or 0), ioThreadsNumber * 8 value will be used. The default value is null.
voidframework.web.server.maxBodySize the max body content size. The default value is 1 MiB.
voidframework.web.server.fileSizeThreshold the maximum size allowed in memory before the uploaded file was stored on the disk rather than in memory. The default value is 256 KiB.
voidframework.web.server.tempFileLocation the location where temporary files will be stored. The default value is null (default Java temporary folder).
HTTP
voidframework.web.server.http.listenHost the interface on which the server will listen for non-secure HTTP requests. The default value is 127.0.0.1.
voidframework.web.server.http.listenPort the port on which the server will listen for non-secure HTTP requests. The default value is 9000.
HTTPS
voidframework.web.server.https.listenHost the interface on which the server will listen for HTTPS requests. The default value is 127.0.0.1.
voidframework.web.server.https.listenPort the port on which the server will listen for HTTPS requests. The default value is 9001.
voidframework.web.server.https.ssl.protocols the protocols to use. The default value is ["TLSv1.2", "TLSv1.3"].
voidframework.web.server.https.ssl.ciphers the allowed ciphers. If list is empty, all ciphers will be allowed. The default value is [].
voidframework.web.server.https.ssl.keyStorePath the path where is located the key store. Could be a “resources” path, a URL or a simple path. The default value is null.
voidframework.web.server.https.ssl.keyStoreType the type of the key store. The default value is JKS.
voidframework.web.server.https.ssl.keyStorePassword the password to use to open the key store. The default value is null.
voidframework.web.server.https.ssl.keyAlias the alias of the key to use. If “null” the key will be choosen automatically. The default value is null.
voidframework.web.server.https.ssl.keyPassword the key password. The default value is ${voidframework.web.server.https.ssl.keyStorePassword}.
Language
voidframework.web.language.availableLanguages the available languages. The default value is ["en", "fr"].
voidframework.web.language.cookieName the name of the cookie containing the current language. The default value is VOID_LANG.
voidframework.web.language.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.language.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Flash messages
voidframework.web.flashMessages.cookieName the name of the cookie containing the current flash messages. The default value is VOID_FLASH.
voidframework.web.flashMessages.cookieHttpOnly if the cookie can only be accessed via HTTP. The default value is false.
voidframework.web.flashMessages.cookieSecure if the cookie must be secured, if true, the cookie will be only sent via HTTPS. The default value is false.
Session
voidframework.web.session.cookieName the name of the cookie containing the current session. The default value is VOID_SESS.
voidframework.web.session.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.session.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.session.signatureKey the key used to digitally sign the session content.
voidframework.web.session.timeToLive the session TTL. The default value is 7 days.
CSRF
voidframework.web.csrf.tokenName the token name (used to retrieve token from Body or QueryString). The default value is csrfToken.
voidframework.web.csrf.cookieName the name of the cookie containing the current CSRF. The default value is VOID_CSRF.
voidframework.web.csrf.cookieHttpOnly is the cookie only be accessed via HTTP? The default value is true.
voidframework.web.csrf.cookieSecure is the cookie secured? If true, sent only for HTTPS requests. The default value is false.
voidframework.web.csrf.signatureKey the key used to digitally sign the CSRF token. The default value is ${voidframework.web.session.signatureKey}.
voidframework.web.csrf.timeToLive the CSRF token TTL. The default value is 15 minutes.
Security headers
voidframework.web.securityHeaders.contentTypeOptions the value for the header “X-Content-Type-Options”. The default value is nosniff.
voidframework.web.securityHeaders.frameOptions the value for the header “X-Frame-Options”. The default value is DENY.
voidframework.web.securityHeaders.xssProtection the value for the header “X-XSS-Protection”. The default value is 1; mode=block.
voidframework.web.securityHeaders.crossOriginResourcePolicy the value for the header “Cross-Origin-Resource-Policy”. The default value is same-origin.
voidframework.web.securityHeaders.contentSecurityPolicy the value for the header “Content-Security-Policy”. The default value is default-src 'self'.

© 2022-2023 Void Framework

 Void Framework is released under the MIT License

diff --git a/index.xml b/index.xml
index 156ce81..cf31da3 100644
--- a/index.xml
+++ b/index.xml
@@ -3,13 +3,13 @@ AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframew
 AspectJ AspectJ runtime (aspectjrt) is already provided by the module voidframework-core, but you have to add an extra plugin to compile aspects during the compilation of your application.Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Boot sequencehttps://voidframework.dev/doc/core/boot-sequence/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/boot-sequence/Below is a diagram describing the boot sequence of Void Framework.
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c .Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : In-memoryhttps://voidframework.dev/doc/cache/in-memory-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/in-memory-cache/This implementation of the cache engine is convenient during the development phase because it avoids the installation of a distributed cache server. However, this implementation is absolutely not recommended for use in a production environment.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.
 Configuration The following configuration key can be used in the configuration file of your application.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Cache engine : Redishttps://voidframework.dev/doc/cache/redis-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/redis-cache/This implementation requires the voidframework-redis module to be properly configured.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-cache-redis&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
 Redis module must be properly configured, read more about Redis configuration.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Class scanninghttps://voidframework.dev/doc/core/class-scanning/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/class-scanning/The core of the Void Framework is based on the scanning of different paths to discover elements to load. 5 types of elements are recognised during the scan:
 Classes implementing com.google.inject.Module or extending com.google.inject.AbstractModule Classes annotated with Bindable familly annotation Classes implementing defined interface Classes annotated with Aspect annotation Interfaces annotated with Proxyable annotation Guice module Guice modules that extend the abstract class AbstractModule are automatically detected and loaded when the application starts.Conditional featurehttps://voidframework.dev/doc/core/conditional-feature/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/conditional-feature/Depending on your runtime environment, you may only need to run a few features of your application. And so, load only the necessary modules and bindable classes.
@@ -36,16 +36,16 @@ Installation Void Framework offers different implementations, depending on the i
 @FilterWith({FirstFilter.java, SecondFilter.Filtershttps://voidframework.dev/doc/web/filters/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/filters/Filters are the middleware and are individual functions that make up the request processing pipeline.
 &nbsp; Note that the use of dependencies direct injection is possible in filters. Specific filters The use of filters is done through the use of the @WithFiter annotation. It is possible to specify as many filters as you wish, the order in which they are declared representing the order in which they are used.
 @FilterWith({FirstFilter.java, SecondFilter.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.FreeMarkerhttps://voidframework.dev/doc/template/freemarker/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/freemarker/To generate HTML document with FreeMarker, you have to use the module voidframework-template-freemarker.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-template-freemarker&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Templates location By default, templates should be placed in the resources/views directory.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.template.basePackagePath the location of the templates. The default value is &quot;/views/&quot;. Built-in methods &amp; variables By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:H2https://voidframework.dev/doc/relational-databases/h2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/h2/H2 is an open-source lightweight relational database. It allows you to quickly have an operational database and its use is very practical during the development phase of an application. This module provides the H2 dependency and the useful H2 web console.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-h2&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used in the configuration file of your application:Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.Hibernatehttps://voidframework.dev/doc/relational-databases/persistence-hibernate/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-hibernate/Hibernate is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 &nbsp; Void Framework uses Hibernate 6 (or higher), which that means Java persistence is no longer defined by the Java Persistence API under Java EE, but rather by to the Jakarta Persistence 3.0 specification under Jakarta EE. This means the javax.persistence package is no longer available and is replaced by jakarta.jOOQ ORMhttps://voidframework.dev/doc/relational-databases/persistence-jooq/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/persistence-jooq/jOOQ is an Object Relational Mapper (ORM). It provides a framework for mapping an object-oriented domain model to a relational database.
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
@@ -53,9 +53,9 @@ Installation This module adds support for the Transactional annotation as well a
 Installation This module adds support for the Transactional annotation as well as setting up an DSLContext provider pre-configured with all the data sources configured via the datasource module. There is no special configuration to apply, just add the voidframework-persistence-jooq module to the pom.xml file of your project.
 &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-persistence-jooq&lt;/artifactId&gt; &lt;version&gt;1.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.JUnit's extensionhttps://voidframework.dev/doc/testing/junit-extension/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/testing/junit-extension/It is very important to test the code of an application. Void Framework provides tools for JUnit 5 to run your unit tests in a ready-to-use context as well as with support for Mockito annotations.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-test&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; JUnit&rsquo;s extension The JUnit 5 extension will initialise the Void Framework application and initialise the variables annotated with Mockito annotations.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
 // Random CUID final CUID cuid = CUID.randomCUID(); // CUID from String representating a CUID final CUID cuid = CUID.fromString(&#34;cl9gts1kw00393647w1z4v2tc&#34;); // Check if String contains a valid CUID (implicitly called by &#34;fromString&#34; method) final boolean isValid = CUID.Langhttps://voidframework.dev/doc/core/lang/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/core/lang/The dev.voidframework.core.lang package contains a set of Java classes that extend the basic JDK.
 CUID CUID is a collision-resistant ID optimized for horizontal scaling and performance. Read more at https://usecuid.org/. Read the Java file to get more information about available methods.
@@ -66,22 +66,22 @@ priority is used to define when the method will be called in relation to the oth
 &nbsp; It is possible to have several methods of a class annotated with the same annotation. @LifeCycleStart Indicates that this method should be called when the application starts.
 The annotation accepts the following parameter:
 priority is used to define when the method will be called in relation to the others.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Apache Commons Emailhttps://voidframework.dev/doc/sendmail/mailer-apache-commons-email/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-apache-commons-email/This implementation of the mailer uses the Apache Commons Email library. It allows you to easily send email via SMTP.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail-commonsemail&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.
 Configuration The following configuration keys can be used in the configuration file of your application:
 voidframework.sendmail.commonsemail.username user name for authentication. The default value is null. voidframework.sendmail.commonsemail.password password for authentication.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Mailer : Dummyhttps://voidframework.dev/doc/sendmail/mailer-dummy/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/mailer-dummy/This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.Redishttps://voidframework.dev/doc/nosql-databases/redis/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/nosql-databases/redis/Sometimes a relational database does not fit the need, so you have to turn to more specific, non-relational databases. Void Framework provides the tools to use the NoSQL database Redis.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-redis&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration key can be used in the configuration file of your application.
 voidframework.redis.host the Redis server host.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
 voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.reference.confhttps://voidframework.dev/doc/advanced/advanced/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/advanced/advanced/The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
-voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.1 2023-12-05 Security Upgrade logback-classic version to 1.4.14 ( CVE-2023-6378) 1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.11.1 2023-12-05 Security Upgrade logback-classic version to 1.4.14 ( CVE-2023-6378) 1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Improved AbstractCacheEngine now using KryoUtils Improved Add TypedMap static "constructor" methods Improved Redis ACL authentication (username/password) Improved Upgrade dependencies Fixed Application must shutdown on "Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
+voidframework-bucket4j reference.conf voidframework-cache reference.conf voidframework-core reference.conf voidframework-datasource-c3p0 reference.conf voidframework-datasource-hikaricp reference.conf voidframework-healthcheck reference.conf voidframework-i18n reference.conf voidframework-migration-flyway reference.conf voidframework-persistence-hibernate reference.conf voidframework-redis reference.conf voidframework-remoteconf-etcd reference.conf voidframework-remoteconf-http reference.conf voidframework-restclient reference.conf voidframework-scheduler reference.conf voidframework-sendmail reference.Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.12.0 2024-01-02 New Add ClassMethodUtils class Fixed Constants PARENTHESIS_OPEN and PARENTHESIS_CLOSE are no longer inverted Improved Error page (dev mode): display filename & partial content Improved Upgrade dependencies 1.11.1 2023-12-05 Security Upgrade logback-classic version to 1.4.14 ( CVE-2023-6378) 1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Fixed Application must shutdown on "Release noteshttps://voidframework.dev/releasenotes/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/releasenotes/1.12.0 2024-01-02 New Add ClassMethodUtils class Fixed Constants PARENTHESIS_OPEN and PARENTHESIS_CLOSE are no longer inverted Improved Error page (dev mode): display filename & partial content Improved Upgrade dependencies 1.11.1 2023-12-05 Security Upgrade logback-classic version to 1.4.14 ( CVE-2023-6378) 1.11.1 2023-11-23 Fixed Fix SQLDialect detection KO (jOOQ) Fixed Fix can't override Hibernate dialect 1.11.0 2023-10-19 New Add KryoUtils class New Add new method ClassResolverUtils::isClassAvailable New Add new Kryo serializers New Add MockitoUtils class (spy lambda) Fixed Application must shutdown on "Render templatehttps://voidframework.dev/doc/web/render-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/render-template/The web module also integrates the template module with the Freemarker rendering engine by default. This allows controllers to return html content easily.
 Although you can manually use the template engine, in most cases this would not be handy. However, you can use the TemplateResult class which will make it easier to use the renderer.
 Built-in methods &amp; variables By default, the module voidframework-template-freemarker provide a set of methods and variables that will be accessible in templates.Requirementshttps://voidframework.dev/doc/getting-started/requirements/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/getting-started/requirements/To use the Void Framework, you need Java JDK 17 or higher, Maven 3 or higher and the Void Framework JAR files. These JAR files are published to the Maven Repository.
 Verifying and installing Java To check that you have Java JDK 17 or higher, enter the following in a shell:
@@ -91,11 +91,11 @@ Verifying and installing Java To check that you have Java JDK 17 or higher, ente
 #&gt; java -version You should see something like:
 openjdk version &#34;17.0.2&#34; 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Retrofit 2https://voidframework.dev/doc/rest-client/retrofit2/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/rest-client/retrofit2/Retrofit 2 is a REST Client for Java allowing to retrieve and upload data via HTTP.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-restclient&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; How it work All interfaces annotated with @RestClient will be automatically proxyfied with the Retrofit 2 client.
 Configuration The following configuration key can be used in the configuration file of your application
 voidframework.restclient.maxIdleConnections the number of connection to keep idle.Scheduling a local jobhttps://voidframework.dev/doc/scheduler/scheduling-job-cron/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/scheduler/scheduling-job-cron/If your application have to schedule a job in a scheduled way (ie: every 5 seconds), not dependending when the application has started, you can schedule job by using delay. In other hand, if you want a precise scheduling not depending on when the application has started, you can use a CRON expression.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
@@ -104,8 +104,8 @@ Installation To enable this module, just add following lines to the pom.xml file
 &lt;dependency&gt; &lt;groupId&gt;dev.Security headershttps://voidframework.dev/doc/web/security-headers/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/security-headers/Void Framework provides a basic filter to add certain headers to HTTP responses by default. These headers allow you to add an extra level of security to your application.
 Configuration The following configuration keys can be used in the configuration file of your application.
 voidframework.web.securityHeaders.contentTypeOptions the value for the header &ldquo;X-Content-Type-Options&rdquo;. The default value is nosniff. voidframework.web.securityHeaders.frameOptions the value for the header &ldquo;X-Frame-Options&rdquo;. The default value is DENY. voidframework.web.securityHeaders.xssProtection the value for the header &ldquo;X-XSS-Protection&rdquo;.Sending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
-Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSending emailshttps://voidframework.dev/doc/sendmail/sending-emails/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/sendmail/sending-emails/If your application needs to send a few emails, you can easily do so via the voidframework-sendmail module. Sending emails is a not blocking operation, the emails are added to a queue that will be consumed asynchronously.
+Installation &lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-sendmail&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; In addition to this basic module, you will need a mailer implementation. By default, the base module provides an implementation intended for local testing. For normal use, you can for example use the voidframework-sendmail-commonsemail moduleSessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Sessionhttps://voidframework.dev/doc/web/session/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/session/If you need to store data between HTTP requests, you can store it in the session. The data stored in the session is available throughout the user&rsquo;s session.
 &nbsp; Note that the session is not stored on the server side, but on the client side via the use of a digitally signed Cookie. Because session is implemented using cookies, there are some implications. The data size is limited to 4 KiB Only string can be stored Configuration The following configuration keys can be used in the configuration file of your application.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
 @Transactional The transactional annotation itself defines the scope of a single database transaction.Transactionalhttps://voidframework.dev/doc/relational-databases/transactional/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/relational-databases/transactional/It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.
@@ -117,19 +117,19 @@ Using conversion The conversion is used via the Conversion service which is acce
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using cachehttps://voidframework.dev/doc/cache/using-cache/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/cache/using-cache/Void Framework provides the tools to use a cache system. Caching can be done in two different ways, via the use of annotations or programmatically via the use of the CacheEngine.
 &nbsp; If no CacheEngine implementation was specified, the cache will not be active. &nbsp; Note that caching a Result (Web) object can lead to errors during deserialization, especially if Result contains an InputStream. Serialization and deserialization of cached objects is handled by the Kryo library.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using internationalizationhttps://voidframework.dev/doc/internationalization/using-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/internationalization/using-i18n/Depending on your needs, you may need to use translated messages in different languages. By default the Void Framework provides a ResourceBundle based implementation. If your needs require more advanced management or different storage (ie: DB rather than files), you can easily use your own implementation.
 To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-i18n&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Defining messages Translations should be placed in a file named messages_&lt;LANG&gt;.Using templatehttps://voidframework.dev/doc/template/using-template/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/template/using-template/Sooner or later you will need to generate documents (HTML, PDF&hellip;). Void Framework provides all the tools you need!
 Example public class TemplateExample { private final TemplateRenderer templateRenderer; @Inject public TemplateExample(final TemplateRenderer templateRenderer) { this.templateRenderer = templateRenderer; } public void renderTemplate() { final Map&lt;String, Object&gt; dataModel = new HashMap&lt;&gt;(); dataModel.put(&#34;greating.msg&#34;, &#34;Hello World!&#34;) final String result = templateRenderer.render( &#34;renderWithDataModel.ftl&#34;, Locale.ENGLISH, dataModel); System.out.println(result); } } &nbsp; Note that the data Map must be mutable.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Virtual File Storagehttps://voidframework.dev/doc/vfs/using-vfs/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/vfs/using-vfs/When you need to store or retrieve files, you don&rsquo;t necessarily want to deal with the complexity or you just want to hide it behind an easy to use interface. Void Framework exposes the VirtualFileStorage interface which allows you to use any storage engine very simply within your application.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-vfs&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration Different VirtualFileStorage implementations must be configured in voidframework.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.Using Webhttps://voidframework.dev/doc/web/using-web/Mon, 01 Jan 0001 00:00:00 +0000https://voidframework.dev/doc/web/using-web/Does your application need to have web entry points (ie: http(s) or websocket) to provide an API or web pages? The voidframework-web module will best meet your expectations.
 Installation To enable this module, just add following lines to the pom.xml file of your project.
-&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.11.2&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
+&lt;dependency&gt; &lt;groupId&gt;dev.voidframework&lt;/groupId&gt; &lt;artifactId&gt;voidframework-web&lt;/artifactId&gt; &lt;version&gt;1.12.0&lt;/version&gt; &lt;/dependency&gt; Configuration The following configuration keys can be used.
 Base
 voidframework.web.gracefulStopTimeout the time (duration or milliseconds) for the web daemon to shut down properly.
\ No newline at end of file
diff --git a/releasenotes/index.html b/releasenotes/index.html
index 005af1b..6320995 100644
--- a/releasenotes/index.html
+++ b/releasenotes/index.html
@@ -1,15 +1,16 @@
-Void Framework – Release notes
+Void Framework – Release notes
 Void Framework
Documentation
    
-Release notes
1.11.1

+Release notes
1.12.0

+2024-01-02
New Add ClassMethodUtils class
Fixed Constants PARENTHESIS_OPEN and PARENTHESIS_CLOSE are no longer inverted
Improved Error page (dev mode): display filename & partial content
Improved Upgrade dependencies

1.11.1

 2023-12-05
Security Upgrade logback-classic version to 1.4.14 ( CVE-2023-6378)

1.11.1

 2023-11-23
Fixed Fix SQLDialect detection KO (jOOQ)
Fixed Fix can't override Hibernate dialect

1.11.0

-2023-10-19
New Add KryoUtils class
New Add new method ClassResolverUtils::isClassAvailable
New Add new Kryo serializers
New Add MockitoUtils class (spy lambda)
Improved AbstractCacheEngine now using KryoUtils
Improved Add TypedMap static "constructor" methods
Improved Redis ACL authentication (username/password)
Improved Upgrade dependencies
Fixed Application must shutdown on "start" lifecycle failure
Fixed H2 web console fail to start because password not encoded

1.10.0

+2023-10-19
New Add KryoUtils class
New Add new method ClassResolverUtils::isClassAvailable
New Add new Kryo serializers
New Add MockitoUtils class (spy lambda)
Fixed Application must shutdown on "start" lifecycle failure
Fixed H2 web console fail to start because password not encoded
Improved AbstractCacheEngine now using KryoUtils
Improved Add TypedMap static "constructor" methods
Improved Redis ACL authentication (username/password)
Improved Upgrade dependencies

1.10.0

 2023-09-11
New REST Client authentication (API Key, Basic, Bearer)
Improved New constant values: CharConstants.EXCLAMATION_MARK, CharConstants.PIPE, StringConstants.EXCLAMATION_MARK and StringConstants.PIPE
Improved Upgrade dependencies

1.9.0

 2023-07-13
New AspectJ
New REST client
New Bucket4J (rate-limiting)
New Add ConfigurationUtils class
Improved Upgrade dependencies
Improved New constant value: CharConstants.TAB and StringConstants.TAB

1.8.1

 2023-16-16
Improved Add exception AppLauncherException.ModuleConstructorNotFound

1.8.0

-2023-05-18
New Proxyable interface
New H2 web console
Improved Bind automatically interface with single implementation
Improved Updated version of all dependencies
Fixed Guice module implementing interface not recognized

1.7.0

-2023-04-12
Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492)
New Conditional feature RunInDevModeConditionalFeature
New Sendmail module
New Sendmail module implementation Apache Commons Email
New Add @CachePut annotation
Improved Javadoc
Improved HttpClient is now used instead of raw URL connection (Remote Configuration)
Improved Result: method badRequest(final String content, final String contentType)
Improved Updated version of all dependencies
Fixed Transactional annotation multiple calls

1.6.1

+2023-05-18
New Proxyable interface
New H2 web console
Fixed Guice module implementing interface not recognized
Improved Bind automatically interface with single implementation
Improved Updated version of all dependencies

1.7.0

+2023-04-12
Security Upgrade Undertow version to 2.3.5 (CVE-2022-4492)
New Conditional feature RunInDevModeConditionalFeature
New Sendmail module
New Sendmail module implementation Apache Commons Email
New Add @CachePut annotation
Fixed Transactional annotation multiple calls
Improved Javadoc
Improved HttpClient is now used instead of raw URL connection (Remote Configuration)
Improved Result: method badRequest(final String content, final String contentType)
Improved Updated version of all dependencies

1.6.1

 2023-02-24
Fixed HTTP webserver graceful shutdown not honored

1.6.0

 2023-02-11
New Web module can now respond to requests securely via HTTPS
New NotInstance validation constraint
New Utility class DurationUtils
Improved Graceful stop timeout is now a duration (with time unit)
Improved Commercial at "@" constant now available in CharConstants and StringConstants classes
Improved Annotation RequestVariable can now use fallback value
Improved Updated version of all dependencies

1.5.1

 2023-01-07
Fixed JavaScript i18n reverse routing name (js_i18n)

1.5.0


From f6b4440a603902a00f4f125e4544287cfee1c526 Mon Sep 17 00:00:00 2001
From: Thibault Meyer 
Date: Thu, 1 Feb 2024 21:42:24 +0000
Subject: [PATCH 67/75] Automated website build

---
 doc/advanced/advanced/index.html                          | 2 +-
 doc/advanced/aspect-oriented-programming/index.html       | 2 +-
 doc/advanced/creating-module/index.html                   | 2 +-
 doc/advanced/index.html                                   | 2 +-
 doc/cache/in-memory-cache/index.html                      | 2 +-
 doc/cache/index.html                                      | 2 +-
 doc/cache/redis-cache/index.html                          | 2 +-
 doc/cache/using-cache/index.html                          | 2 +-
 doc/core/boot-sequence/index.html                         | 2 +-
 doc/core/class-scanning/index.html                        | 2 +-
 doc/core/conditional-feature/index.html                   | 2 +-
 doc/core/configuration/index.html                         | 2 +-
 doc/core/index.html                                       | 2 +-
 doc/core/lang/index.html                                  | 2 +-
 doc/core/life-cycle/index.html                            | 2 +-
 doc/core/type-conversion/index.html                       | 2 +-
 doc/getting-started/index.html                            | 2 +-
 doc/getting-started/new-application/index.html            | 2 +-
 doc/getting-started/requirements/index.html               | 2 +-
 doc/getting-started/upgrading-from-old-version/index.html | 2 +-
 doc/i18n/index.html                                       | 2 +-
 doc/index.html                                            | 2 +-
 doc/internationalization/using-i18n/index.html            | 2 +-
 doc/nosql-databases/index.html                            | 2 +-
 doc/nosql-databases/redis/index.html                      | 2 +-
 doc/relational-databases/datasource/index.html            | 2 +-
 doc/relational-databases/h2/index.html                    | 2 +-
 doc/relational-databases/index.html                       | 2 +-
 doc/relational-databases/persistence-hibernate/index.html | 2 +-
 doc/relational-databases/persistence-jooq/index.html      | 2 +-
 doc/relational-databases/transactional/index.html         | 2 +-
 doc/rest-client/index.html                                | 2 +-
 doc/rest-client/retrofit2/index.html                      | 2 +-
 doc/scheduler/index.html                                  | 2 +-
 doc/scheduler/scheduling-job-cron/index.html              | 2 +-
 doc/sendmail/index.html                                   | 2 +-
 doc/sendmail/mailer-apache-commons-email/index.html       | 2 +-
 doc/sendmail/mailer-dummy/index.html                      | 2 +-
 doc/sendmail/sending-emails/index.html                    | 2 +-
 doc/template/freemarker/index.html                        | 2 +-
 doc/template/index.html                                   | 2 +-
 doc/template/using-template/index.html                    | 2 +-
 doc/testing/index.html                                    | 2 +-
 doc/testing/junit-extension/index.html                    | 2 +-
 doc/vfs/index.html                                        | 2 +-
 doc/vfs/using-vfs/index.html                              | 2 +-
 doc/web/controller/index.html                             | 2 +-
 doc/web/filters/index.html                                | 2 +-
 doc/web/index.html                                        | 2 +-
 doc/web/render-template/index.html                        | 2 +-
 doc/web/security-csrf/index.html                          | 2 +-
 doc/web/security-headers/index.html                       | 2 +-
 doc/web/session/index.html                                | 2 +-
 doc/web/using-web/index.html                              | 2 +-
 index.html                                                | 2 +-
 releasenotes/index.html                                   | 2 +-
 56 files changed, 56 insertions(+), 56 deletions(-)

diff --git a/doc/advanced/advanced/index.html b/doc/advanced/advanced/index.html
index 931f8a6..594ec35 100644
--- a/doc/advanced/advanced/index.html
+++ b/doc/advanced/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – reference.conf

 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-bucket4j reference.conf
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-restclient reference.conf
voidframework-scheduler reference.conf
voidframework-sendmail reference.conf
voidframework-sendmail-commonsemail reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

reference.conf
The reference.conf files define the various configuration keys and default values. These files are the first to be loaded when the application starts. On this page you will find links to the complete list of reference.conf files used by Void Framework.
voidframework-bucket4j reference.conf
voidframework-cache reference.conf
voidframework-core reference.conf
voidframework-datasource-c3p0 reference.conf
voidframework-datasource-hikaricp reference.conf
voidframework-healthcheck reference.conf
voidframework-i18n reference.conf
voidframework-migration-flyway reference.conf
voidframework-persistence-hibernate reference.conf
voidframework-redis reference.conf
voidframework-remoteconf-etcd reference.conf
voidframework-remoteconf-http reference.conf
voidframework-restclient reference.conf
voidframework-scheduler reference.conf
voidframework-sendmail reference.conf
voidframework-sendmail-commonsemail reference.conf
voidframework-template-freemarker reference.conf
voidframework-validation reference.conf
voidframework-vfs reference.conf
voidframework-web-healthcheck reference.conf
voidframework-web reference.conf

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/advanced/aspect-oriented-programming/index.html b/doc/advanced/aspect-oriented-programming/index.html
index d51efb3..0345ac5 100644
--- a/doc/advanced/aspect-oriented-programming/index.html
+++ b/doc/advanced/aspect-oriented-programming/index.html
@@ -37,7 +37,7 @@
 </plugin>
 
 
 If you are using an IDE, remember to configure it so that it executes the goal aspectj:compile before running your application. In IntelliJ, go to Maven tab, plugin, aspectj, left-click on aspectj:compile, choose "Execute before Run/Debug".
 
-Direct injection via constructor can't be used on classes annotated with @Aspect.
Read more about AspectJ at:
https://www.eclipse.org/aspectj/doc/released/progguide/index.html
https://www.baeldung.com/aspectj

Guice
Read more about Guice AOP at:
https://github.com/google/guice/wiki/AOP
https://www.baeldung.com/guice

© 2022-2023 Void Framework

+Direct injection via constructor can't be used on classes annotated with @Aspect.
Read more about AspectJ at:
https://www.eclipse.org/aspectj/doc/released/progguide/index.html
https://www.baeldung.com/aspectj

Guice
Read more about Guice AOP at:
https://github.com/google/guice/wiki/AOP
https://www.baeldung.com/guice

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/advanced/creating-module/index.html b/doc/advanced/creating-module/index.html
index 6913bcd..3a4f992 100644
--- a/doc/advanced/creating-module/index.html
+++ b/doc/advanced/creating-module/index.html
@@ -27,7 +27,7 @@
     }
 }
 
 
-Remember that the module must be in a path that is scanned when the application starts. If this is not the case, you can add a new path via the configuration key voidframework.core.acceptedScanPaths.

© 2022-2023 Void Framework

+Remember that the module must be in a path that is scanned when the application starts. If this is not the case, you can add a new path via the configuration key voidframework.core.acceptedScanPaths.

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/advanced/index.html b/doc/advanced/index.html
index 28af2b0..1275c6d 100644
--- a/doc/advanced/index.html
+++ b/doc/advanced/index.html
@@ -1,7 +1,7 @@
 Void Framework – Advanced
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Advanced

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Advanced

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/in-memory-cache/index.html b/doc/cache/in-memory-cache/index.html
index e465391..bbdbe08 100644
--- a/doc/cache/in-memory-cache/index.html
+++ b/doc/cache/in-memory-cache/index.html
@@ -7,7 +7,7 @@
     <artifactId>voidframework-cache</artifactId>
     <version>1.12.0</version>
 </dependency>
-
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022-2023 Void Framework

+
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.MemoryCacheEngine in your application configuration file.

Configuration
The following configuration key can be used in the configuration file of your application.
voidframework.cache.inMemory.flushWhenFullMaxItem the maximum number of items to be kept in the cache before it gets flushed.

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/index.html b/doc/cache/index.html
index 000d106..a1dab3f 100644
--- a/doc/cache/index.html
+++ b/doc/cache/index.html
@@ -1,7 +1,7 @@
 Void Framework – Cache
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Cache

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/redis-cache/index.html b/doc/cache/redis-cache/index.html
index 0c238f5..b13e445 100644
--- a/doc/cache/redis-cache/index.html
+++ b/doc/cache/redis-cache/index.html
@@ -7,7 +7,7 @@
     <artifactId>voidframework-cache-redis</artifactId>
     <version>1.12.0</version>
 </dependency>
-
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022-2023 Void Framework

+
To enable In-memory cache engine, you have to set voidframework.cache.engine to dev.voidframework.cache.engine.RedisCacheEngine in your application configuration file.
Redis module must be properly configured, read more about Redis configuration.

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/cache/using-cache/index.html b/doc/cache/using-cache/index.html
index f2cbe5b..8ebedee 100644
--- a/doc/cache/using-cache/index.html
+++ b/doc/cache/using-cache/index.html
@@ -25,7 +25,7 @@
         cacheEngine.set("key", "value");
     }
 }
-

© 2022-2023 Void Framework

+

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/boot-sequence/index.html b/doc/core/boot-sequence/index.html
index 25a016d..1b86eb5 100644
--- a/doc/core/boot-sequence/index.html
+++ b/doc/core/boot-sequence/index.html
@@ -2,7 +2,7 @@
 S c a N n O C l N a O s s p a S R t o e h r m s t o L t c G o e l u L R a a i o e L d C s ( c a g i o s 3 e d i f l n p a s e o f a ) m G t C c . t o u e y a h d i r c l P . u c l r b">Void Framework – Boot sequence
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Boot sequence
Below is a diagram describing the boot sequence of Void Framework.


© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/class-scanning/index.html b/doc/core/class-scanning/index.html
index 797eb50..d1ad485 100644
--- a/doc/core/class-scanning/index.html
+++ b/doc/core/class-scanning/index.html
@@ -25,7 +25,7 @@
         </execution>
     </executions>
 </plugin>
-

© 2022-2023 Void Framework

+

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/conditional-feature/index.html b/doc/core/conditional-feature/index.html
index 5fbdee0..b543447 100644
--- a/doc/core/conditional-feature/index.html
+++ b/doc/core/conditional-feature/index.html
@@ -30,7 +30,7 @@
 @ConditionalFeature(RunInDevModeCondition.class)
 public @interface RunInDevModeConditionalFeature {
 }
-

© 2022-2023 Void Framework

+

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/configuration/index.html b/doc/core/configuration/index.html
index c014b86..953b3af 100644
--- a/doc/core/configuration/index.html
+++ b/doc/core/configuration/index.html
@@ -90,7 +90,7 @@
         }
     }
 }
-

Creating a Remote configuration provider
Creating a new provider is very easy. Simply implement the RemoteConfigurationProvider interface or extend the AbstractRemoteConfigurationProvider abstract class.

© 2022-2023 Void Framework

+

Creating a Remote configuration provider
Creating a new provider is very easy. Simply implement the RemoteConfigurationProvider interface or extend the AbstractRemoteConfigurationProvider abstract class.

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/index.html b/doc/core/index.html
index 7806f8c..d162fe5 100644
--- a/doc/core/index.html
+++ b/doc/core/index.html
@@ -1,7 +1,7 @@
 Void Framework – Core
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Core

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Core

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/lang/index.html b/doc/core/lang/index.html
index 202dd2a..614f0be 100644
--- a/doc/core/lang/index.html
+++ b/doc/core/lang/index.html
@@ -18,7 +18,7 @@
 final TypedMap typedMap = new TypedMap();
 
 typedMap.put(STRING_KEY, "Hello World");
-

© 2022-2023 Void Framework

+

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/life-cycle/index.html b/doc/core/life-cycle/index.html
index 0916a28..ae92bb2 100644
--- a/doc/core/life-cycle/index.html
+++ b/doc/core/life-cycle/index.html
@@ -23,7 +23,7 @@
     public void onStop() {
     }
 }
-

© 2022-2023 Void Framework

+

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/core/type-conversion/index.html b/doc/core/type-conversion/index.html
index 7f36a23..1ae5b96 100644
--- a/doc/core/type-conversion/index.html
+++ b/doc/core/type-conversion/index.html
@@ -30,7 +30,7 @@
     }
 }
 
 
-A type converter must be stateless, simple and thread safe. Even if direct injection is available, it is not recommended to perform too complex, blocking or slow operation.

© 2022-2023 Void Framework

+A type converter must be stateless, simple and thread safe. Even if direct injection is available, it is not recommended to perform too complex, blocking or slow operation.

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/index.html b/doc/getting-started/index.html
index 89ebcd9..086da75 100644
--- a/doc/getting-started/index.html
+++ b/doc/getting-started/index.html
@@ -1,7 +1,7 @@
 Void Framework – Getting Started
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Getting Started

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Getting Started

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/new-application/index.html b/doc/getting-started/new-application/index.html
index 3f7b30f..f32b8d8 100644
--- a/doc/getting-started/new-application/index.html
+++ b/doc/getting-started/new-application/index.html
@@ -42,7 +42,7 @@
 }
 

Application launcher
To start the application, you have to instantiate ApplicationLauncher and then call the launch method.
final VoidApplication app = new VoidApplication();
 app.launch();
-

Run your application
You can now start your application and go to the URL http://127.0.0.1:9000 in your favourite web browser.

© 2022-2023 Void Framework

+

Run your application
You can now start your application and go to the URL http://127.0.0.1:9000 in your favourite web browser.

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/requirements/index.html b/doc/getting-started/requirements/index.html
index 15499ac..86b386e 100644
--- a/doc/getting-started/requirements/index.html
+++ b/doc/getting-started/requirements/index.html
@@ -12,7 +12,7 @@
 Java version: 17.0.2, vendor: Oracle Corporation, runtime: C:\Users\user\.jdks\openjdk-17.0.2
 Default locale: en_US, platform encoding: UTF-8
 OS name: "windows 11", version: "10.0", arch: "amd64", family: "windows"
-
If Maven is not available on your computer, you can get Maven from Apache Maven Project.

© 2022-2023 Void Framework

+
If Maven is not available on your computer, you can get Maven from Apache Maven Project.

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/getting-started/upgrading-from-old-version/index.html b/doc/getting-started/upgrading-from-old-version/index.html
index 8342a6d..7bf23e7 100644
--- a/doc/getting-started/upgrading-from-old-version/index.html
+++ b/doc/getting-started/upgrading-from-old-version/index.html
@@ -2,7 +2,7 @@
 1.0.0 Initial relea">Void Framework – Upgrading from old version
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.0.0
Initial release

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

1.6.0
Configuration keys voidframework.web.server.listenHost and voidframework.web.server.listenPort have been renamed to voidframework.web.server.http.listenHost and voidframework.web.server.http.listenPort

1.8.0
Guice 7.0 only supports the jakarta.inject, jakarta.servlet and jakarta.persistence namespaces. Read more at https://github.com/google/guice/wiki/Guice700

1.12.0
Constants PARENTHESIS_OPEN and PARENTHESIS_CLOSE are no longer inverted. If you use these two constants, take care to adapt their use

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Upgrading from old version
Sometimes important changes will be introduced that will break the backwards compatibility with older versions of the framework. On this page you will find the necessary steps to make your application work with the latest version.

1.0.0
Initial release

1.1.0
ApplicationLauncher has been renamed to VoidApplication
The setting key voidframework.web.session.signatureKey is now required

1.2.0
The CSRF filter has been moved to the dev.voidframework.web.http.filter.csrf package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
The Security Headers filter has been moved to the dev.voidframework.web.http.filter.security package, if you use this filter in your application, you will need to modify the configuration key voidframework.web.globalFilters
Annotations NoCSRF, RequestBody, RequestPath, RequestRoute, RequestVariable and WithFilter has been moved to the package dev.voidframework.web.http.annotation

1.3.0
Annotations @CacheRemove and @CacheResult are now in the package dev.voidframework.cache.annotation
Redis parameter connectionTimeout is now a duration, a time unit must be provided
addInList method of the voidframework-redis module now adds items to the end of the list
Classes from dev.voidframework.core.helper has been moved to dev.voidframework.core.utils and the suffix Utils has been added (ie: IO is now named IOUtils)
Method Result::redirectPermanentlyTo has been renamed to Result::redirectMovedPermanently
Method Result::redirectTemporaryTo has been renamed to Result::redirectFound
Class HttpMimeType has been renamed to HttpMimeTypes
Method HttpRequestBodyContent::asRaw now return an InputStream
Class ValidationError is now a record. All methods are now named without any prefix (ie: getMessage() is now named message())

1.4.0
Method Router::addRoute has changed. The routeUrl parameter is now of type RouteURL. You can use RouteURL::of to migrate to the new format

1.5.0
Annotation @BindClass has been renamed to @Bindable

1.6.0
Configuration keys voidframework.web.server.listenHost and voidframework.web.server.listenPort have been renamed to voidframework.web.server.http.listenHost and voidframework.web.server.http.listenPort

1.8.0
Guice 7.0 only supports the jakarta.inject, jakarta.servlet and jakarta.persistence namespaces. Read more at https://github.com/google/guice/wiki/Guice700

1.12.0
Constants PARENTHESIS_OPEN and PARENTHESIS_CLOSE are no longer inverted. If you use these two constants, take care to adapt their use

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/i18n/index.html b/doc/i18n/index.html
index 9ed3d4a..f199d17 100644
--- a/doc/i18n/index.html
+++ b/doc/i18n/index.html
@@ -1,7 +1,7 @@
 Void Framework – Internationalization
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Internationalization

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Internationalization

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/index.html b/doc/index.html
index 729d186..319fda8 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -1,7 +1,7 @@
 Void Framework – Documentation
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Documentation

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Documentation

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/internationalization/using-i18n/index.html b/doc/internationalization/using-i18n/index.html
index fadfc8e..515d0fa 100644
--- a/doc/internationalization/using-i18n/index.html
+++ b/doc/internationalization/using-i18n/index.html
@@ -51,7 +51,7 @@
     // Output: Inbox "Unread" contains 42 messages
     i18n.getMessage(Locale.ENGLISH, 42, "inbox", "Unread", 42);
 }
-

© 2022-2023 Void Framework

+

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/nosql-databases/index.html b/doc/nosql-databases/index.html
index 2983ffa..e47af5b 100644
--- a/doc/nosql-databases/index.html
+++ b/doc/nosql-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – NoSQL Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

NoSQL Databases

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

NoSQL Databases

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/nosql-databases/redis/index.html b/doc/nosql-databases/redis/index.html
index 2baedcc..bfd2c96 100644
--- a/doc/nosql-databases/redis/index.html
+++ b/doc/nosql-databases/redis/index.html
@@ -26,7 +26,7 @@
         final long nextValue = this.redis.increment("incr.key");
     }
 }
-

© 2022-2023 Void Framework

+

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/datasource/index.html b/doc/relational-databases/datasource/index.html
index 043013f..62274cc 100644
--- a/doc/relational-databases/datasource/index.html
+++ b/doc/relational-databases/datasource/index.html
@@ -56,7 +56,7 @@
       conn.close();
     }
 }
-

© 2022-2023 Void Framework

+

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/h2/index.html b/doc/relational-databases/h2/index.html
index 9d2f98c..f6d46ff 100644
--- a/doc/relational-databases/h2/index.html
+++ b/doc/relational-databases/h2/index.html
@@ -7,7 +7,7 @@
     <version>1.12.0</version>
 </dependency>
 

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.h2.webPort the listen port of the H2 console. The default value is 9002.
voidframework.h2.webAdminPassword the password to access preferences and tools of H2 console. The default value is null (disabled).
voidframework.h2.webAllowOthers specifies if other computers are allowed to connect. The default value is false.

Open the web console
Once your application has started, you can access the H2 web console by going to http://127.0.0.1:9002.
 
-Note that H2 web console will be started only if the application is run in development mode (voidframework.core.runInDevMode = true).

© 2022-2023 Void Framework

+Note that H2 web console will be started only if the application is run in development mode (voidframework.core.runInDevMode = true).

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/index.html b/doc/relational-databases/index.html
index 0018263..544047e 100644
--- a/doc/relational-databases/index.html
+++ b/doc/relational-databases/index.html
@@ -1,7 +1,7 @@
 Void Framework – Relational Databases
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Relational Databases

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Relational Databases

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/persistence-hibernate/index.html b/doc/relational-databases/persistence-hibernate/index.html
index 667d046..cecb732 100644
--- a/doc/relational-databases/persistence-hibernate/index.html
+++ b/doc/relational-databases/persistence-hibernate/index.html
@@ -85,7 +85,7 @@
 
         return conversion.convert(newsModelList, NewsModel.class, News.class);
     }
-

Speed-up PersistenceEntityFactory initialization time
By default, Void Framework tells the PersistenceEntityFactory to scan all JARs of the application’s and dependencies. This scan is necessary to detect models. If you want to greatly improve this initialization time, it is advisable to set the voidframework.persistence.modelsJarUrlPattern configuration key to indicate which JARs to keep. The could be null, a regular expression, or auto (default value).
If the configuration is set to null, only the current JAR / classpath (when started in IDE) will be used. auto is like using the regular expression (.*).

© 2022-2023 Void Framework

+

Speed-up PersistenceEntityFactory initialization time
By default, Void Framework tells the PersistenceEntityFactory to scan all JARs of the application’s and dependencies. This scan is necessary to detect models. If you want to greatly improve this initialization time, it is advisable to set the voidframework.persistence.modelsJarUrlPattern configuration key to indicate which JARs to keep. The could be null, a regular expression, or auto (default value).
If the configuration is set to null, only the current JAR / classpath (when started in IDE) will be used. auto is like using the regular expression (.*).

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/persistence-jooq/index.html b/doc/relational-databases/persistence-jooq/index.html
index 886be23..d557f7d 100644
--- a/doc/relational-databases/persistence-jooq/index.html
+++ b/doc/relational-databases/persistence-jooq/index.html
@@ -121,7 +121,7 @@
 
         return conversion.convert(newsModelList, NewsModel.class, News.class);
     }
-

© 2022-2023 Void Framework

+

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/relational-databases/transactional/index.html b/doc/relational-databases/transactional/index.html
index 3479cf0..0b69c2f 100644
--- a/doc/relational-databases/transactional/index.html
+++ b/doc/relational-databases/transactional/index.html
@@ -2,7 +2,7 @@
 Void Framework
Documentation
    
 Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Transactional
It is possible to work within a transaction in two ways: manually or via the use of the @Transactional annotation. The first one is highly dependent of the used backend (ie: Hibernate vs jOOQ), the second one is fully handled by Void Framework. For more information on the manual management of transactions, go to the page corresponding to the backend used.

@Transactional
The transactional annotation itself defines the scope of a single database transaction. Void Framework fully implements Transactional (Jakarta) annotation, so all availables options can be used without any restrictions.
If annotation is used both at class and method level, the second one will take ascendance.
 
-Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

© 2022-2023 Void Framework

+Note that Transactional annotation does not allow the specification of the data source to be used. The current implementation will only work for data source default.

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/rest-client/index.html b/doc/rest-client/index.html
index a9f1927..9f7661c 100644
--- a/doc/rest-client/index.html
+++ b/doc/rest-client/index.html
@@ -1,7 +1,7 @@
 Void Framework – REST Client
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

REST Client

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

REST Client

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/rest-client/retrofit2/index.html b/doc/rest-client/retrofit2/index.html
index 075f788..660b55c 100644
--- a/doc/rest-client/retrofit2/index.html
+++ b/doc/rest-client/retrofit2/index.html
@@ -49,7 +49,7 @@
         return this.echoApiRestClient.echo("Hello World");
     }
 }
-

© 2022-2023 Void Framework

+

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/scheduler/index.html b/doc/scheduler/index.html
index 8cce302..67c976f 100644
--- a/doc/scheduler/index.html
+++ b/doc/scheduler/index.html
@@ -1,7 +1,7 @@
 Void Framework – Scheduler
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Scheduler

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Scheduler

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/scheduler/scheduling-job-cron/index.html b/doc/scheduler/scheduling-job-cron/index.html
index 6819ad8..c675b0c 100644
--- a/doc/scheduler/scheduling-job-cron/index.html
+++ b/doc/scheduler/scheduling-job-cron/index.html
@@ -31,7 +31,7 @@
         LOGGER.info("PING!!");
     }
 }
-

© 2022-2023 Void Framework

+

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/sendmail/index.html b/doc/sendmail/index.html
index b2a7bd7..6ac056f 100644
--- a/doc/sendmail/index.html
+++ b/doc/sendmail/index.html
@@ -1,7 +1,7 @@
 Void Framework – Sendmail
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Sendmail

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Sendmail

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/sendmail/mailer-apache-commons-email/index.html b/doc/sendmail/mailer-apache-commons-email/index.html
index f935364..7369c40 100644
--- a/doc/sendmail/mailer-apache-commons-email/index.html
+++ b/doc/sendmail/mailer-apache-commons-email/index.html
@@ -7,7 +7,7 @@
     <artifactId>voidframework-sendmail-commonsemail</artifactId>
     <version>1.12.0</version>
 </dependency>
-
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.commonsemail.username user name for authentication. The default value is null.
voidframework.sendmail.commonsemail.password password for authentication. The default value is null.
This module also includes many of the configuration keys of the Java Mail properties. To use it, simply prefix them with voidframework.sendmail.commonsemail.. Here is the list of possible properties:
https://javaee.github.io/javamail/docs/api/javax/mail/internet/package-summary.html
mail.mime.address.usecanonicalhostname
mail.mime.allowencodedmessages
mail.mime.applefilenames
mail.mime.base64.ignoreerrors
mail.mime.charset
mail.mime.contenttypehandler
mail.mime.decodefilename
mail.mime.decodeparameters
mail.mime.decodetext.strict
mail.mime.encodeeol.strict
mail.mime.encodefilename
mail.mime.encodeparameters
mail.mime.foldtext
mail.mime.ignoremultipartencoding
mail.mime.ignoreunknownencoding
mail.mime.ignorewhitespacelines
mail.mime.multipart.allowempty
mail.mime.multipart.ignoreexistingboundaryparameter
mail.mime.multipart.ignoremissingboundaryparameter
mail.mime.multipart.ignoremissingendboundary
mail.mime.parameters.strict
mail.mime.setcontenttypefilename
mail.mime.setdefaulttextcharset
mail.mime.uudecode.ignoreerrors
mail.mime.uudecode.ignoremissingbeginend
mail.mime.windowsfilenames
https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html
mail.smtp.user
mail.smtp.host
mail.smtp.port
mail.smtp.connectiontimeout
mail.smtp.timeout
mail.smtp.writetimeout
mail.smtp.from
mail.smtp.localhost
mail.smtp.localaddress
mail.smtp.localport
mail.smtp.ehlo
mail.smtp.auth
mail.smtp.auth.mechanisms
mail.smtp.auth.login.disable
mail.smtp.auth.plain.disable
mail.smtp.auth.digest-md5.disable
mail.smtp.auth.ntlm.disable
mail.smtp.auth.ntlm.domain
mail.smtp.auth.ntlm.flags
mail.smtp.auth.xoauth2.disable
mail.smtp.submitter
mail.smtp.dsn.notify
mail.smtp.dsn.ret
mail.smtp.allow8bitmime
mail.smtp.sendpartial
mail.smtp.sasl.enable
mail.smtp.sasl.mechanisms
mail.smtp.sasl.authorizationid
mail.smtp.sasl.realm
mail.smtp.sasl.usecanonicalhostname
mail.smtp.quitwait
mail.smtp.reportsuccess
mail.smtp.socketFactory
mail.smtp.socketFactory.class
mail.smtp.socketFactory.fallback
mail.smtp.socketFactory.port
mail.smtp.ssl.enable
mail.smtp.ssl.checkserveridentity
mail.smtp.ssl.trust
mail.smtp.ssl.socketFactory
mail.smtp.ssl.socketFactory.class
mail.smtp.ssl.socketFactory.port
mail.smtp.ssl.protocols
mail.smtp.ssl.ciphersuites
mail.smtp.starttls.enable
mail.smtp.starttls.required
mail.smtp.proxy.host
mail.smtp.proxy.port
mail.smtp.proxy.user
mail.smtp.proxy.password
mail.smtp.socks.host
mail.smtp.socks.port
mail.smtp.mailextension
mail.smtp.userset
mail.smtp.noop.strict

© 2022-2023 Void Framework

+
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.ApacheCommonsEmailMailerEngine in your application configuration file.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.sendmail.commonsemail.username user name for authentication. The default value is null.
voidframework.sendmail.commonsemail.password password for authentication. The default value is null.
This module also includes many of the configuration keys of the Java Mail properties. To use it, simply prefix them with voidframework.sendmail.commonsemail.. Here is the list of possible properties:
https://javaee.github.io/javamail/docs/api/javax/mail/internet/package-summary.html
mail.mime.address.usecanonicalhostname
mail.mime.allowencodedmessages
mail.mime.applefilenames
mail.mime.base64.ignoreerrors
mail.mime.charset
mail.mime.contenttypehandler
mail.mime.decodefilename
mail.mime.decodeparameters
mail.mime.decodetext.strict
mail.mime.encodeeol.strict
mail.mime.encodefilename
mail.mime.encodeparameters
mail.mime.foldtext
mail.mime.ignoremultipartencoding
mail.mime.ignoreunknownencoding
mail.mime.ignorewhitespacelines
mail.mime.multipart.allowempty
mail.mime.multipart.ignoreexistingboundaryparameter
mail.mime.multipart.ignoremissingboundaryparameter
mail.mime.multipart.ignoremissingendboundary
mail.mime.parameters.strict
mail.mime.setcontenttypefilename
mail.mime.setdefaulttextcharset
mail.mime.uudecode.ignoreerrors
mail.mime.uudecode.ignoremissingbeginend
mail.mime.windowsfilenames
https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html
mail.smtp.user
mail.smtp.host
mail.smtp.port
mail.smtp.connectiontimeout
mail.smtp.timeout
mail.smtp.writetimeout
mail.smtp.from
mail.smtp.localhost
mail.smtp.localaddress
mail.smtp.localport
mail.smtp.ehlo
mail.smtp.auth
mail.smtp.auth.mechanisms
mail.smtp.auth.login.disable
mail.smtp.auth.plain.disable
mail.smtp.auth.digest-md5.disable
mail.smtp.auth.ntlm.disable
mail.smtp.auth.ntlm.domain
mail.smtp.auth.ntlm.flags
mail.smtp.auth.xoauth2.disable
mail.smtp.submitter
mail.smtp.dsn.notify
mail.smtp.dsn.ret
mail.smtp.allow8bitmime
mail.smtp.sendpartial
mail.smtp.sasl.enable
mail.smtp.sasl.mechanisms
mail.smtp.sasl.authorizationid
mail.smtp.sasl.realm
mail.smtp.sasl.usecanonicalhostname
mail.smtp.quitwait
mail.smtp.reportsuccess
mail.smtp.socketFactory
mail.smtp.socketFactory.class
mail.smtp.socketFactory.fallback
mail.smtp.socketFactory.port
mail.smtp.ssl.enable
mail.smtp.ssl.checkserveridentity
mail.smtp.ssl.trust
mail.smtp.ssl.socketFactory
mail.smtp.ssl.socketFactory.class
mail.smtp.ssl.socketFactory.port
mail.smtp.ssl.protocols
mail.smtp.ssl.ciphersuites
mail.smtp.starttls.enable
mail.smtp.starttls.required
mail.smtp.proxy.host
mail.smtp.proxy.port
mail.smtp.proxy.user
mail.smtp.proxy.password
mail.smtp.socks.host
mail.smtp.socks.port
mail.smtp.mailextension
mail.smtp.userset
mail.smtp.noop.strict

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/sendmail/mailer-dummy/index.html b/doc/sendmail/mailer-dummy/index.html
index 2ce6834..3292ba9 100644
--- a/doc/sendmail/mailer-dummy/index.html
+++ b/doc/sendmail/mailer-dummy/index.html
@@ -2,7 +2,7 @@
 Installation To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframewor">Void Framework – Mailer : Dummy
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Mailer : Dummy
This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.

Installation
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Mailer : Dummy
This implementation is particularly useful locally during development. It simply displays the email in the console rather than sending a real email.

Installation
To enable this mailer, you have to set voidframework.sendmail.engine to dev.voidframework.sendmail.engine.DummyMailerEngine in your application configuration file.

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/sendmail/sending-emails/index.html b/doc/sendmail/sending-emails/index.html
index e72a59a..8d9f0ef 100644
--- a/doc/sendmail/sending-emails/index.html
+++ b/doc/sendmail/sending-emails/index.html
@@ -27,7 +27,7 @@
         sendmail.send(mail);
     }
 }
-

© 2022-2023 Void Framework

+

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/template/freemarker/index.html b/doc/template/freemarker/index.html
index 6630504..b6d0935 100644
--- a/doc/template/freemarker/index.html
+++ b/doc/template/freemarker/index.html
@@ -9,7 +9,7 @@
 </dependency>
 

Templates location
By default, templates should be placed in the resources/views directory.

Configuration
The following configuration keys can be used in the configuration file of your application:
voidframework.template.basePackagePath the location of the templates. The default value is "/views/".

Built-in methods & variables
By default, modules web and template-freemarker provide a set of methods and variables that will be accessible in templates.
Method Description
config Retrieves a value from the configuration
displaySize Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
i18n / _ Translates a message
urlfor Retrieves an URL from the router (reverse router)
Variable Description
isDevMode Indicates whether the application is in dev mode
lang Contains the current language
languages Contains all available languages
voidFrameworkVersion Contains the current Void Framework version
 
 FreeMarker provides a lot of other built-in methods & variables. Read more about FreeMarker
-on the official website.

© 2022-2023 Void Framework

+on the official website.

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/template/index.html b/doc/template/index.html
index 740e8ad..8c8833e 100644
--- a/doc/template/index.html
+++ b/doc/template/index.html
@@ -1,7 +1,7 @@
 Void Framework – Template
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Template

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Template

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/template/using-template/index.html b/doc/template/using-template/index.html
index 387a53f..edc32e8 100644
--- a/doc/template/using-template/index.html
+++ b/doc/template/using-template/index.html
@@ -26,7 +26,7 @@
     }
 }
 
 
-Note that the data Map must be mutable. Internally the different implementations can add other data to it. If you provide a immutable Map, an exception will be thrown.

© 2022-2023 Void Framework

+Note that the data Map must be mutable. Internally the different implementations can add other data to it. If you provide a immutable Map, an exception will be thrown.

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/testing/index.html b/doc/testing/index.html
index 41b4db8..ace3b74 100644
--- a/doc/testing/index.html
+++ b/doc/testing/index.html
@@ -1,7 +1,7 @@
 Void Framework – Testing
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Testing

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Testing

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/testing/junit-extension/index.html b/doc/testing/junit-extension/index.html
index 55de129..085e4a0 100644
--- a/doc/testing/junit-extension/index.html
+++ b/doc/testing/junit-extension/index.html
@@ -30,7 +30,7 @@
         Mockito.verify(myRepository, Mockito.times(1)).findAll();
     }
 }
-

© 2022-2023 Void Framework

+

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/vfs/index.html b/doc/vfs/index.html
index 04839d0..406944b 100644
--- a/doc/vfs/index.html
+++ b/doc/vfs/index.html
@@ -1,7 +1,7 @@
 Void Framework – Virtual File Storage
 Void Framework
Documentation
    
-Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Virtual File Storage

© 2022-2023 Void Framework

+Release notes
Getting Started
Requirements
Creating a new application
Upgrading from old version
Core
Boot sequence
Configuration
Class scanning
Conditional feature
Life cycle
Type conversion
Lang
Relational Databases
Data source
Transactional
Hibernate ORM
jOOQ ORM
H2
NoSQL Databases
Redis
Cache
Using cache
Cache engine : In-memory
Cache engine : Redis
Internationalization
Using internationalization
REST Client
Retrofit 2
Scheduler
Scheduling a local job
Sendmail
Sending emails
Mailer : Dummy
Mailer : Apache Commons Email
Template
Using template
FreeMarker
Virtual File Storage
Using Virtual File Storage
Web
Using Web
Controller
Session
Filters
CSRF
Security headers
Render template
Testing
JUnit's extension
Advanced
Creating Module
Aspect Oriented Programming
reference.conf

Virtual File Storage

© 2022-2024 Void Framework

 Void Framework is released under the MIT License

 
 
diff --git a/doc/vfs/using-vfs/index.html b/doc/vfs/using-vfs/index.html
index ea38fed..4d263d2 100644
--- a/doc/vfs/using-vfs/index.html
+++ b/doc/vfs/using-vfs/index.html
@@ -53,7 +53,7 @@
         return Result.noContent();
     }
 }
-

© 2022-2023 Void Framework

+

Annotation	Description
`@BindClass`	Indicates that an annotated class is a “Bindable”
`@Controller`	Indicates that an annotated class is a “Controller”
`@Repository`	Indicates that an annotated class is a “Repository”
`@Service`	Indicates that an annotated class is a “Service”

Annotation	Description
`@BindClass`	Indicates that an annotated class is a “Bindable”
`@Controller`	Indicates that an annotated class is a “Controller”
`@Repository`	Indicates that an annotated class is a “Repository”
`@Service`	Indicates that an annotated class is a “Service”

Annotation	Description
`@BindClass`	Indicates that an annotated class is a “Bindable”
`@Controller`	Indicates that an annotated class is a “Controller”
`@Repository`	Indicates that an annotated class is a “Repository”
`@Service`	Indicates that an annotated class is a “Service”

Annotation	Description
`@BindClass`	Indicates that an annotated class is a “Bindable”
`@Controller`	Indicates that an annotated class is a “Controller”
`@Repository`	Indicates that an annotated class is a “Repository”
`@Service`	Indicates that an annotated class is a “Service”

Annotation	Description
`@BindClass`	Indicates that an annotated class is a “Bindable”
`@Controller`	Indicates that an annotated class is a “Controller”
`@Repository`	Indicates that an annotated class is a “Repository”
`@Service`	Indicates that an annotated class is a “Service”

Annotation	Description
`@BindClass`	Indicates that an annotated class is a “Bindable”
`@Controller`	Indicates that an annotated class is a “Controller”
`@Repository`	Indicates that an annotated class is a “Repository”
`@Service`	Indicates that an annotated class is a “Service”

Annotation	Description
`@BindClass`	Indicates that an annotated class is a “Bindable”
`@Controller`	Indicates that an annotated class is a “Controller”
`@Repository`	Indicates that an annotated class is a “Repository”
`@Service`	Indicates that an annotated class is a “Service”

Annotation	Description
`@BindClass`	Indicates that an annotated class is a “Bindable”
`@Controller`	Indicates that an annotated class is a “Controller”
`@Repository`	Indicates that an annotated class is a “Repository”
`@Service`	Indicates that an annotated class is a “Service”

Method	Description
`config`	Retrieves a value from the configuration
`displaySize`	Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
`i18n` / `_`	Translates a message
`urlfor`	Retrieves an URL from the router (reverse router)

Variable	Description
`isDevMode`	Indicates whether the application is in dev mode
`lang`	Contains the current language
`languages`	Contains all available languages
`voidFrameworkVersion`	Contains the current Void Framework version

Method	Description
`config`	Retrieves a value from the configuration
`displaySize`	Displays a formatted number with the correct unit (Kio, Mio, Gio, …)
`i18n` / `_`	Translates a message
`urlfor`	Retrieves an URL from the router (reverse router)

Variable	Description
`flash`	Contains temporary messages
`session`	Contains the current session data
`isDevMode`	Indicates whether the application is in dev mode
`lang`	Contains the current language
`languages`	Contains all available languages
`csrfToken`	Contains the CSRF token
`voidFrameworkVersion`	Contains the current Void Framework version

diff --git a/doc/web/controller/index.html b/doc/web/controller/index.html index 5b0f348..c436ab8 100644 --- a/doc/web/controller/index.html +++ b/doc/web/controller/index.html @@ -61,7 +61,7 @@ i18n.getMessage('msg.key', 'var'); i18n.getMessage('msg.key', 'var1', 'var2', /*...*/'varn'); </script> -

New	Ability to retrieve XML body content as Java object
Improved	Cache management : rename the annotation `Cache` to `CacheResult` and add `CacheRemove`
Fixed	Removed I18N reference from Hibernate module
Fixed	`Transactional` annotation : rollback not occur on unchecked exception
Fixed	Routes are randomly sorted

Improved	Change CSRF signature algorithm to HMACSHA256
Fixed	Error 500 CSRF when POST request render template

New	Methods on `Reflection` util class: `getAnnotatedField(Object, Class)` and `getAnnotatedField(Class, Class)`
New	Configuration keys to define number of I/O and Worker threads (Web)
New	Redis (base + cache + healthcheck)
New	CSRF token
Improved	No longer necessary for HealthChecker to be Singleton
Improved	Add cache abstraction helper
Improved	Session signature key configuration is now required
Improved	Rename `ApplicationLauncher` to `VoidApplication`
Improved	Updated version of all dependencies
Fixed	Cookie revocation not working
Fixed	C3P0/HikariCP settings
Fixed	Issue on routes sorting when regex and capture regex are used
Fixed	Assets not found when devMode=false
Fixed	Hibernate : Models not found when application is compiled

New	Add SecurityHeadersFilter
Improved	Force EntityManagerFactory initialization during boot sequence
Improved	Add new Result methods to handle empty content easily
Improved	Updated version of all dependencies

Fix	The "Modules loaded" log is displayed too early
Fix	Remove unused "GlobalFilterDefinition" interface
Improved	Add converter String to Locale (Web). Used to extract Locale from incoming request (route path or query parameter)

Security	Upgrade Undertow version to 2.2.19 (CVE-2022-2053)
New	Add SecurityHeadersFilter
New	Add unit test JUnit extension and annotation
New	Add ability to fetch remote configuration provider & "etcd" remote configuration provider
New	Add "http" remote configuration provider
New	Add CharConstants & StringConstants classes
Improved	Force EntityManagerFactory initialization during boot sequence
Improved	Add new Result methods to handle empty content easily
Improved	Validation constraints can be grouped
Improved	Clean code
Improved	Better boolean support (Freemarker / config)
Improved	Refactoring module "web" (move files, new constant values, unit tests)
Improved	Updated version of all dependencies

Unit	Value	Step Value	Details
Second	0 – 59	1 – 60
Minute	0 – 59	1 – 60
Hour	0 – 23	1 – 24
Day of Month	1 – 31	1 – 32
Month	1 – 12	1 – 13	1: January, 2: February, …, 12: December
Day of Week	0 – 6	1 – 7	0: Sunday, 1: Monday, …, 6: Saturday


`voidframework-cache`	reference.conf
`voidframework-core`	reference.conf
`voidframework-datasource-c3p0`	reference.conf
`voidframework-datasource-hikaricp`	reference.conf
`voidframework-healthcheck`	reference.conf
`voidframework-i18n`	reference.conf
`voidframework-migration-flyway`	reference.conf
`voidframework-persistence-hibernate`	reference.conf
`voidframework-redis`	reference.conf
`voidframework-remoteconf-etcd`	reference.conf
`voidframework-remoteconf-http`	reference.conf
`voidframework-scheduler`	reference.conf
`voidframework-template-freemarker`	reference.conf
`voidframework-validation`	reference.conf
`voidframework-vfs`	reference.conf
`voidframework-web-healthcheck`	reference.conf
`voidframework-web`	reference.conf

Identifier type	Assignable to	Identifier generator annotation
CUID	CUID, String, byte[]	`@CuidGenerator`
UUID	UUID, String, byte[]	`@UuidGenerator`

Security	Upgrade Jackson Databind version to 2.14.0 (CVE-2022-42003)
New	WebSocket support
New	Can configure temporary files location (`voidframework.web.server.tempFileLocation`)
New	Mockito annotation support
New	CUID: a Collision-resistant Unique ID
New	Add `HttpHeaderNames` class
New	Virtual File Storage
New	No HTTP request timeout (`voidframework.web.server.idleTimeout`)
Fixed	The abbreviation of "december" is now correct (scheduler)
Fixed	"Day of Week" and "Month" can't be zero (Scheduler)
Fixed	Redis methods `addInList`, `getFromList` and `decrement` now working correctly
Fixed	Force close all InputStream of uploaded files
Fixed	Can use template-freemarker without web
Improved	Configuration Key/Value from CLI JVM properties (`-D` flag)
Improved	Annotation `@RequestVariable` can now retrieve array
Improved	Move cache annotations to subpackage `annotation`
Improved	Use wrap/unwrap on Memory cache engine
Improved	Updated version of all dependencies
Improved	Redis parameter `connectionTimeout` is now a duration
Improved	Rename all utility classes
Improved	Add new redirection methods on `Result`
Improved	`HttpRequestBodyContent::asRaw` is now an `InputStream`
Improved	`Redis::addInList` now return the current list size
Improved	`ValidationError` is now a record

New	Web module can now respond to requests securely via HTTPS
New	`NotInstance` validation constraint
New	Utility class `DurationUtils`
Improved	Graceful stop timeout is now a duration (with time unit)
Improved	Commercial at "@" constant now available in `CharConstants` and `StringConstants` classes
Improved	Annotation `RequestVariable` can now use fallback value
Improved	Updated version of all dependencies

New	CUID validator
New	Internationalization for JavaScript
New	Conditional feature
Improved	Http Result methods now accept charset
Improved	Rename bindable annotation from `@BindClass` to `@Bindable`
Improved	Clean thread data (Transactional)
Improved	Updated version of all dependencies

Annotation	Description
`@Bindable`
`@Controller`	Indicates that an annotated class is a “Controller”
`@Repository`	Indicates that an annotated class is a “Repository”
`@Service`	Indicates that an annotated class is a “Service”

Security	Upgrade Undertow version to 2.3.5 (CVE-2022-4492)
New	Conditional feature `RunInDevModeConditionalFeature`
New	Sendmail module
New	Sendmail module implementation `Apache Commons Email`
New	Add `@CachePut` annotation
Improved	Javadoc
Improved	HttpClient is now used instead of raw URL connection (Remote Configuration)
Improved	Result: method `badRequest(final String content, final String contentType)`
Improved	Updated version of all dependencies
Fixed	Transactional annotation multiple calls

New	Proxyable interface
New	H2 web console
Improved	Bind automatically interface with single implementation
Improved	Updated version of all dependencies
Fixed	Guice module implementing interface not recognized

New	AspectJ
New	REST client
New	Bucket4J (rate-limiting)
New	Add `ConfigurationUtils` class
Improved	Upgrade dependencies
Improved	New constant value: `CharConstants.TAB` and `StringConstants.TAB`


`voidframework-bucket4j`	reference.conf
`voidframework-cache`	reference.conf
`voidframework-core`	reference.conf
`voidframework-datasource-c3p0`	reference.conf
`voidframework-datasource-hikaricp`	reference.conf
`voidframework-healthcheck`	reference.conf
`voidframework-i18n`	reference.conf
`voidframework-migration-flyway`	reference.conf
`voidframework-persistence-hibernate`	reference.conf
`voidframework-redis`	reference.conf
`voidframework-remoteconf-etcd`	reference.conf
`voidframework-remoteconf-http`	reference.conf
`voidframework-restclient`	reference.conf
`voidframework-scheduler`	reference.conf
`voidframework-sendmail`	reference.conf
`voidframework-sendmail-commonsemail`	reference.conf
`voidframework-template-freemarker`	reference.conf
`voidframework-validation`	reference.conf
`voidframework-vfs`	reference.conf
`voidframework-web-healthcheck`	reference.conf
`voidframework-web`	reference.conf

New	REST Client authentication (API Key, Basic, Bearer)
Improved	New constant values: `CharConstants.EXCLAMATION_MARK`, `CharConstants.PIPE`, `StringConstants.EXCLAMATION_MARK` and `StringConstants.PIPE`
Improved	Upgrade dependencies

New	Add `KryoUtils` class
New	Add new method `ClassResolverUtils::isClassAvailable`
New	Add new Kryo serializers
New	Add `MockitoUtils` class (spy lambda)
Improved	`AbstractCacheEngine` now using `KryoUtils`
Improved	Add `TypedMap` static "constructor" methods
Improved	Redis ACL authentication (username/password)
Improved	Upgrade dependencies
Fixed	Application must shutdown on "start" lifecycle failure
Fixed	H2 web console fail to start because password not encoded

Fixed	Fix SQLDialect detection KO (jOOQ)
Fixed	Fix can't override Hibernate dialect

Cache engine : In-memory

Installation

Configuration

Cache

Using cache

Using Cache with annotations

@CacheRemove

@CacheResult

Example

Using Cache programmatically

Class scanning

Bindable

Bootstrap file generator

Core

Life cycle

@LifeCycleStart

@LifeCycleStop

Example

Type conversion

Using conversion

Creating a new converter

Data source

Configuration

C3P0

HikariCP

Usage

Databases

Hibernate

@Transactional

Exemple

Getting Started

Creating a new application

Maven

Configuration

Web controller

Application launcher

Run your application

Requirements

Verifying and installing Java

Verifying and installing Java

Documentation

Light and modular Framework for Java

1.0.0

Cache engine : In-memory

Installation

Using cache

Using Cache with annotations

@CacheRemove

@CacheResult

Example

Cache engine : In-memory

Installation

Cache engine : In-memory

Installation

Configuration

Cache

Cache

Using cache

Using Cache with annotations

@CacheRemove

@CacheResult

Example

Boot sequence

Class scanning

Class scanning

Bindable

Bootstrap file generator

Core

Core

Life cycle

Life cycle

@LifeCycleStart

@LifeCycleStop

Example

Type conversion

Using conversion

Type conversion

Using conversion

Data source

Configuration

`Cache engine : In-memory`

`Using cache`

`Cache engine : In-memory`

`Cache`

`Using cache`

`Core`

`Type conversion`

`Getting Started`

`Creating a new application`

`Requirements`

`Documentation`

`Cache engine : In-memory`

`Cache`

`Boot sequence`

New	Add `ClassMethodUtils` class
Fixed	Constants `PARENTHESIS_OPEN` and `PARENTHESIS_CLOSE` are no longer inverted
Improved	Error page (dev mode): display filename & partial content
Improved	Upgrade dependencies