(plc4x-website) branch asf-site updated: Site checkin for project PLC4X: Jenkins Tools

[git-site-role]

This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/plc4x-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 87984290c Site checkin for project PLC4X: Jenkins Tools
87984290c is described below

commit 87984290c87b3b769419a301028c35624dfaccc1
Author: jenkins <bui...@apache.org>
AuthorDate: Wed Feb 14 22:36:51 2024 +0000

    Site checkin for project PLC4X: Jenkins Tools
---
 users/getting-started/plc4j.html          | 6 +++---
 users/getting-started/virtual-modbus.html | 4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/users/getting-started/plc4j.html b/users/getting-started/plc4j.html
index 6d744861d..c6c2dd9d9 100644
--- a/users/getting-started/plc4j.html
+++ b/users/getting-started/plc4j.html
@@ -419,7 +419,7 @@ So if a protocol doesn&#8217;t support subscription based 
communication it is ou
 <div class="listingblock">
 <div class="content">
 <pre>// Check if this connection support reading of data.
-if (!plcConnection.getMetadata().canRead()) {
+if (!plcConnection.getMetadata().isReadSupported()) {
   logger.error("This connection doesn't support reading.");
   return;
 }</pre>
@@ -572,7 +572,7 @@ In order to avoid causing this exception to be thrown, 
however there are <code>i
 <div class="listingblock">
 <div class="content">
 <pre>// Check if this connection support writing of data.
-if (!plcConnection.getMetadata().canWrite()) {
+if (!plcConnection.getMetadata().isWriteSupported()) {
   logger.error("This connection doesn't support writing.");
   return;
 }</pre>
@@ -640,7 +640,7 @@ asyncResponse.whenComplete((response, throwable) -&gt; {
 <div class="listingblock">
 <div class="content">
 <pre>// Check if this connection support subscribing to data.
-if (!plcConnection.getMetadata().canSubscribe()) {
+if (!plcConnection.getMetadata().isSubscribeSupported()) {
     logger.error("This connection doesn't support subscribing.");
     return;
 }</pre>
diff --git a/users/getting-started/virtual-modbus.html 
b/users/getting-started/virtual-modbus.html
index cef73b31f..f2ebf225a 100644
--- a/users/getting-started/virtual-modbus.html
+++ b/users/getting-started/virtual-modbus.html
@@ -680,7 +680,7 @@ So if a protocol doesn&#8217;t support subscription based 
communication it is ou
 <div class="listingblock">
 <div class="content">
 <pre>// Check if this connection support reading of data.
-if (!plcConnection.getMetadata().canRead()) {
+if (!plcConnection.getMetadata().isReadSupported()) {
   logger.error("This connection doesn't support reading.");
   return;
 }</pre>
@@ -859,7 +859,7 @@ If you attempt to write to these, this will result in 
errors.</p>
 <div class="listingblock">
 <div class="content">
 <pre>// Check if this connection support reading of data.
-if (!plcConnection.getMetadata().canWrite()) {
+if (!plcConnection.getMetadata().isWriteSupported()) {
   logger.error("This connection doesn't support writing.");
   return;
 }</pre>