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 ee310a9e3 Site checkin for project PLC4X: Jenkins Tools
ee310a9e3 is described below

commit ee310a9e31532c1d708632fde5587b83562eca15
Author: jenkins <[email protected]>
AuthorDate: Mon Jan 2 14:25:39 2023 +0000

    Site checkin for project PLC4X: Jenkins Tools
---
 users/integrations/apache-camel.html | 95 +-----------------------------------
 1 file changed, 2 insertions(+), 93 deletions(-)

diff --git a/users/integrations/apache-camel.html 
b/users/integrations/apache-camel.html
index 6ce0f09c3..78d31cd3b 100644
--- a/users/integrations/apache-camel.html
+++ b/users/integrations/apache-camel.html
@@ -297,99 +297,8 @@
 <h2 id="apache_camel">Apache Camel</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>The Camel Component for PLC4X allows you to create routes using the PLC4X 
API to read from a PLC device or write to it.</p>
-</div>
-<div class="sect2">
-<h3 id="maven_dependency">Maven dependency</h3>
-<div class="paragraph">
-<p>To use the Camel component, just add following dependency to your 
project</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre>&lt;dependency&gt;
-  &lt;groupId&gt;org.apache.plc4x&lt;/groupId&gt;
-  &lt;artifactId&gt;plc4j-apache-camel&lt;/artifactId&gt;
-  &lt;version&gt;{current-last-released-version}&lt;/version&gt;
-&lt;/dependency&gt;</pre>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="endpoint">Endpoint</h2>
-<div class="sectionbody">
-<table class="tableblock frame-all grid-all stretch">
-<colgroup>
-<col style="width: 50%;"/>
-<col style="width: 50%;"/>
-</colgroup>
-<thead>
-<tr>
-<th class="tableblock halign-left valign-top">Name</th>
-<th class="tableblock halign-left valign-top">Value</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><strong>Tags</strong></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">The tags 
to read as <code>Map&lt;String,String&gt;</code> containing the tagname 
associated to its query</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><strong>Trigger</strong></p></td>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock">(<strong>Consumer</strong>) Query to a trigger. On a rising 
edge of the trigger, the tags will be read once</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><strong>Period</strong></p></td>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock">(<strong>Consumer</strong>) Interval on which the Trigger 
should be checked</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><strong>Driver parameters</strong></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Every 
Parameter unknown to the Component will be passed to the driver</p></td>
-</tr>
-</tbody>
-</table>
-<div class="sect2">
-<h3 id="uri_format">URI Format</h3>
-<div class="listingblock">
-<div class="content">
-<pre>plc4x:[driver-code]://[IP|host][?parameters]</pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Note that sometimes you want to add the <code>Transport</code> code after 
the <code>Driver</code> code:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre>plc4x:[driver-code]:[transport-code]://[IP|host][?parameters]</pre>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="consumer">Consumer</h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>The consumer supports one-time reading or Triggered Reading. 
(<em>Schedulded Reading using Period only soon</em>).To read from
-the PLC, use a  <code>Map&lt;String,String&gt;</code> containing the Alias and 
Queries for the Data you want.</p>
-</div>
-<div class="paragraph">
-<p>The Body create by the Consumer will be a 
<code>Map&lt;String,Object&gt;</code> containing the Aliases and there 
associated value
-read from the PLC.</p>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="producer">Producer</h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>To write data to the PLC, we also use a <code>Map</code>. The difference 
with the Producer is that the <code>Value</code> of the Map has also to
-be a Map. Also, this <code>Map</code> has to be set into the <code>Body</code> 
of the <code>Message</code></p>
-</div>
-<div class="paragraph">
-<p>The used <code>Map</code> would be a 
<code>Map&lt;String,Map&lt;String,Object&gt;</code> where the 
<code>Map&lt;String,Object&gt;</code> represent the Query and the
-data we want to write to it.</p>
+<p>The Camel Component for PLC4X allows you to create routes using the PLC4X 
API to read from a PLC device or write to it.
+This component is now maintained within the <a 
href="https://camel.apache.org/components/next/plc4x-component.html";>Apache 
Camel</a> Project.</p>
 </div>
 </div>
 </div>

Reply via email to