From 1a1fdf2156eba0efe7a3f07c6c811ec283bc03d5 Mon Sep 17 00:00:00 2001 From: John Blum Date: Tue, 18 Jun 2019 07:01:12 -0700 Subject: [PATCH] SGF-827 - Additional URL cleanup caught by Checkstyle. --- src/main/asciidoc/reference/data.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/main/asciidoc/reference/data.adoc b/src/main/asciidoc/reference/data.adoc index 531432ef..f4364a09 100644 --- a/src/main/asciidoc/reference/data.adoc +++ b/src/main/asciidoc/reference/data.adoc @@ -117,9 +117,9 @@ distributed transactions. Many managed environments with CMT maintain support for "_Last Resource_", non-XA compliant resources in JTA transactions though it is not actually required in the JTA spec. More information on what a non-XA compliant, "_Last Resource_" means can be found in Red Hat's https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/5/html/Administration_And_Configuration_Guide/lrco-overview.html[documentation]. -In fact, Red Hat's JBoss project, http://narayana.io/[Narayana] is one such LGPL Open Source implementation. _Narayana_ +In fact, Red Hat's JBoss project, https://narayana.io/[Narayana] is one such LGPL Open Source implementation. _Narayana_ refers to this as "_Last Resource Commit Optimization_" (LRCO). More details can be found -http://narayana.io//docs/project/index.html#d0e1859[here]. +https://narayana.io//docs/project/index.html#d0e1859[here]. However, whether you are using {data-store-name} in a standalone environment with an Open Source JTA Transaction Management implementation that supports "_Last Resource_", or a managed environment (e.g. Java EE AS such as WAS),