Release 6u1 (#580)

* UniversalDaoのページング処理で、件数取得SQLの差し替えかたを追記しました。 (#539) * 件数取得SQLについての記載追加 * ビルドエラー修正 * レビュー指摘修正 * レビュー指摘対応 * レビュー指摘対応 * レビュー指摘対応 * レビュー指摘対応 * レビュー指摘対応 * レビュー指摘対応 * レビュー指摘対応 * レビュー指摘対応 * レビュー指摘対応 * レビュー指摘対応 * レビュー指摘修正 * 件数取得SQLの差し替えかたを英訳しました。 (#540) * ドキュメントの英訳 * レビュー指摘修正 * メッセージング基盤テストシミュレータの実行モジュールの作成手順修正 (#541) * メッセージング基盤テストシミュレータの実行モジュールの作成手順修正(#555) * 画像内の文言修正（WebSphere MQ→IBM MQ）(#555) * メッセージング基盤テストシミュレータサンプルのJavaバージョンについての記載を追加(#555) * IBM MQの利用バージョンを追加(#555) * IBM MQの利用バージョンを追加(#555) * 解説書のリリース情報へ今回リリース分を追加 * リリースノートの前回保存者の削除 * JobOperatorのJavadocリンクが誤っているため修正 * 使用不許可APIチェックツールへのリンクが誤っているため修正 * Bean Validationグループ機能でJavadocへのリンクが誤っているため修正 * Javadocのリンク先がLATEST固定になっていたため修正 * 6のリリースノートを修正 * メッセージング基盤テストシミュレータサンプル（英語版）修正(#555) (#550) * メッセージング基盤テストシミュレータサンプル（英語版）修正(#555) * メッセージング基盤テストシミュレータサンプル（英語版）の画像修正(#555) * メッセージング基盤テストシミュレータサンプル（英語版）の画像修正(#555) * Javadocのリンク先がLATEST固定になっていたため修正 (#551) * WebSphere MQ→IBM MQに文言修正(#552) (#549) * WebSphere MQ→IBM MQに文言修正(#552) * 変更しWebSphere MQ→IBM MQの文言変更に伴う表現の修正(#552) * WebSphere MQ→IBM MQに文言修正(英語版)(#552) * slf4j-nablarch-adaptorで利用するSLF4Jのバージョンアップに伴う変更(#557) (#552) * slf4j-nablarch-adaptorで利用するSLF4Jのバージョンアップに伴う変更(#557) * 互換性のないバージョンのSLF4Jを利用した場合の文言を修正(#557) * Java21で使用する場合のセットアップ方法をドキュメントに追加（日本語のみ） (#555) * Java21で使用する場合のセットアップ方法をドキュメントに追加（日本語のみ） * Java21で使用する場合のセットアップ方法をドキュメントに追加（日本語のみ） * Java21で使用する場合のセットアップ方法の修正 * Java21で使用する場合のセットアップ方法の修正 * Java21で使用する場合のセットアップ方法の追加（英語） (#556) * Java21で使用する場合のセットアップ方法をドキュメントに追加（日本語のみ） * Java21で使用する場合のセットアップ方法をドキュメントに追加（日本語のみ） * Java21で使用する場合のセットアップ方法の修正 * Java21で使用する場合のセットアップ方法の修正 * Java21で使用する場合のセットアップ方法の追加（英語）~ * Java17で使用する場合のセットアップ方法で誤って削除したバージョンの修正（英語） * Java21で使用する場合のセットアップ方法の追加の修正 * Java21で使用する場合のセットアップ方法の追加（日英） (#557) * Java21で使用する場合のセットアップ方法をドキュメントに追加（日本語のみ） * Java21で使用する場合のセットアップ方法の追加(日本語) * Java21で使用する場合のセットアップ方法の追加（英語） * AWSにおける分散トレーシングの依存ライブラリバージョンアップ(#559) (#558) * AWSにおける分散トレーシングの依存ライブラリバージョンアップ(#559) * AWSにおける分散トレーシングのサンプルコード修正(#559) * Java21で使用する場合のセットアップ方法からJacocoのバージョンアップを削除（nablarch-single-module-archetypeで修正したため） (#559) * SLF4J 2.x系へのバージョンアップ対応（テストバージョンの変更） (#560) * ユニバーサルDAOのエンティティ生成機能をDate and Time APIに対応のドキュメントを追加 (#562) * ユニバーサルDAOのエンティティ生成機能をDate and Time APIに対応のドキュメントを追加（日） * ユニバーサルDAOのエンティティ生成機能をDate and Time APIに対応のドキュメントの修正（日） * ユニバーサルDAOのエンティティ生成機能をDate and Time APIに対応のドキュメントの修正（日） * ユニバーサルDAOのエンティティ生成機能をDate and Time APIに対応のドキュメントの修正（英） * HttpRequest#getParam、HttpRequest#getParamMapの利用箇所を修正 (#561) * RESTfulウェブサービスのサンプルを修正 * パスパラメータの定義の実装サンプルを修正 * リクエストパラメータの値を検証の実装サンプルを修正 * RESTfulウェブサービスのサンプルを修正 * RESTfulウェブサービスのサンプルを修正 * ディスパッチされるメソッドが直前にあるコード例と一致してないため修正 * HttpRequestの使用箇所をJaxRsHttpRequestに変更 * restでのHttpRequestの使用に関して注釈を追加 * HttpRequest#getParam、HttpRequest#getParamMapの利用箇所を修正 (#563) * HttpRequest#getParam、HttpRequest#getParamMapの利用箇所を修正 * HttpRequest#getParam、HttpRequest#getParamMapの利用箇所を修正 * HttpRequest#getParam、HttpRequest#getParamMapの利用箇所を修正 * ディスパッチされるメソッドが直前にあるコード例と一致してないため修正 * doc: タイポ修正 (#565) * BeanUtilでレコードを使用する際の解説を追加しました。 (#564) * レコードについての記載追加 * レビュー指摘対応 * レビュー指摘対応 * 文言・助詞の修正 * BeanUtilのレコード対応の記載を英訳しました。 (#566) * 英語に翻訳 * 参照文字列を修正 * ビルドエラー対応 * レビュー指摘対応 * レビュー指摘対応 * レビュー指摘対応 * 表記ゆれの修正 (#567) * MavenプラグインのJVMオプション指定について注意喚起したほうがよいとの指摘に対応 (#570) * Azureのリンク切れ対応のマージ (#573) * 表記ゆれの修正 (#568) * MavenプラグインのJVMオプション指定について注意喚起したほうがよいとの指摘に対応 (#569) * Nab 571/link check (#571) * linkcheckでBrokenのものに対応 * linkcheckでRedirectのものに対応 * javadocのURLをhttpからhttpsに修正 * Nab 571/link check (#572) * linkcheckでBrokenのものに対応 * linkcheckでRedirectのものに対応 * javadocのURLをhttpからhttpsに修正 * linkcheckでBroken、Redirectに対応（英語） * リンク先の英語版ページに変更 --------- Co-authored-by: oguchi-shiori03 <[email protected]> --------- Co-authored-by: Takayuki Uchida <[email protected]> Co-authored-by: tishijiri <[email protected]> Co-authored-by: kankichi00 <[email protected]> * 解説書のリリース情報の記載修正 (#574) * 5系のリリース情報を削除し、5系の最新版リリース情報へのリンクを追加 * 5系のリリース情報を削除 * テスト環境、JDBCのバージョンの更新 (#575) * 解説書で案内しているojdbcのバージョンを更新 * テスト環境の更新 * テスト環境の更新 * リリース情報の追加 (#578) * リリース情報の追加 * リリース情報の追加 * リリース作業：Nablarchバージョンの更新 * 操作ミスによる不要な記号を削除 * waringの解消：<が重なっていたので修正 * releasenote差し替え --------- Co-authored-by: Takayuki Uchida <[email protected]> Co-authored-by: kankichi <[email protected]> Co-authored-by: hijiri <[email protected]> Co-authored-by: kankichi00 <[email protected]> Co-authored-by: Takayuki Uchida <[email protected]> Co-authored-by: tishijiri <[email protected]>
nablarch · Mar 15, 2024 · 80655b7 · 80655b7
1 parent 806085b
commit 80655b7
Show file tree

Hide file tree

Showing 78 changed files with 562 additions and 262 deletions.
diff --git a/en/application_framework/adaptors/jaxrs_adaptor.rst b/en/application_framework/adaptors/jaxrs_adaptor.rst
@@ -19,8 +19,8 @@ Provides the following adapter to use in :ref:`RESTful web service <restful_web_
 
 
 *	Adapter to convert JSON using `Jackson (external site) <https://github.com/FasterXML/jackson>`_
-*	Adapter for using :ref:`RESTful web service <restful_web_service>` with `Jersey (external site) <https://jersey.java.net/>`_
-*	Adapter for using :ref:`RESTful web service <restful_web_service>` with `RESTEasy (external site) <http://resteasy.jboss.org/>`_
+*	Adapter for using :ref:`RESTful web service <restful_web_service>` with `Jersey (external site) <https://eclipse-ee4j.github.io/jersey/>`_
+*	Adapter for using :ref:`RESTful web service <restful_web_service>` with `RESTEasy (external site) <https://resteasy.dev/>`_
 
 Module list
 --------------------------------------------------
@@ -61,7 +61,7 @@ Module list
 
 Using RESTful web services under Jersey environment
 -------------------------------------------------------
-If the implementation of `Jakarta RESTful Web Services(external site) <https://jakarta.ee/specifications/restful-ws/>`_ bundled with the web application server is `Jersey(external site) <https://jersey.java.net/>`_ , use the adapter for Jersey.
+If the implementation of `Jakarta RESTful Web Services(external site) <https://jakarta.ee/specifications/restful-ws/>`_ bundled with the web application server is `Jersey(external site) <https://eclipse-ee4j.github.io/jersey/>`_ , use the adapter for Jersey.
 
 An application of Jersey adapter is shown below.
 
@@ -95,7 +95,7 @@ For :java:extdoc:`JaxRsMethodBinderFactory#setHandlerList <nablarch.fw.jaxrs.Jax
 
 Using RESTful web services under RESTEasy environment
 --------------------------------------------------------
-If the implementation of `Jakarta RESTful Web Services (external site) <https://jakarta.ee/specifications/restful-ws/>`_ bundled with the web application server is `RESTEasy (external site) <http://resteasy.jboss.org/>`_ , use the adapter for RESTEasy.
+If the implementation of `Jakarta RESTful Web Services (external site) <https://jakarta.ee/specifications/restful-ws/>`_ bundled with the web application server is `RESTEasy (external site) <https://resteasy.dev/>`_ , use the adapter for RESTEasy.
 
 An application of RESTEasy adapter is shown below.
 

diff --git a/en/application_framework/adaptors/log_adaptor.rst b/en/application_framework/adaptors/log_adaptor.rst
@@ -12,7 +12,7 @@ When an adapter is used, all log output processing using :ref:`the log output fu
 
 .. important::
 
-  The log4j adapter that was provided up to Nablarch5u15 uses `log4j1.2 (external site) <http://logging.apache.org/log4j/1.2/>`_. log4j 1.2 is EOL.
+  The log4j adapter that was provided up to Nablarch5u15 uses `log4j1.2 (external site) <https://logging.apache.org/log4j/1.x/>`_. log4j 1.2 is EOL.
   Therefore, the log4j adapter has been deprecated as no fix for the `vulnerability <https://jvndb.jvn.jp/ja/contents/2019/JVNDB-2019-013606.html>`_ has been published. Use slf4j or JBoss Logging.
 
 .. tip::
@@ -38,7 +38,7 @@ slf4j
 
 .. tip::
 
-  Tests are conducted using slf4j version 1.7.22. 
+  Tests are conducted using slf4j version 2.0.11. 
   When changing the version, test in the project to confirm that there are no problems.
 
 

diff --git a/en/application_framework/adaptors/micrometer_adaptor.rst b/en/application_framework/adaptors/micrometer_adaptor.rst
@@ -655,11 +655,11 @@ Working with Azure
 How to send metrics to Azure with Micrometer
   Azure provides the library using the Java agent (**Java 3.0 agent**) for sending metrics from Java applications to Azure.
 
-  * `Java codeless application monitoring Azure Monitor Application Insights(external site) <https://docs.microsoft.com/en-us/azure/azure-monitor/app/java-in-process-agent>`_
+  * `Java codeless application monitoring Azure Monitor Application Insights(external site) <https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-enable?tabs=java>`_
 
   The Java 3.0 agent automatically collects metrics output to Micrometer's `Global Registry(external site) <https://micrometer.io/docs/concepts#_global_registry>`_, and sends to Azure.
 
-  * `Send custom telemetry from your application(external site) <https://docs.microsoft.com/en-us/azure/azure-monitor/app/java-in-process-agent#send-custom-telemetry-from-your-application>`_
+  * `Send custom telemetry from your application(external site) <https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-enable?tabs=java>`_
 
   .. important::
     The Java 3.0 agent loads a large number of jar files during the initialization process.
@@ -678,7 +678,7 @@ How to configure Micrometer adaptor
   * Add the Java 3.0 agent to your application's JVM args
   * Define a ``MeterRegistry`` component using the Global Registry
 
-  See the `Azure documentation(external site) <https://docs.microsoft.com/en-us/azure/azure-monitor/app/java-in-process-agent#quickstart>`_ for how to set JVM args.
+  See the `Azure documentation(external site) <https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-enable?tabs=java#modify-your-application>`_ for how to set JVM args.
 
   This adaptor provides :java:extdoc:`GlobalMeterRegistryFactory <nablarch.integration.micrometer.GlobalMeterRegistryFactory>` for factory of Global Registry component.
   The following is an example of a component definition for this factory class.
@@ -701,7 +701,7 @@ Configuration
   The metrics are sent by the Java 3.0 agent provided by Azure.
   Therefore, you must use configuration options provided by the Java 3.0 agent.
 
-  For more information, see `Configuration Options(external site) <https://docs.microsoft.com/en-us/azure/azure-monitor/app/java-standalone-config>`_.
+  For more information, see `Configuration Options(external site) <https://learn.microsoft.com/en-us/azure/azure-monitor/app/java-standalone-config>`_.
 
   .. important::
     The configuration file for this adapter, ``micrometer.properties``, is not used.

diff --git a/en/application_framework/adaptors/router_adaptor.rst b/en/application_framework/adaptors/router_adaptor.rst
@@ -209,7 +209,7 @@ The following is an example implementation that defines the mapping using the ``
 
         @POST
         @Produces(MediaType.APPLICATION_JSON)
-        public int register(HttpRequest request) {
+        public int register(JaxRsHttpRequest request) {
             // Omitted
         }
     }
@@ -224,7 +224,7 @@ In the above example implementation, the HTTP request will be dispatched as foll
 Path         HTTP method    Method of dispatching target
 ============ ============== =============================
 ``/sample``   ``GET``        ``SampleAction#findAll()``
-``/sample``   ``POST``       ``SampleAction#register(HttpRequest)``
+``/sample``   ``POST``       ``SampleAction#register(JaxRsHttpRequest)``
 ============ ============== =============================
 
 .. tip::
@@ -265,8 +265,8 @@ In this case, the dispatch of the HTTP request would be as follows.
 ================ ============== =============================
 Path             HTTP method    Method of dispatching target
 ================ ============== =============================
-``/sample/foo``   ``GET``       ``SampleAction#findAll()``
-``/sample/bar``   ``GET``       ``SampleAction#register(HttpRequest)``
+``/sample/foo``   ``GET``       ``TestAction#foo()``
+``/sample/bar``   ``GET``       ``TestAction#bar()``
 ================ ============== =============================
 
 Definition of path parameters
@@ -281,16 +281,16 @@ Can also include parameters in the path, as follows
         @GET
         @Path("/foo/{param}")
         @Produces(MediaType.APPLICATION_JSON)
-        public Person foo(HttpRequest request) {
-            String param = request.getParam("param")[0];
+        public Person foo(JaxRsHttpRequest request) {
+            String param = request.getPathParam("param");
             // Omitted
         }
 
         @GET
         @Path("/bar/{id : \\d+}")
         @Produces(MediaType.APPLICATION_JSON)
-        public Person bar(HttpRequest request) {
-            int id = Integer.parseInt(request.getParam("id")[0]);
+        public Person bar(JaxRsHttpRequest request) {
+            int id = Integer.parseInt(request.getPathParam("id");
             // Omitted
         }
     }
@@ -299,7 +299,7 @@ Can also include parameters in the path, as follows
 | This is because this feature (routing definition with ``Path`` annotations) follows the Jakarta RESTful Web Services specification.
 
 | By describing a part of the path as ``{parameter name}``, can define that part of the path as a parameter.
-| Can get the value of the path parameter by passing the parameter name defined here to :java:extdoc:`HttpRequest#getParam(String) <nablarch.fw.web.HttpRequest.getParam(java.lang.String)>` .
+| Can get the value of the path parameter by passing the parameter name defined here to :java:extdoc:`JaxRsHttpRequest#getPathParam(String) <nablarch.fw.jaxrs.JaxRsHttpRequest.getPathParam(java.lang.String)>` .
 
 | In addition, can define the format of the path parameter in a regular expression by describing it as ``{parameter name: regular expression}``.
 | In the example implementation above, set the regular expression to ``\\d+``, so the method will be dispatched only if the path value is a number.
@@ -309,10 +309,10 @@ An example of HTTP request dispatch would be as follows.
 ===================== ============== =============================
 Path                  HTTP method    Method of dispatching target
 ===================== ============== =============================
-``/sample/foo/hello`` ``GET``        ``SampleAction#foo(HttpRequest)``
-``/sample/foo/world`` ``GET``        ``SampleAction#foo(HttpRequest)``
-``/sample/bar/123``   ``GET``        ``SampleAction#bar(HttpRequest)``
-``/sample/bar/987``   ``GET``        ``SampleAction#bar(HttpRequest)``
+``/sample/foo/hello`` ``GET``        ``TestAction#foo(JaxRsHttpRequest)``
+``/sample/foo/world`` ``GET``        ``TestAction#foo(JaxRsHttpRequest)``
+``/sample/bar/123``   ``GET``        ``TestAction#bar(JaxRsHttpRequest)``
+``/sample/bar/987``   ``GET``        ``TestAction#bar(JaxRsHttpRequest)``
 ===================== ============== =============================
 
 See the list of routing definitions

diff --git a/en/application_framework/adaptors/slf4j_adaptor.rst b/en/application_framework/adaptors/slf4j_adaptor.rst
@@ -23,8 +23,15 @@ Module list
 
 .. tip::
 
-  Tested with SLF4J 1.7.25.
+  Tested with SLF4J 2.0.11.
   If you change the version, the project should be tested on the project side to make sure it is working.
+  Note that the search method for logging implementation has changed since version 2.0.0 of SLF4J. For example, if an incompatible version 1.7 series is used, the following logs will be output, and no further log output will be performed.
+
+  .. code-block:: none
+
+    SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
+    SLF4J: Defaulting to no-operation (NOP) logger implementation
+    SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.  
 
 Using SLF4J Adapter
 --------------------------------------------------

diff --git a/en/application_framework/adaptors/webspheremq_adaptor.rst b/en/application_framework/adaptors/webspheremq_adaptor.rst
@@ -1,15 +1,15 @@
 .. _webspheremq_adaptor:
 
-IBM WebSphere MQ Adapter
+IBM MQ Adapter
 ==================================================
 
 .. contents:: Table of contents
   :depth: 3
   :local:
 
-Provides an adapter to use `IBM WebSphere MQ (external site) <https://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.pro.doc/q001010_.htm>`_ with :ref:`the MOM messaging function of Nablarch <mom_messaging>` .
+Provides an adapter to use `IBM MQ (external site) <https://www.ibm.com/docs/en/ibm-mq/9.3?topic=mq-about>`_ with :ref:`the MOM messaging function of Nablarch <mom_messaging>` .
 
-Refer to the official Website and manuals of IBM Corporation for the specifications and construction procedures of WebSphere MQ.
+Refer to the official Website and manuals of IBM Corporation for the specifications and construction procedures of IBM MQ.
 
 Module list
 --------------------------------------------------
@@ -22,8 +22,7 @@ Module list
 
 .. important::
 
-  For WebSphere MQ jars, refer to the product manual and add those that are required to the class path.
-  The library included with WebSphere MQ v7.5 is used for testing.
+  The library included with IBM MQ v9.3 is used for testing.
   When changing the version, test in the project to confirm that there are no problems.
 
 Configuration for using this adapter
@@ -37,7 +36,7 @@ A configuration example is shown below.
 
 .. code-block:: xml
 
-  <!-- Provider implementation for IBM WebSphere MQ Adapter- -->
+  <!-- Provider implementation for IBM MQ Adapter- -->
   <component name="wmqMessagingProvider"
       class="nablarch.integration.messaging.wmq.provider.WmqMessagingProvider">
     <!-- See Javadoc for configuration value-->
@@ -54,7 +53,7 @@ A configuration example is shown below.
 
 Use distributed transaction
 --------------------------------------------------
-This adapter includes a function to realize distributed transactions using IBM WebSphere MQ as the transaction manager.
+This adapter includes a function to realize distributed transactions using IBM MQ as the transaction manager.
 
 This function is used to prevent omission and duplicate capture when sending and receiving messages to and from external systems.
 
@@ -120,7 +119,7 @@ A configuration example is shown below.
 
 .. important::
 
-  For using distributed transactions, an XA resource manager has to be configured for WebSphere MQ and authority to the database has to be granted. 
+  For using distributed transactions, an XA resource manager has to be configured for IBM MQ and authority to the database has to be granted. 
   Refer to the manual of the product to be used for the detailed configuration method and necessary authority.
 
 .. |br| raw:: html

diff --git a/en/application_framework/application_framework/blank_project/CustomizeDB.rst b/en/application_framework/application_framework/blank_project/CustomizeDB.rst
@@ -79,7 +79,7 @@ The JDBC driver can be downloaded from the following site on the Internet.
 
   * - IBM DB2 JDBC Driver Versions |br|
       and Downloads - Japan
-    - http://www-01.ibm.com/support/docview.wss?uid=swg21363866 (External site)
+    - https://www.ibm.com/support/pages/db2-jdbc-driver-versions-and-downloads (External site)
 
 An example of the command to register the downloaded JDBC driver to the local Maven repository is shown below.
 
@@ -304,7 +304,7 @@ H2 configuration example (default)
         <dependency>
           <groupId>com.h2database</groupId>
           <artifactId>h2</artifactId>
-          <version>2.1.214</version>
+          <version>2.2.220</version>
           <scope>runtime</scope>
         </dependency>
         <!-- Omitted -->
@@ -325,8 +325,8 @@ Oracle configuration example
         <!-- Omitted -->
         <dependency>
           <groupId>com.oracle.database.jdbc</groupId>
-          <artifactId>ojdbc6</artifactId>
-          <version>11.2.0.4</version>
+          <artifactId>ojdbc11</artifactId>
+          <version>23.2.0.0</version>
           <scope>runtime</scope>
         </dependency>
         <!-- Omitted -->
@@ -348,7 +348,7 @@ PostgreSQL configuration example
         <dependency>
           <groupId>org.postgresql</groupId>
           <artifactId>postgresql</artifactId>
-          <version>9.4.1207</version>
+          <version>42.7.2</version>
           <scope>runtime</scope>
         </dependency>
         <!-- Omitted -->
@@ -368,9 +368,9 @@ DB2 configuration example
       <dependencies>
         <!-- Omitted -->
         <dependency>
-          <groupId>com.ibm</groupId>
-          <artifactId>db2jcc4</artifactId>
-          <version>10.5.0.7</version>
+          <groupId>com.ibm.db2</groupId>
+          <artifactId>jcc</artifactId>
+          <version>11.5.9.0</version>
           <scope>runtime</scope>
         </dependency>
         <!-- Omitted -->
@@ -392,7 +392,7 @@ SQLServer configuration example
         <dependency>
           <groupId>com.microsoft.sqlserver</groupId>
           <artifactId>mssql-jdbc</artifactId>
-          <version>7.4.1.jre8</version>
+          <version>12.6.1.jre11</version>
           <scope>runtime</scope>
         </dependency>
         <!-- Omitted -->
@@ -419,7 +419,7 @@ An example of the dependency element described by default is shown.
     <dependency>
       <groupId>com.h2database</groupId>
       <artifactId>h2</artifactId>
-      <version>2.1.214</version>
+      <version>2.2.220</version>
       <scope>runtime</scope>
     </dependency>
     <!-- Omitted -->

diff --git a/en/application_framework/application_framework/blank_project/FirstStep.rst b/en/application_framework/application_framework/blank_project/FirstStep.rst
@@ -10,6 +10,7 @@ Initial Setup Procedure
    setup_blankProject/setup_Jbatch
    setup_blankProject/setup_NablarchBatch
    setup_blankProject/setup_NablarchBatch_Dbless
+   setup_blankProject/setup_Java21
 
 .. toctree::
    :maxdepth: 1

diff --git a/...amework/application_framework/blank_project/setup_blankProject/setup_Java21.rst b/...amework/application_framework/blank_project/setup_blankProject/setup_Java21.rst
@@ -0,0 +1,37 @@
+.. _setup_blank_project_for_Java21:
+
+----------------------------------------------------------
+How to Setup When Using With Java21
+----------------------------------------------------------
+
+When using blank projects in Java 21, perform the following procedure before communication confirmation of each blank project.
+
+* Change the standard encoding（if you want the standard encoding to be the same execution environment as Java 17 or earlier）
+* Change of Java Version
+
+Change the standard encoding（If you want to make the standard encoding dependent on the execution environment as before Java 17）
+----------------------------------------------------------------------------------------------------------------------------------------------------------
+
+Since Java 18, the standard encoding is UTF-8, making it environment independent. If you want to make the standard encoding dependent on the execution environment as before Java 17, specify the system property as a runtime option for the Java command as shown below.
+
+* ``-Dfile.encoding=COMPAT``
+
+.. tip::
+  When running from Maven, the environment variable `MAVEN_OPTS (external site) <https://maven.apache.org/configure.html#maven_opts-environment-variable>`_ can be used to set the JVM options. However, ``Picked up MAVEN_OPTS: -Dfile.encoding=COMPAT`` is displayed in the log.
+  Please note that the settings for JVM options may differ depending on Maven plugin.(For example, in maven-surefire-plugin that runs the test, it needs to be specified in ``argLine`` in plugin settings in pom.xml)
+
+.. important::
+  The ``-Dfile.encoding=COMPAT`` option is not valid until Java 17, so be careful not to apply this JVM option to previous execution environments.
+
+Change of Java Version
+------------------------------
+
+In a blank project, Java 17 is set as the Java version
+that the source and class files conform to, so change the file as below.
+
+* pom.xml
+
+.. code-block:: xml
+
+    <!-- Change Java version as follows -->
+    <java.version>21</java.version>