From 95633f7cac3675c8acca9b0a95be8c1377482833 Mon Sep 17 00:00:00 2001 From: Hiroko Takamiya Date: Fri, 20 Sep 2024 14:19:18 -0400 Subject: [PATCH 01/24] 24.0.0.9 Japanese translation draft --- posts/2024-09-10-24.0.0.9.adoc | 2 + posts/ja/2024-09-10-24.0.0.9.adoc | 324 ++++++++++++++++++++++++++++++ 2 files changed, 326 insertions(+) create mode 100644 posts/ja/2024-09-10-24.0.0.9.adoc diff --git a/posts/2024-09-10-24.0.0.9.adoc b/posts/2024-09-10-24.0.0.9.adoc index d942b79459..5f11a8da8b 100644 --- a/posts/2024-09-10-24.0.0.9.adoc +++ b/posts/2024-09-10-24.0.0.9.adoc @@ -10,6 +10,8 @@ seo-description: MicroProfile Telemetry standardizes the observability of your J blog_description: MicroProfile Telemetry standardizes the observability of your Java applications by using OpenTelemetry to collect and export logs, metrics, and traces. The release also includes a solution for managing third-party browser cookies and new additions to our versionless features collection. open-graph-image: https://openliberty.io/img/twitter_card.jpg open-graph-image-alt: Open Liberty Logo +- lang: ja + path: /blog/ja/2024/09/10//2024-09-10-24.0.0.9.html --- = Simplify observability with MicroProfile Telemetry 2.0 and more in 24.0.0.9 David Mueller diff --git a/posts/ja/2024-09-10-24.0.0.9.adoc b/posts/ja/2024-09-10-24.0.0.9.adoc new file mode 100644 index 0000000000..52d4a6fe28 --- /dev/null +++ b/posts/ja/2024-09-10-24.0.0.9.adoc @@ -0,0 +1,324 @@ +--- +layout: post +title: 「24.0.0.9 では MicroProfile Telemetry 2.0 で監視を簡素化します」 +# Do NOT change the categories section +categories: blog +author_picture: https://avatars3.githubusercontent.com/dmuelle +author_github: https://github.com/dmuelle +seo-title: 24.0.0.9 の MicroProfile Telemetry 2.0 で監視を簡素化 - OpenLiberty.io +seo-description: MicroProfile Telemetry は、OpenTelemetry を使用してログ、メトリック、トレースを収集およびエクスポートすることで、Java アプリケーションの可観測性を標準化します。このリリースには、サードパーティのブラウザ クッキーを管理するためのソリューションと、バージョンレス機能コレクションへの新機能も含まれています。 +blog_description: MicroProfile Telemetry は、OpenTelemetry を使用してログ、メトリック、トレースを収集およびエクスポートすることで、Java アプリケーションの可観測性を標準化します。このリリースには、サードパーティのブラウザ クッキーを管理するためのソリューションと、バージョンレス機能コレクションへの新機能も含まれています。 +open-graph-image: https://openliberty.io/img/twitter_card.jpg +open-graph-image-alt: Open Liberty Logo +additional_authors: +- name: 高宮 裕子 (翻訳) + github: https://github.com/una-tapa + image: https://avatars0.githubusercontent.com/una-tapa +blog-available-in-languages: +- lang: en + path: /blog/2024/09/10//2024-09-10-24.0.0.9.html +--- += 24.0.0.9 の MicroProfile Telemetry 2.0 などで監視を簡素化 +David Mueller + +:imagesdir: / +:url-prefix: +:url-about: / +//Blank line here is necessary before starting the body of the post. + + +このリリースでは、MicroProfile Telemetry は、OpenTelemetry を使用してログ、メトリック、トレースを収集およびエクスポートすることで、Java アプリケーションの可観測性を標準化します。また、このリリースには、サードパーティのブラウザ クッキーを管理するためのソリューションと、バージョンレス機能コレクションへの新機能も含まれています。 + + +link:{url-about}[Open Liberty] 24.0.0.9では下記のアップデートが追加されました。 + +* <> + + ** <> + + ** <> + +* <> + +* <> + +* <> + +link:https://github.com/OpenLiberty/open-liberty/issues?q=label%3Arelease%3A24009+label%3A%22release+bug%22[24.0.0.9] で修正されたバグの一覧をご覧ください。 + +link:{url-prefix}/blog/?search=release&search!=beta[以前の Open Liberty GA リリースブログ投稿] をチェックしてください。 + + +[#run] + +== 24.0.0.9 を使用してアプリを開発および実行する + +link:{url-prefix}/guides/maven-intro.html[Maven]を使用している場合は、`pom.xml` ファイルに以下を含めます。 + +[source,xml] +---- + + io.openliberty.tools + liberty-maven-plugin + 3.10.3 + +---- + +または、link:{url-prefix}/guides/gradle-intro.html[Gradle] の場合は、`build.gradle` ファイルに次の内容を含めます。 + +[source,gradle] +---- +buildscript { + repositories { + mavenCentral() + } + dependencies { + classpath 'io.openliberty.tools:liberty-gradle-plugin:3.8.3' + } +} +apply plugin: 'liberty' +---- + +または、link:{url-prefix}/docs/latest/container-images.html[コンテナ イメージ] を使用している場合: + +[source] +---- +FROM icr.io/appcafe/open-liberty +---- + +または、link:{url-prefix}/start/[ダウンロード・ページ]をご覧ください。 + +link:https://plugins.jetbrains.com/plugin/14856-liberty-tools[IntelliJ IDEA]、link:https://marketplace.visualstudio.com/items?itemName=Open-Liberty.liberty-dev-vscode-ext[Visual Studio Code]、または link:https://marketplace.eclipse.org/content/liberty-tools[Eclipse IDE]を使用している場合は、オープンソースの link:https://openliberty.io/docs/latest/develop-liberty-tools.html[Liberty 開発者ツール] を活用して、IDE 内から効果的な開発、テスト、デバッグ、アプリケーション管理を行うこともできます。 + +[link=https://stackoverflow.com/tags/open-liberty] +image::img/blog/blog_btn_stack_ja.svg[Ask a question on Stack Overflow, align="center"] + +// // // // DO NOT MODIFY THIS COMMENT BLOCK // // // // +// Blog issue: https://github.com/OpenLiberty/open-liberty/issues/29558 +// Contact/Reviewer: yasmin-aumeeruddy +// // // // // // // // +[#mptelem] +== MicroProfile Telemetry 2.0 でログ、メトリック、トレースを管理します + +このリリースでは、link:{url-prefix}/docs/latest/reference/feature/mpTelemetry-2.0.html[MicroProfile Telemetry 2.0] 機能 (`mpTelemetry-2.0`) により、OpenTelemetryを使用して標準化された方法でログ、メトリクス、トレースを収集およびエクスポートすることで、Javaアプリケーションの可観測性を向上させます。以前のバージョンのMicroProfile Telemetryは、分散トレースのみを管理できました。 + +利用可能な構成プロパティに関する詳細については、link:{url-prefix}/docs/latest/microprofile-config-properties.html#telemetry[MicroProfile Configプロパティ: MicroProfile Telemetry] を参照してください。 + +MicroProfile Telemetryを使用して、標準化された方法でメトリクス、ログ、トレースを管理する方法については、link:{url-prefix}/docs/latest/microprofile-telemetry.html[Enable observability with MicroProfile Telemetry] を参照してください。 + +MicroProfile Telemetry 2.0は最新のOpenTelemetryテクノロジーを提供します。link:{url-prefix}/docs/latest/microprofile-telemetry.html[分散トレース] に加えて、この機能はOpenTelemetryを使用してメトリクスとログを収集およびエクスポートできるようになりました。 管理に関する情報 <> と <> MicroProfile Telemetry を使用する場合は、次のセクションを参照してください。 + +// DO NOT MODIFY THIS LINE. + +// // // // DO NOT MODIFY THIS COMMENT BLOCK // // // // +// Blog issue: https://github.com/OpenLiberty/open-liberty/issues/29563 +// Contact/Reviewer: Channyboy +// // // // // // // // +[#metrics] +=== Liberty メトリックを OpenTelemetry に送信する + +MicroProfile Telemetry 2.0機能 (`mpTelemetry-2.0`) が有効になると、Open Libertyは、link:{url-prefix}/docs/latest/reference/feature/monitor-1.0.html[Performance Monitoring 1.0] 機能 ( `monitor-1.0``) によって収集されたランタイムコンポーネントの統計情報をMicroProfile Telemetry 2.0ランタイムに転送できるようになります。この統計データはテレメトリランタイムでメトリクスとして登録され、OpenTelemetry Protocol (OTLP) と互換性のあるメトリクスコンシューマーに転送され、監視のニーズを満たすことができます。 + + +次のランタイム コンポーネントがサポートされています。 + +* `ThreadPool` +* `Sessions` +* `RequestTiming` +* `ConnectionPool` + +メトリックを収集してエクスポートするには、次のシステム プロパティまたは環境変数を使用して OpenTelemetry を有効にします。 + +* システムプロパティ: `otel.sdk.disabled=false` +* 環境変数: `OTEL_SDK_DISABLED=false` + +構成プロパティは、link:{url-prefix}/docs/latest/external-configuration.html#default[MicroProfile Configで使用可能な構成ソース]のいずれかに設定できます。 + +`mpTelemetry-2.0` 機能と、選択したサポートされているランタイム コンポーネントに関連付けられているすべての機能を有効にします。`mpTelemetry-2.0` 機能により、`monitor-1.0` 機能が自動的に有効になります。 + +たとえば、`ConnectionPool` コンポーネントには次の構成が必要です。 + +[source,xml] +---- + + mpTelemetry-2.0 + jdbc-4.3 + +---- + +デフォルトでは、すべてのOpenTelemetryデータはlink:https://opentelemetry.io/docs/languages/java/exporters/#otlp[OTLP]にエクスポートされます。次のシステムプロパティまたは環境変数を指定することで、別のエクスポーターを設定することができます。 + +* システムプロパティ: `otel.metrics.exporter` +* 環境変数: `OTEL_METRICS_EXPORTER` + +オプションで、メトリック エクスポート間隔構成変数を構成することもできます。値はミリ秒単位で指定され、デフォルトは 60000 (60 秒) です。 + +* システムプロパティ: `otel.metric.export.interval` +* 環境変数: `OTEL_METRIC_EXPORT_INTERVAL` + +使用可能な構成プロパティの詳細については、xref:{url-prefix}/docs/latest/microprofile-config-properties.html#telemetry[MicroProfile Config properties: MicroProfile Telemetry] を参照してください。 + +// DO NOT MODIFY THIS LINE. + + + +// // // // DO NOT MODIFY THIS COMMENT BLOCK // // // // +// Blog issue: https://github.com/OpenLiberty/open-liberty/issues/29551 +// Contact/Reviewer: pgunapal +// // // // // // // // +[#logs] +=== OpenTelemetryにログを送信する + +`mpTelemetry-2.0` 機能では、Open Liberty ランタイム ログ ソース (メッセージ、トレース、ffdcs) と `java.util.logging` (JUL) パッケージを通じて生成されたアプリケーション ログを収集できるようになりました。 + +MicroProfile Telemetry 2.0 機能を有効にしてすべてのログを収集するには、`server.xml` ファイルに次の構成を追加します。 + +[source,xml] +---- + + mpTelemetry-2.0 + + + +---- + +`mpTelemetry` 構成要素または `source` 属性が構成されていない場合、デフォルトで `message` ソースが設定されます。この場合、メッセージのみが収集されます。`source` 属性が空に指定されている場合 (`source=""`)、ログは OpenTelemetry に送信されません。 + +ランタイム レベルのログを収集してエクスポートするには、次のシステム プロパティまたは環境変数を使用して OpenTelemetry を有効にします。 + +* システムプロパティ: `otel.sdk.disabled=false` +* 環境変数: `OTEL_SDK_DISABLED=false` + +構成プロパティは、link:{url-prefix}/docs/latest/external-configuration.html#default[MicroProfile Configで利用可能な構成ソース]のいずれかに設定できます。 + +サーバー内の複数のアプリケーションを個別に構成するには、アプリケーション構成を使用して OpenTelemetry を構成できます。ただし、この方法ではランタイム レベルのログを収集することはできません。 + +デフォルトでは、すべてのOpenTelemetryデータはlink:https://opentelemetry.io/docs/languages/java/exporters/#otlp[OTLP]にエクスポートされます。次のシステムプロパティまたは環境変数を指定することで、別のエクスポーターを設定することができます。 + +* システムプロパティ: `otel.logs.exporter` +* 環境変数: `OTEL_LOGS_EXPORTER` + +使用可能な構成プロパティの詳細については、xref:{url-prefix}/docs/latest/microprofile-config-properties.html#telemetry[MicroProfile Config properties: MicroProfile Telemetry] を参照してください。 + +// DO NOT MODIFY THIS LINE. + +// // // // DO NOT MODIFY THIS COMMENT BLOCK // // // // +// Blog issue: https://github.com/OpenLiberty/open-liberty/issues/28443 +// Contact/Reviewer: volosied +// // // // // // // // +[#cookie] +== CHIPSでサードパーティのCookieを使い続ける + + + +プライバシーを向上させ追跡を減らすために、link:https://developers.google.com/privacy-sandbox/3pcd/[Google Chromeは2025年にサードパーティクッキーを段階的に廃止すると発表しました]。その後、2024年7月22日時点で、link:https://privacysandbox.com/news/privacy-sandbox-update/[Chromeは規制上の懸念から段階的廃止計画を撤回する可能性があると述べました]。代わりに、ユーザーはブラウザでサードパーティクッキーをブロックするオプションを選択できるようになります。サードパーティクッキーを前提に設計されたサイトの一部は、サードパーティクッキーのブロックを選択するブラウザによって正しく動作しなくなることがあります。Chromeは、サイトが影響を受けているかどうかをテストするためのlink:https://developers.google.com/privacy-sandbox/3pcd/prepare/test-for-breakage[ドキュメント]を提供しています。この変更を緩和するためのオプションの1つとして、CHIPS(独立したパーティション状態を持つクッキー)という手法があります。 + + + +まず、サードパーティ (クロスサイト) Cookie に関する背景情報をいくつか紹介します。 + +トップレベル サイト X が iframe などの別のサイト Z を埋め込む場合、埋め込まれたサイト Z によって設定された Cookie は、トップレベル サイト Y など、サイト Z を埋め込む他のサイトと共有される可能性があります。この脆弱性は、Z サイト キーの下の Cookie jar に配置されている Cookie が原因で発生します。このシナリオでは、Cookie が `SameSite=None` としてラベル付けされていると想定しています。これは、Cookie が `Lax` または `Strict` に設定されている場合は共有されないためです。 + +image::/img/blog/cookie1.png[multisite cookie diagram,width=70%,align="center"] + + +Chrome は、制限のあるサードパーティ Cookie の回避策として、Cookie jar を分割する「パーティション化」Cookie 属性を提供します。Cookie は Z サイト キー内に保存されるのではなく、X や Y などのトップレベル サイトの下にもキーが付けられます。このように、X が Z を埋め込み、Y が Z を埋め込む場合、Z の Cookie は X と Y の間で共有されません。 + +image::/img/blog/cookie2.png[partitioned cookie diagram,width=70%,align="center"] + +`Partitioned` 属性を使用して、Cookie をパーティション分割するかどうかを指定できます。Cookie に `SameSite=None` 属性がない場合、これは `Lax` として扱われるため、Chrome および Chromium ベースのブラウザによってブロックされます。 + +パーティション属性の設定はオプトインであり、SameSite 設定とほぼ同じように動作します。`samesite` チャネル設定はすべての Cookie に適用されますが、`httpSession` および `webAppSecurity` 設定はそれぞれの Cookie に適用されます。`httpSession` および `webAppSecurity` 設定はチャネル設定よりも優先されることに注意してください。これら 2 つの属性のデフォルト値は `defer` で、チャネル設定に従うことを意味します。チャネル設定に関しては、デフォルト値は `false` で、`Partitioned` 属性が追加されないことを意味します。 + +`Partitioned` 属性を宣言するために使用する構成に応じて、Liberty は 3 つの属性のいずれかを使用します。 + +次の例は、`server.xml` ファイルの `httpSession` 属性で HTTP セッション クッキーの `cookiePartitioned` 属性を設定する方法を示しています。 + +[source,xml] +---- +` +---- + +次の例は、`server.xml` ファイルの `webAppSecurity` 属性で LTPA および JWT セキュリティ クッキーの `partitionedCookie` 属性を設定する方法を示しています。 + +[source,xml] +---- +` +---- + +次の例は、`server.xml` ファイルの `httpEndpoint` 属性で他の Cookie の `partitioned` 属性を設定する方法を示しています。 + +[source,xml] +---- + + + +---- + + +あるいは、次の 2 つの `HttpServletResponse` API で `Set-Cookie` ヘッダーを使用して `Partitioned` を設定することもできます。 + +* link:https://openliberty.io/docs/latest/reference/javadoc/liberty-jakartaee10-javadoc.html?path=liberty-jakartaee10-javadoc/jakarta/servlet/http/HttpServletResponse.html[HttpServletResponse.setHeader] +* link:https://openliberty.io/docs/latest/reference/javadoc/liberty-jakartaee10-javadoc.html?path=liberty-jakartaee10-javadoc/jakarta/servlet/http/HttpServletResponse.html[HttpServletResponse.addHeader] + +詳しい情報やビジュアル例については、GitHubのlink:https://github.com/privacycg/CHIPS?tab=readme-ov-file#chips-cookies-having-independent-partitioned-state[CHIPS (Cookies Having Independent Partitioned State)] をご覧ください。 + +// DO NOT MODIFY THIS LINE. + + +// // // // DO NOT MODIFY THIS COMMENT BLOCK // // // // +// Blog issue: https://github.com/OpenLiberty/open-liberty/issues/29571 +// Contact/Reviewer: jhanders34 +// // // // // // // // +[#versionless] +== Java / Jakarta EE コンテナ Liberty 機能のバージョンレス機能 + +24.0.0.8 では、Open Liberty にバージョンレス Java EE および Jakarta EE 機能が導入されました。これらの新しいバージョンレス機能により、どの機能バージョンを使用するかを知らなくても、機能を簡単に使用できます。バージョンレス機能の最初のリリースには、特定の Java EE または Jakarta EE コンポーネント仕様の独自の実装を提供できる `Container` 機能は含まれていませんでした。このような機能の例として、`facesContainer-4.0` があります。 + + +24.0.0.9 では、Open Liberty は不足している `Container` 機能に対してバージョンレス機能を追加します。次のバージョンレス機能が追加されました。 + +- `jpaContainer` / `persistenceContainer` +- `jsfContainer` / `facesContainer` +- `jsonbContainer` +- `jsonpコンテナ` + +次の `server.xml` 構成ファイルは、バージョンレス機能 `jpaContainer`、`jsfContainer`、`jsonbContainer`、および `jsonpContainer` を備えた Java EE プラットフォーム `javaee-8.0` を使用します。 + +[source,xml] +---- + + + javaee-8.0 + jpaContainer + jsfContainer + jsonbContainer + jsonpContainer + +---- + +詳細を学び、利用可能なプラットフォームやバージョンレス機能の完全なコレクションについては、link:{url-prefix}/docs/latest/reference/feature/versionless-features.html[Open Liberty ドキュメント]をご覧ください。今後のリリースでは、さらに多くのバージョンレス機能やプラットフォームが登場予定です。 + +// DO NOT MODIFY THIS LINE. + +[#CVEs] +== このリリースでのセキュリティ脆弱性 (CVE) の修正 +[cols="5*"] +|=== +|CVE |CVSS スコア |脆弱性評価 |影響を受けるバージョン |注記 + +|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-50314[CVE-2023-50314] +|5.3 +|Information disclosure +|17.0.0.3 - 24.0.0.8 +| +|=== + +過去のセキュリティ脆弱性修正の一覧については、link:{url-prefix}/docs/latest/security-vulnerabilities.html[セキュリティ脆弱性 (CVE) リスト] を参照してください。 + +== Open Liberty 24.0.0.9 を今すぐ入手 + +Open Liberty 24.0.0.9は、<>のリンクからお試しいただけます。 + From 8e1522274909e901736589c1d77fd3dbd67e93ba Mon Sep 17 00:00:00 2001 From: David Mueller Date: Tue, 8 Oct 2024 09:05:18 -0400 Subject: [PATCH 02/24] fix metadata error 24008-ja --- posts/2024-09-10-24.0.0.9.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/posts/2024-09-10-24.0.0.9.adoc b/posts/2024-09-10-24.0.0.9.adoc index 5f11a8da8b..d5070948a0 100644 --- a/posts/2024-09-10-24.0.0.9.adoc +++ b/posts/2024-09-10-24.0.0.9.adoc @@ -10,6 +10,7 @@ seo-description: MicroProfile Telemetry standardizes the observability of your J blog_description: MicroProfile Telemetry standardizes the observability of your Java applications by using OpenTelemetry to collect and export logs, metrics, and traces. The release also includes a solution for managing third-party browser cookies and new additions to our versionless features collection. open-graph-image: https://openliberty.io/img/twitter_card.jpg open-graph-image-alt: Open Liberty Logo +blog-available-in-languages: - lang: ja path: /blog/ja/2024/09/10//2024-09-10-24.0.0.9.html --- From 580ca89b60c4f7ec8691162e0634eb75c1b768fd Mon Sep 17 00:00:00 2001 From: David Mueller Date: Tue, 8 Oct 2024 10:28:30 -0400 Subject: [PATCH 03/24] Update 2024-09-10-24.0.0.9.adoc --- posts/2024-09-10-24.0.0.9.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2024-09-10-24.0.0.9.adoc b/posts/2024-09-10-24.0.0.9.adoc index d5070948a0..bf9f126d02 100644 --- a/posts/2024-09-10-24.0.0.9.adoc +++ b/posts/2024-09-10-24.0.0.9.adoc @@ -12,7 +12,7 @@ open-graph-image: https://openliberty.io/img/twitter_card.jpg open-graph-image-alt: Open Liberty Logo blog-available-in-languages: - lang: ja - path: /blog/ja/2024/09/10//2024-09-10-24.0.0.9.html + path: /ja/blog/2024/09/10/24.0.0.9.html --- = Simplify observability with MicroProfile Telemetry 2.0 and more in 24.0.0.9 David Mueller From 0eb316bf95f2207d5f1036a9928bf35a33df5abe Mon Sep 17 00:00:00 2001 From: David Mueller Date: Tue, 8 Oct 2024 12:01:40 -0400 Subject: [PATCH 04/24] Update 2024-09-10-24.0.0.9.adoc --- posts/ja/2024-09-10-24.0.0.9.adoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/posts/ja/2024-09-10-24.0.0.9.adoc b/posts/ja/2024-09-10-24.0.0.9.adoc index 52d4a6fe28..58cc547bb0 100644 --- a/posts/ja/2024-09-10-24.0.0.9.adoc +++ b/posts/ja/2024-09-10-24.0.0.9.adoc @@ -10,13 +10,13 @@ seo-description: MicroProfile Telemetry は、OpenTelemetry を使用してロ blog_description: MicroProfile Telemetry は、OpenTelemetry を使用してログ、メトリック、トレースを収集およびエクスポートすることで、Java アプリケーションの可観測性を標準化します。このリリースには、サードパーティのブラウザ クッキーを管理するためのソリューションと、バージョンレス機能コレクションへの新機能も含まれています。 open-graph-image: https://openliberty.io/img/twitter_card.jpg open-graph-image-alt: Open Liberty Logo -additional_authors: +additional_authors: - name: 高宮 裕子 (翻訳) github: https://github.com/una-tapa image: https://avatars0.githubusercontent.com/una-tapa blog-available-in-languages: - lang: en - path: /blog/2024/09/10//2024-09-10-24.0.0.9.html + path: /blog/2024/09/10/24.0.0.9.html --- = 24.0.0.9 の MicroProfile Telemetry 2.0 などで監視を簡素化 David Mueller @@ -321,4 +321,3 @@ image::/img/blog/cookie2.png[partitioned cookie diagram,width=70%,align="center" == Open Liberty 24.0.0.9 を今すぐ入手 Open Liberty 24.0.0.9は、<>のリンクからお試しいただけます。 - From 153277a5e0b92d57370f4b73f9baaebac2d40a2c Mon Sep 17 00:00:00 2001 From: Hiroko Takamiya Date: Thu, 7 Nov 2024 08:09:47 -0500 Subject: [PATCH 05/24] Incorporate Miyuka's review comments --- posts/ja/2024-09-10-24.0.0.9.adoc | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/posts/ja/2024-09-10-24.0.0.9.adoc b/posts/ja/2024-09-10-24.0.0.9.adoc index 58cc547bb0..fa8f8e5d7f 100644 --- a/posts/ja/2024-09-10-24.0.0.9.adoc +++ b/posts/ja/2024-09-10-24.0.0.9.adoc @@ -6,8 +6,8 @@ categories: blog author_picture: https://avatars3.githubusercontent.com/dmuelle author_github: https://github.com/dmuelle seo-title: 24.0.0.9 の MicroProfile Telemetry 2.0 で監視を簡素化 - OpenLiberty.io -seo-description: MicroProfile Telemetry は、OpenTelemetry を使用してログ、メトリック、トレースを収集およびエクスポートすることで、Java アプリケーションの可観測性を標準化します。このリリースには、サードパーティのブラウザ クッキーを管理するためのソリューションと、バージョンレス機能コレクションへの新機能も含まれています。 -blog_description: MicroProfile Telemetry は、OpenTelemetry を使用してログ、メトリック、トレースを収集およびエクスポートすることで、Java アプリケーションの可観測性を標準化します。このリリースには、サードパーティのブラウザ クッキーを管理するためのソリューションと、バージョンレス機能コレクションへの新機能も含まれています。 +seo-description: MicroProfile Telemetry は、OpenTelemetry を使用してログ、メトリック、トレースを収集およびエクスポートすることで、Java アプリケーションの可観測性を標準化します。このリリースには、サードパーティのブラウザ Cookieを管理するためのソリューションと、バージョンレス機能コレクションへの新機能も含まれています。 +blog_description: MicroProfile Telemetry は、OpenTelemetry を使用してログ、メトリック、トレースを収集およびエクスポートすることで、Java アプリケーションの可観測性を標準化します。このリリースには、サードパーティのブラウザ Cookieを管理するためのソリューションと、バージョンレス機能コレクションへの新機能も含まれています。 open-graph-image: https://openliberty.io/img/twitter_card.jpg open-graph-image-alt: Open Liberty Logo additional_authors: @@ -27,7 +27,7 @@ David Mueller //Blank line here is necessary before starting the body of the post. -このリリースでは、MicroProfile Telemetry は、OpenTelemetry を使用してログ、メトリック、トレースを収集およびエクスポートすることで、Java アプリケーションの可観測性を標準化します。また、このリリースには、サードパーティのブラウザ クッキーを管理するためのソリューションと、バージョンレス機能コレクションへの新機能も含まれています。 +このリリースでは、MicroProfile Telemetry は、OpenTelemetry を使用してログ、メトリック、トレースを収集およびエクスポートすることで、Java アプリケーションの可観測性を標準化します。また、このリリースには、サードパーティのブラウザ Cookieを管理するためのソリューションと、バージョンレス機能コレクションへの新機能も含まれています。 link:{url-about}[Open Liberty] 24.0.0.9では下記のアップデートが追加されました。 @@ -106,7 +106,7 @@ image::img/blog/blog_btn_stack_ja.svg[Ask a question on Stack Overflow, align="c MicroProfile Telemetryを使用して、標準化された方法でメトリクス、ログ、トレースを管理する方法については、link:{url-prefix}/docs/latest/microprofile-telemetry.html[Enable observability with MicroProfile Telemetry] を参照してください。 -MicroProfile Telemetry 2.0は最新のOpenTelemetryテクノロジーを提供します。link:{url-prefix}/docs/latest/microprofile-telemetry.html[分散トレース] に加えて、この機能はOpenTelemetryを使用してメトリクスとログを収集およびエクスポートできるようになりました。 管理に関する情報 <> と <> MicroProfile Telemetry を使用する場合は、次のセクションを参照してください。 +MicroProfile Telemetry 2.0は最新のOpenTelemetryテクノロジーを提供します。link:{url-prefix}/docs/latest/microprofile-telemetry.html[分散トレース] に加えて、この機能はOpenTelemetryを使用してメトリクスとログを収集およびエクスポートできるようになりました。 MicroProfile Telemetry を使用した<> と <> の管理については、次のセクションを参照してください。 // DO NOT MODIFY THIS LINE. @@ -211,7 +211,7 @@ MicroProfile Telemetry 2.0 機能を有効にしてすべてのログを収集 -プライバシーを向上させ追跡を減らすために、link:https://developers.google.com/privacy-sandbox/3pcd/[Google Chromeは2025年にサードパーティクッキーを段階的に廃止すると発表しました]。その後、2024年7月22日時点で、link:https://privacysandbox.com/news/privacy-sandbox-update/[Chromeは規制上の懸念から段階的廃止計画を撤回する可能性があると述べました]。代わりに、ユーザーはブラウザでサードパーティクッキーをブロックするオプションを選択できるようになります。サードパーティクッキーを前提に設計されたサイトの一部は、サードパーティクッキーのブロックを選択するブラウザによって正しく動作しなくなることがあります。Chromeは、サイトが影響を受けているかどうかをテストするためのlink:https://developers.google.com/privacy-sandbox/3pcd/prepare/test-for-breakage[ドキュメント]を提供しています。この変更を緩和するためのオプションの1つとして、CHIPS(独立したパーティション状態を持つクッキー)という手法があります。 +プライバシーを向上させ追跡を減らすために、link:https://developers.google.com/privacy-sandbox/3pcd/[Google Chromeは2025年にサードパーティCookieを段階的に廃止すると発表しました]。その後、2024年7月22日時点で、link:https://privacysandbox.com/news/privacy-sandbox-update/[Chromeは規制上の懸念から段階的廃止計画を撤回する可能性があると述べました]。代わりに、ユーザーはブラウザでサードパーティCookieをブロックするオプションを選択できるようになります。サードパーティCookieを前提に設計されたサイトの一部は、サードパーティCookieのブロックを選択するブラウザによって正しく動作しなくなることがあります。Chromeは、サイトが影響を受けているかどうかをテストするためのlink:https://developers.google.com/privacy-sandbox/3pcd/prepare/test-for-breakage[ドキュメント]を提供しています。この変更を緩和するためのオプションの1つとして、CHIPS(独立したパーティション状態を持つCookie)という手法があります。 @@ -232,14 +232,14 @@ image::/img/blog/cookie2.png[partitioned cookie diagram,width=70%,align="center" `Partitioned` 属性を宣言するために使用する構成に応じて、Liberty は 3 つの属性のいずれかを使用します。 -次の例は、`server.xml` ファイルの `httpSession` 属性で HTTP セッション クッキーの `cookiePartitioned` 属性を設定する方法を示しています。 +次の例は、`server.xml` ファイルの `httpSession` 属性で HTTP セッション Cookieの `cookiePartitioned` 属性を設定する方法を示しています。 [source,xml] ---- ` ---- -次の例は、`server.xml` ファイルの `webAppSecurity` 属性で LTPA および JWT セキュリティ クッキーの `partitionedCookie` 属性を設定する方法を示しています。 +次の例は、`server.xml` ファイルの `webAppSecurity` 属性で LTPA および JWT セキュリティ Cookieの `partitionedCookie` 属性を設定する方法を示しています。 [source,xml] ---- @@ -283,7 +283,7 @@ image::/img/blog/cookie2.png[partitioned cookie diagram,width=70%,align="center" - `jpaContainer` / `persistenceContainer` - `jsfContainer` / `facesContainer` - `jsonbContainer` -- `jsonpコンテナ` +- `jsonpContainer` 次の `server.xml` 構成ファイルは、バージョンレス機能 `jpaContainer`、`jsfContainer`、`jsonbContainer`、および `jsonpContainer` を備えた Java EE プラットフォーム `javaee-8.0` を使用します。 From 439dbdf300968614a92a9e0865df8b768eb2275e Mon Sep 17 00:00:00 2001 From: dmuelle Date: Tue, 12 Nov 2024 13:40:59 +0000 Subject: [PATCH 06/24] 24.0.0.12-beta --- posts/2024-11-19-24.0.0.12-beta.adoc | 303 +++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 posts/2024-11-19-24.0.0.12-beta.adoc diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc new file mode 100644 index 0000000000..1412022fd8 --- /dev/null +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -0,0 +1,303 @@ +--- +layout: post +title: "TITLE" +# Do NOT change the categories section +categories: blog +author_picture: https://avatars3.githubusercontent.com/dmuelle +author_github: https://github.com/dmuelle +seo-title: TITLE - makes sure it ends with - OpenLiberty.io +seo-description: DESCRIPTION +blog_description: DESCRIPTION +open-graph-image: https://openliberty.io/img/twitter_card.jpg +open-graph-image-alt: Open Liberty Logo +--- += TITLE +David Mueller +:imagesdir: / +:url-prefix: +:url-about: / +//Blank line here is necessary before starting the body of the post. + +// // // // // // // // +// In the preceding section: +// Do not insert any blank lines between any of the lines. +// Do not remove or edit the variables on the lines beneath the author name. +// +// "open-graph-image" is set to OL logo. Whenever possible update this to a more appropriate/specific image (For example if present an image that is being used in the post). However, it +// can be left empty which will set it to the default +// +// "open-graph-image-alt" is a description of what is in the image (not a caption). When changing "open-graph-image" to +// a custom picture, you must provide a custom string for "open-graph-image-alt". +// +// Replace TITLE with the blog post title eg: MicroProfile 3.3 is now available on Open Liberty 20.0.0.4 +// Replace dmuelle with your GitHub username eg: lauracowen +// Replace DESCRIPTION with a short summary (~60 words) of the release (a more succinct version of the first paragraph of the post). +// Replace David Mueller with your name as you'd like it to be displayed, +// eg: LauraCowen +// +// For every link starting with "https://openliberty.io" in the post make sure to use +// {url-prefix}. e.g- link:{url-prefix}/guides/GUIDENAME[GUIDENAME]: +// +// If adding image into the post add : +// ------------------------- +// [.img_border_light] +// image::img/blog/FILE_NAME[IMAGE CAPTION ,width=70%,align="center"] +// ------------------------- +// "[.img_border_light]" = This adds a faint grey border around the image to make its edges sharper. Use it around screenshots but not +// around diagrams. Then double check how it looks. +// There is also a "[.img_border_dark]" class which tends to work best with screenshots that are taken on dark backgrounds. +// Change "FILE_NAME" to the name of the image file. Also make sure to put the image into the right folder which is: img/blog +// change the "IMAGE CAPTION" to a couple words of what the image is +// // // // // // // // + +BETA_RELEASE_SUMMARY + +// // // // // // // // +// Change the RELEASE_SUMMARY to an introductory paragraph. This sentence is really +// important because it is supposed to grab the readers attention. Make sure to keep the blank lines +// +// Throughout the doc, replace 24.0.0.12-beta with the version number of Open Liberty, eg: 22.0.0.2-beta +// // // // // // // // + +The link:{url-about}[Open Liberty] 24.0.0.12-beta includes the following beta features (along with link:{url-prefix}/docs/latest/reference/feature/feature-overview.html[all GA features]): + +* <> + +// // // // // // // // +// In the preceding section: +// Change SUB_FEATURE_TITLE to the feature that is included in this release and +// change the SUB_TAG_1/2/3 to the heading tags +// +// However if there's only 1 new feature, delete the previous section and change it to the following sentence: +// "The link:{url-about}[Open Liberty] 24.0.0.12-beta includes SUB_FEATURE_TITLE" +// // // // // // // // + +See also link:{url-prefix}/blog/?search=beta&key=tag[previous Open Liberty beta blog posts]. + +// // // // DO NOT MODIFY THIS COMMENT BLOCK // // // // +// Blog issue: https://github.com/OpenLiberty/open-liberty/issues/29770 +// Contact/Reviewer: neuwerk +// // // // // // // // +[#SUB_TAG_0] +== Fine tuning XML Web Services inbound SOAP Meessage validation. + +Please provide a summary of the update, including the following points: + + - A sentence or two that introduces the update to someone new to the general technology/concept. + +XML Web Services features on Open Liberty now support fine tuning message validation of inbound SOAP messages. In XML Web Services there's more than one flavor of message validation, and so we've introduced new server.xml configuration to support them. These options allow users to enable full XML Schema Validation, enable or disable XML Binding's (JAXB) Default validation, or to keep Default Validation enabled while ignoring only `UnmarshallExceptions: Unknown Element` errors + + - The Human-readable name and short feature name for your feature- eg WebSockets feature (websockets-1.0). + +jaxws-2.2, xmlWS-3.0, xmlWS-4.0 + + - Who is the target persona? Who do you expect to use the update? eg application developer, operations. + + +XML Schema Validation - Application Developer, Operations + +Default Validation - Operations + +Ignore Unexpected Elements - Operations + + + - What was the problem before and how does your update make their life better? (Why should they care?) + +XML Schema Validation: + +This has never been configurable on Liberty, and has never been enabled. Now with thanks to the `enableSchemaValidation=true` property a developer or admin can set this option to provide more insight into JAXB unmarshalling exceptions and making that painful message debugging easier. This is the highest level of XML validation, and therefor comes with a tradeoff - faster debugging and the most thorough checks on inbound message contents but with the higher performance cost. + +Default Validation - + +JAXB's default validation of inbound SOAP Messages is now configurable with the `enableDefaultValidation=true` property. Depending on whether your application is a XML Web Services Client or Web Service, Liberty either enables or disables default validation. Default validation is much more efficient then XML Schema Validation, so enabling will allow basic message validation with a lower overhead, while disabling it will allow users to ignore various Unmarshalling errors for problematic messages. + +Ignore Unexpected Elements - + +In traditional WebSphere, a user could configure a JVM property `com.ibm.ws.webservices.ignoreUnknownElements=true` to have the runtime ignore all Unknown Elements during JAXB Unmarshalling. The new Open Liberty configuration, `ignoreUnexpectedElements`. allows users to do the same. Its not unusual for a inbound SOAP Message to contain extra elements in the SOAP body when a Web Service has been updated but the client has not. When a message contains an unknown element, Open Liberty will throw a `UnmarshallingException: Unknown Element`. By enabling `ignoreUnkownEllements` a user can keep Validation enabled while ignoring unknown elements. + + - Briefly explain how to make your update work. Include screenshots, diagrams, and/or code snippets, and provide a `server.xml` snippet. + +Each configuration requires the one of the XML Web Services features enabled on your server.xml, additionally the configuration can be applied to Web Services or Web Service Clients. Each configuration can be applied globally, or to a individual Client or Web Service implementation. The following examples show how to enable each option, to disable any of these options, set the corresponding properties to `false` + +# Web Service Client configuration: + +## Global XML Schema Validation: + +`` + +## Targeted XML Schema Validation: + +`` + +The `Client Service Name` will be the name of your XML Web Service Client. This name comes from your `@WebServiceClient(serviceName=` annotated stub class for managed clients, or for unmanaged clients you can check the line in your WSDL file ``. For example, if the name of your Client is `SayHelloService` then the matching `serviceName` would be set to: + + +`` + +## Global Default Validation: + + +`` + +## Targeted Default Validation: + + +`` + +## Global Ignore Unexpected Elements: + + +`` + +## Targeted Ignore Unexpected Elements: + + +`` + + +# Web Service configuration: + +XML Schema Validation: + +`` + +Targeted XML Schema Validation: + + +`` + +The `Web Service Port Name` will be the port name of the individual Web Service implementation. This name comes from your `@WebService(portName=` annotated class, alternatively you can check the line in your WSDL file + `` for the port name. For example, if the name of your port name is `SimpleEchoPort` then the matching `portName` would be set to: + + +`` + +Global Default Validation: + + +`` + +Targeted Default Validation: + + +`` + + +Global Ignore Unexpected Elements: + + +`` + +Targeted Ignore Unexpected Elements: + + +`` + + - Where can they find out more about this specific update (eg Open Liberty docs, Javadoc) and/or the wider technology? + +More info can be found: + + +// DO NOT MODIFY THIS LINE. + + + +To enable the new beta features in your app, add them to your `server.xml`: + +[source, xml] +---- + +---- + +[#run] +=== Try it now + +To try out these features, update your build tools to pull the Open Liberty All Beta Features package instead of the main release. The beta works with Java SE 21, Java SE 17, Java SE 11, and Java SE 8. +// // // // // // // // +// In the preceding section: +// Check if a new non-LTS Java SE version is supported that needs to be added to the list (21, 17, 11, and 8 are LTS and will remain for a while) +// https://openliberty.io/docs/latest/java-se.html +// +// In the following section: +// Check if a new MicroProfile or Jakarta version is in beta that could replace the example values in the codeblock +// // // // // // // // + +If you're using link:{url-prefix}/guides/maven-intro.html[Maven], you can install the All Beta Features package using: + +[source,xml] +---- + + io.openliberty.tools + liberty-maven-plugin + 3.8.2 + + + io.openliberty.beta + openliberty-runtime + 24.0.0.12-beta + zip + + + +---- + +You must also add dependencies to your pom.xml file for the beta version of the APIs that are associated with the beta features that you want to try. For example, the following block adds dependencies for two example beta APIs: + +[source,xml] +---- + + org.example.spec + exampleApi + 7.0 + pom + provided + + + example.platform + example.example-api + 11.0.0 + provided + +---- + +Or for link:{url-prefix}/guides/gradle-intro.html[Gradle]: + +[source,gradle] +---- +buildscript { + repositories { + mavenCentral() + } + dependencies { + classpath 'io.openliberty.tools:liberty-gradle-plugin:3.6.2' + } +} +apply plugin: 'liberty' +dependencies { + libertyRuntime group: 'io.openliberty.beta', name: 'openliberty-runtime', version: '[24.0.0.12-beta,)' +} +---- +// // // // // // // // +// In the preceding section: +// Replace the Maven `3.8.2` with the latest version of the plugin: https://search.maven.org/artifact/io.openliberty.tools/liberty-maven-plugin +// Replace the Gradle `3.6.2` with the latest version of the plugin: https://search.maven.org/artifact/io.openliberty.tools/liberty-gradle-plugin +// TODO: Update GHA to automatically do the above. If the maven.org is problematic, then could fallback to using the GH Releases for the plugins +// // // // // // // // + +Or if you're using link:{url-prefix}/docs/latest/container-images.html[container images]: + +[source] +---- +FROM icr.io/appcafe/open-liberty:beta +---- + +Or take a look at our link:{url-prefix}/downloads/#runtime_betas[Downloads page]. + +If you're using link:https://plugins.jetbrains.com/plugin/14856-liberty-tools[IntelliJ IDEA], link:https://marketplace.visualstudio.com/items?itemName=Open-Liberty.liberty-dev-vscode-ext[Visual Studio Code] or link:https://marketplace.eclipse.org/content/liberty-tools[Eclipse IDE], you can also take advantage of our open source link:https://openliberty.io/docs/latest/develop-liberty-tools.html[Liberty developer tools] to enable effective development, testing, debugging and application management all from within your IDE. + +For more information on using a beta release, refer to the link:{url-prefix}docs/latest/installing-open-liberty-betas.html[Installing Open Liberty beta releases] documentation. + +[#feedback] +== We welcome your feedback + +Let us know what you think on link:https://groups.io/g/openliberty[our mailing list]. If you hit a problem, link:https://stackoverflow.com/questions/tagged/open-liberty[post a question on StackOverflow]. If you hit a bug, link:https://github.com/OpenLiberty/open-liberty/issues[please raise an issue]. From a39cec0c4a6c2bea379048ef49f7ec4dbf4ba95b Mon Sep 17 00:00:00 2001 From: David Mueller Date: Tue, 12 Nov 2024 11:08:52 -0500 Subject: [PATCH 07/24] Update 2024-11-19-24.0.0.12-beta.adoc --- posts/2024-11-19-24.0.0.12-beta.adoc | 313 ++++++++++----------------- 1 file changed, 117 insertions(+), 196 deletions(-) diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc index 1412022fd8..0db009380a 100644 --- a/posts/2024-11-19-24.0.0.12-beta.adoc +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -1,218 +1,145 @@ --- layout: post -title: "TITLE" +title: "Enhanced message validation for XML Web Services in 24.0.0.12-beta" # Do NOT change the categories section categories: blog author_picture: https://avatars3.githubusercontent.com/dmuelle author_github: https://github.com/dmuelle -seo-title: TITLE - makes sure it ends with - OpenLiberty.io -seo-description: DESCRIPTION -blog_description: DESCRIPTION +seo-title: Enhanced message validation for XML Web Services in 24.0.0.12-beta - OpenLiberty.io +seo-description: The 24.0.0.12-beta release enhances inbound SOAP message validation in XML Web Services to simplify message debugging and make your web services and clients more resilient during updates. +blog_description: The 24.0.0.12-beta release enhances inbound SOAP message validation in XML Web Services to simplify message debugging and make your web services and clients more resilient during updates. open-graph-image: https://openliberty.io/img/twitter_card.jpg open-graph-image-alt: Open Liberty Logo --- -= TITLE += Enhanced message validation for XML Web Services in 24.0.0.12-beta David Mueller :imagesdir: / :url-prefix: :url-about: / -//Blank line here is necessary before starting the body of the post. -// // // // // // // // -// In the preceding section: -// Do not insert any blank lines between any of the lines. -// Do not remove or edit the variables on the lines beneath the author name. -// -// "open-graph-image" is set to OL logo. Whenever possible update this to a more appropriate/specific image (For example if present an image that is being used in the post). However, it -// can be left empty which will set it to the default -// -// "open-graph-image-alt" is a description of what is in the image (not a caption). When changing "open-graph-image" to -// a custom picture, you must provide a custom string for "open-graph-image-alt". -// -// Replace TITLE with the blog post title eg: MicroProfile 3.3 is now available on Open Liberty 20.0.0.4 -// Replace dmuelle with your GitHub username eg: lauracowen -// Replace DESCRIPTION with a short summary (~60 words) of the release (a more succinct version of the first paragraph of the post). -// Replace David Mueller with your name as you'd like it to be displayed, -// eg: LauraCowen -// -// For every link starting with "https://openliberty.io" in the post make sure to use -// {url-prefix}. e.g- link:{url-prefix}/guides/GUIDENAME[GUIDENAME]: -// -// If adding image into the post add : -// ------------------------- -// [.img_border_light] -// image::img/blog/FILE_NAME[IMAGE CAPTION ,width=70%,align="center"] -// ------------------------- -// "[.img_border_light]" = This adds a faint grey border around the image to make its edges sharper. Use it around screenshots but not -// around diagrams. Then double check how it looks. -// There is also a "[.img_border_dark]" class which tends to work best with screenshots that are taken on dark backgrounds. -// Change "FILE_NAME" to the name of the image file. Also make sure to put the image into the right folder which is: img/blog -// change the "IMAGE CAPTION" to a couple words of what the image is -// // // // // // // // +The 24.0.0.12-beta release enhances inbound SOAP message validation in XML Web Services to simplify message debugging and make your web services and clients more resilient during updates. -BETA_RELEASE_SUMMARY +See also link:{url-prefix}/blog/?search=beta&key=tag[previous Open Liberty beta blog posts]. + +// // // // DO NOT MODIFY THIS COMMENT BLOCK // // // // +// Blog issue: https://github.com/OpenLiberty/open-liberty/issues/29770 +// Contact/Reviewer: neuwerk // // // // // // // // -// Change the RELEASE_SUMMARY to an introductory paragraph. This sentence is really -// important because it is supposed to grab the readers attention. Make sure to keep the blank lines -// -// Throughout the doc, replace 24.0.0.12-beta with the version number of Open Liberty, eg: 22.0.0.2-beta -// // // // // // // // +[#xmlws] +== Fine-tuning XML Web Services inbound SOAP message validation -The link:{url-about}[Open Liberty] 24.0.0.12-beta includes the following beta features (along with link:{url-prefix}/docs/latest/reference/feature/feature-overview.html[all GA features]): +XML Web Services features on Open Liberty now support fine-tuned message validation for inbound SOAP messages. XML Web Services provide various options for message validation. In 24.0.0.12-beta, Open Liberty introduces `server.xml` configuration attributes to support these options. These attributes for the `webService` and `webServiceClient` element allow you to enable full XML schema validation, enable or disable XML binding (JAXB) default validation, or to use default validation while ignoring only `UnmarshallExceptions: Unknown Element` errors. -* <> +These attributes require the one of the following XML Web Services features to be enabled in your `server.xml` file: -// // // // // // // // -// In the preceding section: -// Change SUB_FEATURE_TITLE to the feature that is included in this release and -// change the SUB_TAG_1/2/3 to the heading tags -// -// However if there's only 1 new feature, delete the previous section and change it to the following sentence: -// "The link:{url-about}[Open Liberty] 24.0.0.12-beta includes SUB_FEATURE_TITLE" -// // // // // // // // +* xref:{url-prefix}/docs/latest/reference/feature/xmlWS-4.0.html[Jakarta XML Web Services +4.0] (`xmlWS-4.0`) +* xref:{url-prefix}/docs/latest/reference/feature/xmlWS-3.0.html[Jakarta XML Web Services +4.0] (`xmlWS-3.0`) +* xref:{url-prefix}/docs/latest/reference/feature/jaxws-2.2.html[Java Web Services] (`jaxws-2.2`) -See also link:{url-prefix}/blog/?search=beta&key=tag[previous Open Liberty beta blog posts]. +You can apply the configuration to web services (`webService`) or web service clients (`webServiceClient`), either globally, or to an individual client or web service implementation. -// // // // DO NOT MODIFY THIS COMMENT BLOCK // // // // -// Blog issue: https://github.com/OpenLiberty/open-liberty/issues/29770 -// Contact/Reviewer: neuwerk -// // // // // // // // -[#SUB_TAG_0] -== Fine tuning XML Web Services inbound SOAP Meessage validation. - -Please provide a summary of the update, including the following points: - - - A sentence or two that introduces the update to someone new to the general technology/concept. - -XML Web Services features on Open Liberty now support fine tuning message validation of inbound SOAP messages. In XML Web Services there's more than one flavor of message validation, and so we've introduced new server.xml configuration to support them. These options allow users to enable full XML Schema Validation, enable or disable XML Binding's (JAXB) Default validation, or to keep Default Validation enabled while ignoring only `UnmarshallExceptions: Unknown Element` errors - - - The Human-readable name and short feature name for your feature- eg WebSockets feature (websockets-1.0). - -jaxws-2.2, xmlWS-3.0, xmlWS-4.0 - - - Who is the target persona? Who do you expect to use the update? eg application developer, operations. - - -XML Schema Validation - Application Developer, Operations - -Default Validation - Operations - -Ignore Unexpected Elements - Operations - - - - What was the problem before and how does your update make their life better? (Why should they care?) - -XML Schema Validation: - -This has never been configurable on Liberty, and has never been enabled. Now with thanks to the `enableSchemaValidation=true` property a developer or admin can set this option to provide more insight into JAXB unmarshalling exceptions and making that painful message debugging easier. This is the highest level of XML validation, and therefor comes with a tradeoff - faster debugging and the most thorough checks on inbound message contents but with the higher performance cost. - -Default Validation - - -JAXB's default validation of inbound SOAP Messages is now configurable with the `enableDefaultValidation=true` property. Depending on whether your application is a XML Web Services Client or Web Service, Liberty either enables or disables default validation. Default validation is much more efficient then XML Schema Validation, so enabling will allow basic message validation with a lower overhead, while disabling it will allow users to ignore various Unmarshalling errors for problematic messages. - -Ignore Unexpected Elements - - -In traditional WebSphere, a user could configure a JVM property `com.ibm.ws.webservices.ignoreUnknownElements=true` to have the runtime ignore all Unknown Elements during JAXB Unmarshalling. The new Open Liberty configuration, `ignoreUnexpectedElements`. allows users to do the same. Its not unusual for a inbound SOAP Message to contain extra elements in the SOAP body when a Web Service has been updated but the client has not. When a message contains an unknown element, Open Liberty will throw a `UnmarshallingException: Unknown Element`. By enabling `ignoreUnkownEllements` a user can keep Validation enabled while ignoring unknown elements. - - - Briefly explain how to make your update work. Include screenshots, diagrams, and/or code snippets, and provide a `server.xml` snippet. - -Each configuration requires the one of the XML Web Services features enabled on your server.xml, additionally the configuration can be applied to Web Services or Web Service Clients. Each configuration can be applied globally, or to a individual Client or Web Service implementation. The following examples show how to enable each option, to disable any of these options, set the corresponding properties to `false` - -# Web Service Client configuration: - -## Global XML Schema Validation: - -`` - -## Targeted XML Schema Validation: - -`` - -The `Client Service Name` will be the name of your XML Web Service Client. This name comes from your `@WebServiceClient(serviceName=` annotated stub class for managed clients, or for unmanaged clients you can check the line in your WSDL file ``. For example, if the name of your Client is `SayHelloService` then the matching `serviceName` would be set to: - - -`` - -## Global Default Validation: - - -`` - -## Targeted Default Validation: - - -`` - -## Global Ignore Unexpected Elements: - - -`` - -## Targeted Ignore Unexpected Elements: - - -`` - - -# Web Service configuration: - -XML Schema Validation: - -`` - -Targeted XML Schema Validation: - - -`` - -The `Web Service Port Name` will be the port name of the individual Web Service implementation. This name comes from your `@WebService(portName=` annotated class, alternatively you can check the line in your WSDL file - `` for the port name. For example, if the name of your port name is `SimpleEchoPort` then the matching `portName` would be set to: - - -`` - -Global Default Validation: - - -`` - -Targeted Default Validation: - - -`` - - -Global Ignore Unexpected Elements: - - -`` - -Targeted Ignore Unexpected Elements: - - -`` - - - Where can they find out more about this specific update (eg Open Liberty docs, Javadoc) and/or the wider technology? - -More info can be found: - - -// DO NOT MODIFY THIS LINE. - - - -To enable the new beta features in your app, add them to your `server.xml`: - -[source, xml] +The examples in the following sections show how to enable each option. To disable any of these options, set the corresponding attributes to `false`. + +=== XML schema validation + +You can set the `enableSchemaValidation=true` attribute to provide more insight into JAXB unmarshalling exceptions and make painful message debugging easier. This option is the highest level of XML validation, which provides faster debugging and the most thorough checks on inbound message contents. But it comes with a tradeoff: higher performance cost. + +The following example shows how to enable XML schema validation for web services globally for your Open Liberty runtime: + +[source,xml] +---- + ---- +To enable XML schema validation globally for web service clients, set the same attribute on the `webServiceClient` element: + +[source,xml] +---- + ---- + +The following example shows how to enable XML schema validation for a specific client service: + +[source,xml] +---- + +---- + +The `Client Service Name` is the name of your XML Web Service client. This name comes from your `@WebServiceClient(serviceName=` annotated stub class for managed clients. For unmanaged clients, you can check the ` +---- + +The following example shows how to enable XML schema validation for a particular web service by usingnthe webservice port: + +[source,xml] +---- + +---- + +The `web service port name` is the port name of the individual web service implementation. This name comes from your `@WebService(portName=` annotated class. Alternatively, you can check the `` line in your WSDL file for the port name. For example, if the name of your port name is `SimpleEchoPort`, set the matching `portName` attribute similar to the following example: + +[source,xml] +---- + +---- + +=== Default validation + +You can now configure the default JAXB validation of inbound SOAP Messages with the `enableDefaultValidation=true` attribute. Depending on whether your application is an XML Web Services client or web service, Open Liberty either enables or disables default validation. Default validation is much more efficient than XML schema validation, so enabling it provides basic message validation with lower overhead. Disabling it lets you ignore various unmarshalling errors for problematic messages. + +The following example shows how to enable default validation globally for your Open Liberty runtime: + +[source,xml] +---- + +---- + +To enable default validation globally for web service clients, set the same attribute on the `webServiceClient` element. + +The following example shows how to enable default validation for a specific web service: + +[source,xml] +---- + +---- + +To enable default validation for a specific web service client, set the same attribute on the `webServiceClient`element and use the `serviceName` attribute to specify the client service. + +=== Ignore unexpected elements + +WebSphere Application Server traditional provides the `com.ibm.ws.webservices.ignoreUnknownElements=true` JVM property to configure the runtime to ignore all unknown elements during JAXB unmarshalling. The new Open Liberty `ignoreUnexpectedElements` attribute provides the same function. Inbound SOAP messages often contain extra elements in the SOAP body when a web service is updated but the client is not. When a message contains an unknown element, Open Liberty throws a `UnmarshallingException: Unknown Element`. By enabling `ignoreUnkownEllements`, you can keep validation enabled while ignoring unknown elements. + +The following example shows how to ignore unexpected elements globally for web services on your Open Liberty runtime: + +[source,xml] +---- + +---- + +To ignore unexpected elements globally for web service clients, set the same attribute on the `webServiceClient` element. + +The following example shows how to ignore unexpected elements for a specific web service: + +[source,xml] +---- + +---- + +To ignore unexpected elements for a specific web service client, set the same attribute on the `webServiceClient`element and use the `serviceName` attribute to specify the client service. + +// DO NOT MODIFY THIS LINE. + [#run] === Try it now -To try out these features, update your build tools to pull the Open Liberty All Beta Features package instead of the main release. The beta works with Java SE 21, Java SE 17, Java SE 11, and Java SE 8. +To try out these features, update your build tools to pull the Open Liberty All Beta Features package instead of the main release. The beta works with Java SE 23, 21, 17, 11, and 8. // // // // // // // // // In the preceding section: // Check if a new non-LTS Java SE version is supported that needs to be added to the list (21, 17, 11, and 8 are LTS and will remain for a while) @@ -222,14 +149,14 @@ To try out these features, update your build tools to pull the Open Liberty All // Check if a new MicroProfile or Jakarta version is in beta that could replace the example values in the codeblock // // // // // // // // -If you're using link:{url-prefix}/guides/maven-intro.html[Maven], you can install the All Beta Features package using: +If you're using link:{url-prefix}/guides/maven-intro.html[Maven], you can install the All Beta Features package by using: [source,xml] ---- io.openliberty.tools liberty-maven-plugin - 3.8.2 + 3.11.1 io.openliberty.beta @@ -269,7 +196,7 @@ buildscript { mavenCentral() } dependencies { - classpath 'io.openliberty.tools:liberty-gradle-plugin:3.6.2' + classpath 'io.openliberty.tools:liberty-gradle-plugin:3.9.1' } } apply plugin: 'liberty' @@ -277,12 +204,6 @@ dependencies { libertyRuntime group: 'io.openliberty.beta', name: 'openliberty-runtime', version: '[24.0.0.12-beta,)' } ---- -// // // // // // // // -// In the preceding section: -// Replace the Maven `3.8.2` with the latest version of the plugin: https://search.maven.org/artifact/io.openliberty.tools/liberty-maven-plugin -// Replace the Gradle `3.6.2` with the latest version of the plugin: https://search.maven.org/artifact/io.openliberty.tools/liberty-gradle-plugin -// TODO: Update GHA to automatically do the above. If the maven.org is problematic, then could fallback to using the GH Releases for the plugins -// // // // // // // // Or if you're using link:{url-prefix}/docs/latest/container-images.html[container images]: @@ -293,7 +214,7 @@ FROM icr.io/appcafe/open-liberty:beta Or take a look at our link:{url-prefix}/downloads/#runtime_betas[Downloads page]. -If you're using link:https://plugins.jetbrains.com/plugin/14856-liberty-tools[IntelliJ IDEA], link:https://marketplace.visualstudio.com/items?itemName=Open-Liberty.liberty-dev-vscode-ext[Visual Studio Code] or link:https://marketplace.eclipse.org/content/liberty-tools[Eclipse IDE], you can also take advantage of our open source link:https://openliberty.io/docs/latest/develop-liberty-tools.html[Liberty developer tools] to enable effective development, testing, debugging and application management all from within your IDE. +If you're using link:https://plugins.jetbrains.com/plugin/14856-liberty-tools[IntelliJ IDEA], link:https://marketplace.visualstudio.com/items?itemName=Open-Liberty.liberty-dev-vscode-ext[Visual Studio Code] or link:https://marketplace.eclipse.org/content/liberty-tools[Eclipse IDE], you can also take advantage of our open source link:https://openliberty.io/docs/latest/develop-liberty-tools.html[Liberty developer tools] to enable effective development, testing, debugging, and application management all from within your IDE. For more information on using a beta release, refer to the link:{url-prefix}docs/latest/installing-open-liberty-betas.html[Installing Open Liberty beta releases] documentation. From 531926a61d4a1e4201165130972ef6e35b7fdb44 Mon Sep 17 00:00:00 2001 From: David Mueller Date: Tue, 12 Nov 2024 11:38:24 -0500 Subject: [PATCH 08/24] Update blog_tags.json --- blog_tags.json | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/blog_tags.json b/blog_tags.json index aa97010fdd..b75fe045bb 100644 --- a/blog_tags.json +++ b/blog_tags.json @@ -2,7 +2,7 @@ "blog_tags": [ { "name": "announcements", - "posts": ["24.0.0.11", + "posts": ["24.0.0.12-beta", "24.0.0.11", "24.0.0.11-beta", "24.0.0.10", "24.0.0.10-beta", "24.0.0.9", "24.0.0.9-beta", "liberty-developer-essentials-badge", @@ -172,7 +172,8 @@ }, { "name": "release", - "posts": ["24.0.0.11", "24.0.0.11-beta", + "posts": ["24.0.0.12-beta", + "24.0.0.11", "24.0.0.11-beta", "24.0.0.10", "24.0.0.10-beta", "24.0.0.9", "24.0.0.9-beta", "24.0.0.8", "24.0.0.8-beta", @@ -236,7 +237,7 @@ }, { "name": "beta", - "posts": ["24.0.0.11-beta", + "posts": ["24.0.0.12-beta", "24.0.0.11-beta", "24.0.0.10-beta", "24.0.0.9-beta", "24.0.0.8-beta", "24.0.0.7-beta", "24.0.0.6-beta", "24.0.0.5-beta", @@ -375,7 +376,7 @@ }, { "name": "jakarta-ee", - "posts": ["rethinking-microservices", + "posts": ["24.0.0.12-beta", "rethinking-microservices", "24.0.0.8", "liberty-developer-essentials-badge", "24.0.0.8-beta", "24.0.0.7-beta", "24.0.0.6-beta", "simplifying-nosql-database-integration-with-jakarta-nosql", From 65ec88fc004975e6eea039ca7cb0658afc3253a8 Mon Sep 17 00:00:00 2001 From: David Mueller Date: Wed, 13 Nov 2024 08:56:51 -0500 Subject: [PATCH 09/24] edits --- posts/2024-11-19-24.0.0.12-beta.adoc | 22 +++++++++++++++++----- 1 file changed, 17 insertions(+), 5 deletions(-) diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc index 0db009380a..688943e8f8 100644 --- a/posts/2024-11-19-24.0.0.12-beta.adoc +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -6,8 +6,8 @@ categories: blog author_picture: https://avatars3.githubusercontent.com/dmuelle author_github: https://github.com/dmuelle seo-title: Enhanced message validation for XML Web Services in 24.0.0.12-beta - OpenLiberty.io -seo-description: The 24.0.0.12-beta release enhances inbound SOAP message validation in XML Web Services to simplify message debugging and make your web services and clients more resilient during updates. -blog_description: The 24.0.0.12-beta release enhances inbound SOAP message validation in XML Web Services to simplify message debugging and make your web services and clients more resilient during updates. +seo-description: The 24.0.0.12-beta release enhances inbound SOAP message validation in XML Web Services to simplify message debugging and make your web services and clients more resilient. +blog_description: The 24.0.0.12-beta release enhances inbound SOAP message validation in XML Web Services to simplify message debugging and make your web services and clients more resilient. open-graph-image: https://openliberty.io/img/twitter_card.jpg open-graph-image-alt: Open Liberty Logo --- @@ -17,7 +17,7 @@ David Mueller :url-prefix: :url-about: / -The 24.0.0.12-beta release enhances inbound SOAP message validation in XML Web Services to simplify message debugging and make your web services and clients more resilient during updates. +The 24.0.0.12-beta release enhances inbound SOAP message validation in XML Web Services to simplify message debugging and make your web services and clients more resilient. See also link:{url-prefix}/blog/?search=beta&key=tag[previous Open Liberty beta blog posts]. @@ -29,7 +29,19 @@ See also link:{url-prefix}/blog/?search=beta&key=tag[previous Open Liberty beta [#xmlws] == Fine-tuning XML Web Services inbound SOAP message validation -XML Web Services features on Open Liberty now support fine-tuned message validation for inbound SOAP messages. XML Web Services provide various options for message validation. In 24.0.0.12-beta, Open Liberty introduces `server.xml` configuration attributes to support these options. These attributes for the `webService` and `webServiceClient` element allow you to enable full XML schema validation, enable or disable XML binding (JAXB) default validation, or to use default validation while ignoring only `UnmarshallExceptions: Unknown Element` errors. +Open Liberty's XML Web Services features now support fine-grained message validation for inbound SOAP messages. This enhancement provides more control over message validation options. +In Open Liberty 24.0.0.12-beta, you can configure message validation using new attributes in the `server.xml` file. These attributes are available for the `webService` and `webServiceClient` elements. + + +[options="header"] +|======================= +| Attribute | Description +| `enableSchemaValidation` | Enable full validation against the XML schema +| `enableDefaultValidation` | Enable or disable default validation for JAXB +| `ignoreUnexpectedElements` | Use default validation while ignoring `UnmarshallExceptions: Unknown Element` errors +|======================= + +By using these attributes, you can tailor message validation to your specific needs and improve the security and reliability of your SOAP-based web services. These attributes require the one of the following XML Web Services features to be enabled in your `server.xml` file: @@ -76,7 +88,7 @@ The `Client Service Name` is the name of your XML Web Service client. This name ---- -The following example shows how to enable XML schema validation for a particular web service by usingnthe webservice port: +The following example shows how to enable XML schema validation for a particular web service by using the web service port: [source,xml] ---- From 064c39f8600dd35e3b013848a05419a05dc05e7e Mon Sep 17 00:00:00 2001 From: David Mueller Date: Wed, 13 Nov 2024 08:57:20 -0500 Subject: [PATCH 10/24] Update 2024-11-19-24.0.0.12-beta.adoc --- posts/2024-11-19-24.0.0.12-beta.adoc | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc index 688943e8f8..14f4bc8810 100644 --- a/posts/2024-11-19-24.0.0.12-beta.adoc +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -81,7 +81,9 @@ The following example shows how to enable XML schema validation for a specific c ---- -The `Client Service Name` is the name of your XML Web Service client. This name comes from your `@WebServiceClient(serviceName=` annotated stub class for managed clients. For unmanaged clients, you can check the `` annotated stub class for managed clients. + +For unmanaged clients, you can check the ` ---- -The `web service port name` is the port name of the individual web service implementation. This name comes from your `@WebService(portName=` annotated class. Alternatively, you can check the `` line in your WSDL file for the port name. For example, if the name of your port name is `SimpleEchoPort`, set the matching `portName` attribute similar to the following example: +The `web service port name` is the port name of the individual web service implementation. This name comes from your `@WebService(portName=` annotated class. + +Alternatively, you can check the `` line in your WSDL file for the port name. For example, if the name of your port name is `SimpleEchoPort`, set the matching `portName` attribute similar to the following example: [source,xml] ---- @@ -152,14 +156,6 @@ To ignore unexpected elements for a specific web service client, set the same at === Try it now To try out these features, update your build tools to pull the Open Liberty All Beta Features package instead of the main release. The beta works with Java SE 23, 21, 17, 11, and 8. -// // // // // // // // -// In the preceding section: -// Check if a new non-LTS Java SE version is supported that needs to be added to the list (21, 17, 11, and 8 are LTS and will remain for a while) -// https://openliberty.io/docs/latest/java-se.html -// -// In the following section: -// Check if a new MicroProfile or Jakarta version is in beta that could replace the example values in the codeblock -// // // // // // // // If you're using link:{url-prefix}/guides/maven-intro.html[Maven], you can install the All Beta Features package by using: From ae740cd3a9b5eaac67664e7000ddd68e25771d9d Mon Sep 17 00:00:00 2001 From: David Mueller Date: Wed, 13 Nov 2024 10:22:22 -0500 Subject: [PATCH 11/24] Update 2024-11-19-24.0.0.12-beta.adoc --- posts/2024-11-19-24.0.0.12-beta.adoc | 38 +++++++++++++++------------- 1 file changed, 21 insertions(+), 17 deletions(-) diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc index 14f4bc8810..1a8b6ebdbd 100644 --- a/posts/2024-11-19-24.0.0.12-beta.adoc +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -59,6 +59,8 @@ The examples in the following sections show how to enable each option. To disabl You can set the `enableSchemaValidation=true` attribute to provide more insight into JAXB unmarshalling exceptions and make painful message debugging easier. This option is the highest level of XML validation, which provides faster debugging and the most thorough checks on inbound message contents. But it comes with a tradeoff: higher performance cost. +==== Global XML schema validation + The following example shows how to enable XML schema validation for web services globally for your Open Liberty runtime: [source,xml] @@ -73,44 +75,40 @@ To enable XML schema validation globally for web service clients, set the same a ---- +==== Targeted XML schema validation -The following example shows how to enable XML schema validation for a specific client service: +The following example shows how to enable XML schema validation for a particular web service by using the web service port: [source,xml] ---- - + ---- -The `Client Service Name` is the name of your XML Web Service client. This name comes from your `@WebServiceClient(serviceName=` annotated stub class for managed clients. +The `web service port name` is the port name of the individual web service implementation. This name comes from your `@WebService(portName=` annotated class. -For unmanaged clients, you can check the `` line in your WSDL file for the port name. -[source,xml] ----- - ----- -The following example shows how to enable XML schema validation for a particular web service by using the web service port: +The following example shows how to enable XML schema validation for a specific client service: [source,xml] ---- - + ---- -The `web service port name` is the port name of the individual web service implementation. This name comes from your `@WebService(portName=` annotated class. +The `Client Service Name` is the name of your XML Web Service client. This name comes from your `@WebServiceClient(serviceName=` annotated stub class for managed clients. + +For unmanaged clients, you can check the `` line in your WSDL file for the port name. For example, if the name of your port name is `SimpleEchoPort`, set the matching `portName` attribute similar to the following example: -[source,xml] ----- - ----- === Default validation You can now configure the default JAXB validation of inbound SOAP Messages with the `enableDefaultValidation=true` attribute. Depending on whether your application is an XML Web Services client or web service, Open Liberty either enables or disables default validation. Default validation is much more efficient than XML schema validation, so enabling it provides basic message validation with lower overhead. Disabling it lets you ignore various unmarshalling errors for problematic messages. -The following example shows how to enable default validation globally for your Open Liberty runtime: +==== Global default validation + +The following example shows how to enable default validation globally for web services in your Open Liberty runtime: [source,xml] ---- @@ -119,6 +117,8 @@ The following example shows how to enable default validation globally for your O To enable default validation globally for web service clients, set the same attribute on the `webServiceClient` element. +==== Targeted default validation + The following example shows how to enable default validation for a specific web service: [source,xml] @@ -132,6 +132,8 @@ To enable default validation for a specific web service client, set the same att WebSphere Application Server traditional provides the `com.ibm.ws.webservices.ignoreUnknownElements=true` JVM property to configure the runtime to ignore all unknown elements during JAXB unmarshalling. The new Open Liberty `ignoreUnexpectedElements` attribute provides the same function. Inbound SOAP messages often contain extra elements in the SOAP body when a web service is updated but the client is not. When a message contains an unknown element, Open Liberty throws a `UnmarshallingException: Unknown Element`. By enabling `ignoreUnkownEllements`, you can keep validation enabled while ignoring unknown elements. +==== Global configuration + The following example shows how to ignore unexpected elements globally for web services on your Open Liberty runtime: [source,xml] @@ -141,6 +143,8 @@ The following example shows how to ignore unexpected elements globally for web s To ignore unexpected elements globally for web service clients, set the same attribute on the `webServiceClient` element. +==== Targeted configuration + The following example shows how to ignore unexpected elements for a specific web service: [source,xml] From 5a13076da801d5c2ba84f05be38cde53b94df7c1 Mon Sep 17 00:00:00 2001 From: David Mueller Date: Wed, 13 Nov 2024 16:15:47 -0500 Subject: [PATCH 12/24] Update 2024-11-19-24.0.0.12-beta.adoc --- posts/2024-11-19-24.0.0.12-beta.adoc | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc index 1a8b6ebdbd..10bdd64b1d 100644 --- a/posts/2024-11-19-24.0.0.12-beta.adoc +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -85,7 +85,6 @@ The following example shows how to enable XML schema validation for a particular ---- The `web service port name` is the port name of the individual web service implementation. This name comes from your `@WebService(portName=` annotated class. - Alternatively, you can check the `` line in your WSDL file for the port name. @@ -97,14 +96,13 @@ The following example shows how to enable XML schema validation for a specific c ---- The `Client Service Name` is the name of your XML Web Service client. This name comes from your `@WebServiceClient(serviceName=` annotated stub class for managed clients. - For unmanaged clients, you can check the ` ---- -To enable default validation for a specific web service client, set the same attribute on the `webServiceClient`element and use the `serviceName` attribute to specify the client service. +To enable default validation for a specific web service client, set the `enableDefaultValidation` attribute on the `webServiceClient`element and use the `serviceName` attribute to specify the client service. === Ignore unexpected elements -WebSphere Application Server traditional provides the `com.ibm.ws.webservices.ignoreUnknownElements=true` JVM property to configure the runtime to ignore all unknown elements during JAXB unmarshalling. The new Open Liberty `ignoreUnexpectedElements` attribute provides the same function. Inbound SOAP messages often contain extra elements in the SOAP body when a web service is updated but the client is not. When a message contains an unknown element, Open Liberty throws a `UnmarshallingException: Unknown Element`. By enabling `ignoreUnkownEllements`, you can keep validation enabled while ignoring unknown elements. +The new Open Liberty `ignoreUnexpectedElements` attribute provides the same function. Inbound SOAP messages often contain extra elements in the SOAP body when a web service is updated but the client is not. When a message contains an unknown element, Open Liberty throws a `UnmarshallingException: Unknown Element`. By enabling `ignoreUnkownEllements`, you can keep validation enabled while ignoring unknown elements. ==== Global configuration @@ -141,7 +139,7 @@ The following example shows how to ignore unexpected elements globally for web s ---- -To ignore unexpected elements globally for web service clients, set the same attribute on the `webServiceClient` element. +To ignore unexpected elements globally for web service clients, set the `ignoreUnexpectedElements` attribute on the `webServiceClient` element. ==== Targeted configuration From 1ac8b5c1412cdc70bbfe624b797c354072503267 Mon Sep 17 00:00:00 2001 From: David Mueller <48686014+dmuelle@users.noreply.github.com> Date: Fri, 15 Nov 2024 12:12:44 -0500 Subject: [PATCH 13/24] Update posts/2024-11-19-24.0.0.12-beta.adoc Co-authored-by: Thomas Johnson --- posts/2024-11-19-24.0.0.12-beta.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc index 10bdd64b1d..22a9d63600 100644 --- a/posts/2024-11-19-24.0.0.12-beta.adoc +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -84,7 +84,7 @@ The following example shows how to enable XML schema validation for a particular ---- -The `web service port name` is the port name of the individual web service implementation. This name comes from your `@WebService(portName=` annotated class. +Here `portName`'s value port name of the Web Service implementation you're configuring. This name comes from your `@WebService(portName=` annotated class. Alternatively, you can check the `` line in your WSDL file for the port name. From d5c9be9e5a5a1dc34e9f65c572812aead2acdb60 Mon Sep 17 00:00:00 2001 From: David Mueller <48686014+dmuelle@users.noreply.github.com> Date: Fri, 15 Nov 2024 12:13:26 -0500 Subject: [PATCH 14/24] Update posts/2024-11-19-24.0.0.12-beta.adoc --- posts/2024-11-19-24.0.0.12-beta.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc index 22a9d63600..68237e9f5e 100644 --- a/posts/2024-11-19-24.0.0.12-beta.adoc +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -84,7 +84,7 @@ The following example shows how to enable XML schema validation for a particular ---- -Here `portName`'s value port name of the Web Service implementation you're configuring. This name comes from your `@WebService(portName=` annotated class. +The value of `portName` is the port name of the Web Service implementation you're configuring. This name comes from your `@WebService(portName=` annotated class. Alternatively, you can check the `` line in your WSDL file for the port name. From 784fca835b6ce2cb3db0db980bb8f3fbf072758c Mon Sep 17 00:00:00 2001 From: David Mueller <48686014+dmuelle@users.noreply.github.com> Date: Fri, 15 Nov 2024 12:13:42 -0500 Subject: [PATCH 15/24] Update posts/2024-11-19-24.0.0.12-beta.adoc Co-authored-by: Thomas Johnson --- posts/2024-11-19-24.0.0.12-beta.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc index 68237e9f5e..ade6caefca 100644 --- a/posts/2024-11-19-24.0.0.12-beta.adoc +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -95,7 +95,7 @@ The following example shows how to enable XML schema validation for a specific c ---- -The `Client Service Name` is the name of your XML Web Service client. This name comes from your `@WebServiceClient(serviceName=` annotated stub class for managed clients. +Here `serviceName`'s value is the name of the Web Service Client you're are configuring. This name comes from your `@WebServiceClient(serviceName=` annotated stub class for managed clients. For unmanaged clients, you can check the ` Date: Fri, 15 Nov 2024 12:14:41 -0500 Subject: [PATCH 16/24] Update posts/2024-11-19-24.0.0.12-beta.adoc --- posts/2024-11-19-24.0.0.12-beta.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc index ade6caefca..5dd4f88f84 100644 --- a/posts/2024-11-19-24.0.0.12-beta.adoc +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -95,7 +95,7 @@ The following example shows how to enable XML schema validation for a specific c ---- -Here `serviceName`'s value is the name of the Web Service Client you're are configuring. This name comes from your `@WebServiceClient(serviceName=` annotated stub class for managed clients. +The value of `serviceName` is the name of the Web Service Client you're configuring. This name comes from your `@WebServiceClient(serviceName=` annotated stub class for managed clients. For unmanaged clients, you can check the ` Date: Fri, 15 Nov 2024 12:15:16 -0500 Subject: [PATCH 17/24] Update posts/2024-11-19-24.0.0.12-beta.adoc Co-authored-by: Thomas Johnson --- posts/2024-11-19-24.0.0.12-beta.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc index 5dd4f88f84..c80f7f2802 100644 --- a/posts/2024-11-19-24.0.0.12-beta.adoc +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -102,7 +102,7 @@ For unmanaged clients, you can check the ` Date: Fri, 15 Nov 2024 16:02:38 -0500 Subject: [PATCH 19/24] Update 2024-11-19-24.0.0.12-beta.adoc --- posts/2024-11-19-24.0.0.12-beta.adoc | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc index 4aeca9c8f2..d6458e193a 100644 --- a/posts/2024-11-19-24.0.0.12-beta.adoc +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -41,6 +41,8 @@ In Open Liberty 24.0.0.12-beta, you can configure message validation using new a | `ignoreUnexpectedElements` | Use default validation while ignoring `UnmarshallExceptions: Unknown Element` errors |======================= +The default value for all three attributes is `false`, except for `enableDefaultValidation` for web service clients, which defaults to `true`. + By using these attributes, you can tailor message validation to your specific needs and improve the security and reliability of your SOAP-based web services. These attributes require the one of the following XML Web Services features to be enabled in your `server.xml` file: @@ -53,7 +55,8 @@ These attributes require the one of the following XML Web Services features to b You can apply the configuration to web services (`webService`) or web service clients (`webServiceClient`), either globally, or to an individual client or web service implementation. -The examples in the following sections show how to enable each option. To disable any of these options, set the corresponding attributes to `false`. + + === XML schema validation @@ -102,7 +105,7 @@ For unmanaged clients, you can check the ` ---- -To enable default validation globally for web service clients, set the same attribute on the `webServiceClient` element. +Default validation is enabled by default for web service clients. To disable default validation globally for web service clients, set the `enableDefaultValidation="true"` attribute on the `webServiceClient` element. + +[source,xml] +---- + +---- ==== Targeted default validation @@ -124,7 +132,7 @@ The following example shows how to enable default validation for a specific web ---- -To enable default validation for a specific web service client, set the `enableDefaultValidation` attribute on the `webServiceClient`element and use the `serviceName` attribute to specify the client service. +Default validation is enabled by default for web service clients. To disable default validation for a specific web service client, set the `enableDefaultValidation="true"` attribute on the `webServiceClient` element and use the `serviceName` attribute to specify the client service. === Ignore unexpected elements From 0e478ea65ea49f532ccbf1e5acc3c02638cfdf05 Mon Sep 17 00:00:00 2001 From: Hiroko Takamiya Date: Sun, 17 Nov 2024 12:39:22 -0500 Subject: [PATCH 20/24] Contribution from Takakiyo-san and update to the original version with available language --- posts/2024-11-05-24.0.0.11.adoc | 3 + posts/ja/2024-11-05-24.0.0.11.adoc | 137 +++++++++++++++++++++++++++++ 2 files changed, 140 insertions(+) create mode 100755 posts/ja/2024-11-05-24.0.0.11.adoc diff --git a/posts/2024-11-05-24.0.0.11.adoc b/posts/2024-11-05-24.0.0.11.adoc index 1668a18440..92548c3f10 100644 --- a/posts/2024-11-05-24.0.0.11.adoc +++ b/posts/2024-11-05-24.0.0.11.adoc @@ -10,6 +10,9 @@ seo-description: The 24.0.0.11 release expands the collection of InstantOn-suppo blog_description: The 24.0.0.11 release expands the collection of InstantOn-supported Liberty features to include messaging and authorization capabilities. A new Open Liberty guide and a CVE fix are also included. open-graph-image: https://openliberty.io/img/twitter_card.jpg open-graph-image-alt: Open Liberty Logo +blog-available-in-languages: +- lang: ja + path: /ja/blog/2024/11/05/24.0.0.11.html --- = Rapid startup for applications that use authorization and messaging features in 24.0.0.11 David Mueller diff --git a/posts/ja/2024-11-05-24.0.0.11.adoc b/posts/ja/2024-11-05-24.0.0.11.adoc new file mode 100755 index 0000000000..f1da7744bd --- /dev/null +++ b/posts/ja/2024-11-05-24.0.0.11.adoc @@ -0,0 +1,137 @@ +--- +layout: post +title: 24.0.0.11での認証およびメッセージング機能を使用するアプリケーションの高速起動 +# Do NOT change the categories section +categories: blog +author_picture: https://avatars3.githubusercontent.com/dmuelle +author_github: https://github.com/dmuelle +seo-title: 24.0.0.11での認証およびメッセージング機能を使用するアプリケーションの高速起動 - OpenLiberty.io +seo-description: この 24.0.0.11 リリースでは、InstantOn がサポートする Liberty 機能のコレクションが拡張され、メッセージング機能と認証機能が追加されました。新しい Open Liberty ガイドと CVE 修正も含まれています。 +blog_description: この 24.0.0.11 リリースでは、InstantOn がサポートする Liberty 機能のコレクションが拡張され、メッセージング機能と認証機能が追加されました。新しい Open Liberty ガイドと CVE 修正も含まれています。 +open-graph-image: https://openliberty.io/img/twitter_card.jpg +open-graph-image-alt: Open Liberty Logo +additional_authors: +- name: 田中 孝清 (翻訳) + github: https://github.com/takakiyo + image: https://avatars.githubusercontent.com/takakiyo +blog-available-in-languages: +- lang: en + path: /blog/2024/11/05/24.0.0.11.html +--- += 24.0.0.11での認証およびメッセージング機能を使用するアプリケーションの高速起動 +David Mueller +:imagesdir: / +:url-prefix: +:url-about: / +//Blank line here is necessary before starting the body of the post. + +この 24.0.0.11 リリースでは、InstantOn がサポートする Liberty 機能のコレクションが拡張され、メッセージング機能と認証機能が追加されました。新しい Open Liberty ガイドと CVE 修正も含まれています。 + +link:{url-about}[Open Liberty] 24.0.0.11 では、以下のアップデートがおこなわれました。 + +* <> +* <> +* <> + + +link:https://github.com/OpenLiberty/open-liberty/issues?q=label%3Arelease%3A240011+label%3A%22release+bug%22[24.0.0.11] で修正されたバグの一覧をご覧ください。 + +link:{url-prefix}/blog/?search=release&search!=beta[以前の Open Liberty GA リリースブログ投稿] をチェックしてください。 + + +[#run] + +== 24.0.0.11 を使用してアプリを開発および実行する + +link:{url-prefix}/guides/maven-intro.html[Maven] を使用している場合は、`pom.xml` ファイルに以下を含めます。 + +[source,xml] +---- + + io.openliberty.tools + liberty-maven-plugin + 3.11.1 + +---- + +または、link:{url-prefix}/guides/gradle-intro.html[Gradle] の場合は、`build.gradle` ファイルに次の内容を含めます。 + +[source,gradle] +---- +buildscript { + repositories { + mavenCentral() + } + dependencies { + classpath 'io.openliberty.tools:liberty-gradle-plugin:3.9.1' + } +} +apply plugin: 'liberty' +---- + +または、link:{url-prefix}/docs/latest/container-images.html[コンテナ イメージ] を使用している場合: + +[source] +---- +FROM icr.io/appcafe/open-liberty +---- + +または、link:{url-prefix}/start/[ダウンロード・ページ]をご覧ください。 + +link:https://plugins.jetbrains.com/plugin/14856-liberty-tools[IntelliJ IDEA]、link:https://marketplace.visualstudio.com/items?itemName=Open-Liberty.liberty-dev-vscode-ext[Visual Studio Code]、または link:https://marketplace.eclipse.org/content/liberty-tools[Eclipse IDE]を使用している場合は、オープンソースの link:https://openliberty.io/docs/latest/develop-liberty-tools.html[Liberty 開発者ツール] を活用して、IDE 内から効果的な開発、テスト、デバッグ、アプリケーション管理を行うこともできます。 + +[link=https://stackoverflow.com/tags/open-liberty] +image::img/blog/blog_btn_stack_ja.svg[Stack Overflowで質問する, align="center"] + +// // // // DO NOT MODIFY THIS COMMENT BLOCK // // // // +// Blog issue: https://github.com/OpenLiberty/open-liberty/issues/29887 +// Contact/Reviewer: gkwan-ibm +// // // // // // // // + +[#instant] +== Liberty InstantOnで認証機能とメッセージング機能が使用できるようになりました + +InstantOn は link:{url-prefix}/docs/latest/instanton.html#supported-features[Open Liberty 機能のサブセット]をサポートしています。24.0.0.11 リリースで、この利用可能なサブセットに以下のFeatureが追加されました。 + +* link:{url-prefix}/docs/latest/reference/feature/jacc-1.5.html[Java Authorization Contract for Containers (jacc-1.5)]. +* link:{url-prefix}/docs/latest/reference/feature/appAuthorization-2.0.html[Jakarta Authorization 2.0 (appAuthorization-2.0)] +* link:{url-prefix}/docs/latest/reference/feature/appAuthorization-2.1.html[Jakarta Authorization 2.1 (appAuthorization-2.1)] +* link:{url-prefix}/docs/latest/reference/feature/wasJmsServer-1.0.html[Message Server 1.0 (wasJmsServer-1.0)] +* link:{url-prefix}/docs/latest/reference/feature/messagingServer-3.0.html[Messaging Server 3.0 (messagingServer-3.0)] +* link:{url-prefix}/docs/latest/reference/feature/wasJmsClient-2.0.html[JMS Client for Message Server 2.0 (wasJmsClient-2.0)] +* link:{url-prefix}/docs/latest/reference/feature/messagingClient-3.0.html[Messaging Server Client 3.0 (messagingClient-3.0)] + +この機能強化により、Open Liberty InstantOn を使用して、これらの機能を使用するアプリケーションを迅速にデプロイできるようになります。詳細については、link:{url-prefix}/docs/latest/instanton.html[「Open Liberty InstantOn によるコンテナー化されたアプリケーションの起動の高速化」]を参照してください。 + + +[#guide] +== 新しいガイド: "Producing and consuming messages in Java microservices" + + +新しいガイド link:https://openliberty.io/guides/jms-intro.html[Producing and consuming messages in Java microservices] が link:https://openliberty.io/guides/#rest_alternatives[REST alternatives] カテゴリーで公開されました。 Java マイクロサービス間で標準的なJakarta メッセージング APIを使用して、組み込みの Liberty メッセージングサーバーまたは外部メッセージングサーバーである IBM MQに接続し、メッセージを送信(Produce)し受信(Consume)する方法を学習します。 + + + +[#CVEs] +== Security Vulnerability (CVE) の修正 +[cols="5*"] + +以下の CVE が 24.0.0.11 で修正されました。 + +|=== +|CVE |CVSS Score |Vulnerability Assessment |Versions Affected |Notes + +|https://www.cve.org/CVERecord?id=CVE-2024-7254[CVE-2024-7254] +|7.5 +|Denial of service +|20.0.0.12 - 24.0.0.10 +| link:{url-prefix}/docs/latest/reference/feature/grpc-1.0.html[grpc-1.0] と link:{url-prefix}/docs/latest/reference/feature/grpcClient-1.0.html[grpcClient-1.0] に影響あり +|=== + +過去のセキュリティ脆弱性修正の一覧については、link:{url-prefix}/docs/latest/security-vulnerabilities.html[セキュリティ脆弱性 (CVE) リスト] を参照してください。 + + +== Open Liberty 24.0.0.11 を今すぐ入手 + +<> こちらのリンクから入手できます。 + From 415945ec6bc83d64f3a255e4e785c1c55c371c51 Mon Sep 17 00:00:00 2001 From: David Mueller Date: Mon, 18 Nov 2024 09:38:10 -0500 Subject: [PATCH 21/24] Update 2024-11-19-24.0.0.12-beta.adoc --- posts/2024-11-19-24.0.0.12-beta.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc index d6458e193a..a6d4dec232 100644 --- a/posts/2024-11-19-24.0.0.12-beta.adoc +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -134,6 +134,11 @@ The following example shows how to enable default validation for a specific web Default validation is enabled by default for web service clients. To disable default validation for a specific web service client, set the `enableDefaultValidation="true"` attribute on the `webServiceClient` element and use the `serviceName` attribute to specify the client service. +[source,xml] +---- + +---- + === Ignore unexpected elements The new Open Liberty `ignoreUnexpectedElements` attribute provides the same function. Inbound SOAP messages often contain extra elements in the SOAP body when a web service is updated but the client is not. When a message contains an unknown element, Open Liberty throws a `UnmarshallingException: Unknown Element`. By enabling `ignoreUnkownEllements`, you can keep validation enabled while ignoring unknown elements. From fc675b39e84c7c49d4855ecf214a75b9b76c6d4a Mon Sep 17 00:00:00 2001 From: David Mueller Date: Mon, 18 Nov 2024 10:26:16 -0500 Subject: [PATCH 22/24] Update 2024-11-19-24.0.0.12-beta.adoc --- posts/2024-11-19-24.0.0.12-beta.adoc | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc index a6d4dec232..7b6c5f7433 100644 --- a/posts/2024-11-19-24.0.0.12-beta.adoc +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -43,17 +43,13 @@ In Open Liberty 24.0.0.12-beta, you can configure message validation using new a The default value for all three attributes is `false`, except for `enableDefaultValidation` for web service clients, which defaults to `true`. -By using these attributes, you can tailor message validation to your specific needs and improve the security and reliability of your SOAP-based web services. - These attributes require the one of the following XML Web Services features to be enabled in your `server.xml` file: -* xref:{url-prefix}/docs/latest/reference/feature/xmlWS-4.0.html[Jakarta XML Web Services -4.0] (`xmlWS-4.0`) -* xref:{url-prefix}/docs/latest/reference/feature/xmlWS-3.0.html[Jakarta XML Web Services -4.0] (`xmlWS-3.0`) -* xref:{url-prefix}/docs/latest/reference/feature/jaxws-2.2.html[Java Web Services] (`jaxws-2.2`) +* xref:{url-prefix}/docs/latest/reference/feature/xmlWS-4.0.html[Jakarta XML Web Services 4.0] (`xmlWS-4.0`) +* xref:{url-prefix}/docs/latest/reference/feature/xmlWS-3.0.html[Jakarta XML Web Services 4.0] (`xmlWS-3.0`) +* xref:{url-prefix}/docs/latest/reference/feature/jaxws-2.2.html[Java Web Services 2.2] (`jaxws-2.2`) -You can apply the configuration to web services (`webService`) or web service clients (`webServiceClient`), either globally, or to an individual client or web service implementation. +By using these attributes, you can tailor message validation to your specific needs and improve the security and reliability of your SOAP-based web services. You can apply the configuration to web services (`webService`) or web service clients (`webServiceClient`), either globally, or to an individual client or web service implementation. From 38e90ecd2a8c67c1bdd0d9db18e5e9df4b54dafa Mon Sep 17 00:00:00 2001 From: David Mueller Date: Mon, 18 Nov 2024 11:56:29 -0500 Subject: [PATCH 23/24] Update 2024-11-19-24.0.0.12-beta.adoc --- posts/2024-11-19-24.0.0.12-beta.adoc | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc index 7b6c5f7433..f7dbba28b1 100644 --- a/posts/2024-11-19-24.0.0.12-beta.adoc +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -51,9 +51,6 @@ These attributes require the one of the following XML Web Services features to b By using these attributes, you can tailor message validation to your specific needs and improve the security and reliability of your SOAP-based web services. You can apply the configuration to web services (`webService`) or web service clients (`webServiceClient`), either globally, or to an individual client or web service implementation. - - - === XML schema validation You can set the `enableSchemaValidation=true` attribute to provide more insight into JAXB unmarshalling exceptions and make painful message debugging easier. This option is the highest level of XML validation, which provides faster debugging and the most thorough checks on inbound message contents. But it comes with a tradeoff: higher performance cost. @@ -112,11 +109,11 @@ The following example shows how to enable default validation globally for web se ---- -Default validation is enabled by default for web service clients. To disable default validation globally for web service clients, set the `enableDefaultValidation="true"` attribute on the `webServiceClient` element. +Default validation is enabled by default for web service clients. To disable default validation globally for web service clients, set the `enableDefaultValidation="false"` attribute on the `webServiceClient` element. [source,xml] ---- - + ---- ==== Targeted default validation @@ -128,7 +125,7 @@ The following example shows how to enable default validation for a specific web ---- -Default validation is enabled by default for web service clients. To disable default validation for a specific web service client, set the `enableDefaultValidation="true"` attribute on the `webServiceClient` element and use the `serviceName` attribute to specify the client service. +Default validation is enabled by default for web service clients. To disable default validation for a specific web service client, set the `enableDefaultValidation="false"` attribute on the `webServiceClient` element and use the `serviceName` attribute to specify the client service. [source,xml] ---- From b4057b7b276968fd013cf2c28e351674c4f7e6b1 Mon Sep 17 00:00:00 2001 From: David Mueller Date: Tue, 19 Nov 2024 16:18:34 -0500 Subject: [PATCH 24/24] apply changes from Adams review apply changes from #4148 review --- posts/2024-11-19-24.0.0.12-beta.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/posts/2024-11-19-24.0.0.12-beta.adoc b/posts/2024-11-19-24.0.0.12-beta.adoc index f7dbba28b1..292e512db9 100644 --- a/posts/2024-11-19-24.0.0.12-beta.adoc +++ b/posts/2024-11-19-24.0.0.12-beta.adoc @@ -41,9 +41,9 @@ In Open Liberty 24.0.0.12-beta, you can configure message validation using new a | `ignoreUnexpectedElements` | Use default validation while ignoring `UnmarshallExceptions: Unknown Element` errors |======================= -The default value for all three attributes is `false`, except for `enableDefaultValidation` for web service clients, which defaults to `true`. +The default value for `enableDefaultValidation` in the `webServiceClient` element is `true`. The rest of the attributes default to `false` in both the `webServiceClient` and `webService` elements. -These attributes require the one of the following XML Web Services features to be enabled in your `server.xml` file: +These attributes require one of the following XML Web Services features to be enabled in your `server.xml` file: * xref:{url-prefix}/docs/latest/reference/feature/xmlWS-4.0.html[Jakarta XML Web Services 4.0] (`xmlWS-4.0`) * xref:{url-prefix}/docs/latest/reference/feature/xmlWS-3.0.html[Jakarta XML Web Services 4.0] (`xmlWS-3.0`) @@ -134,7 +134,7 @@ Default validation is enabled by default for web service clients. To disable def === Ignore unexpected elements -The new Open Liberty `ignoreUnexpectedElements` attribute provides the same function. Inbound SOAP messages often contain extra elements in the SOAP body when a web service is updated but the client is not. When a message contains an unknown element, Open Liberty throws a `UnmarshallingException: Unknown Element`. By enabling `ignoreUnkownEllements`, you can keep validation enabled while ignoring unknown elements. +Inbound SOAP messages often contain extra elements in the SOAP body when a web service is updated but the client is not. When a message contains an unknown element, Open Liberty throws a `UnmarshallingException: Unknown Element`. By enabling `ignoreUnexpectedElements`, you can keep validation enabled while ignoring unknown elements. ==== Global configuration @@ -156,7 +156,7 @@ The following example shows how to ignore unexpected elements for a specific web ---- -To ignore unexpected elements for a specific web service client, set the same attribute on the `webServiceClient`element and use the `serviceName` attribute to specify the client service. +To ignore unexpected elements for a specific web service client, set the same attribute on the `webServiceClient` element and use the `serviceName` attribute to specify the client service. // DO NOT MODIFY THIS LINE.