[ofbiz-framework] branch release18.12 updated: Documented: Comment out the SOAP and HTTP engines (OFBIZ-12212)

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

jleroux pushed a commit to branch release18.12
in repository https://gitbox.apache.org/repos/asf/ofbiz-framework.git


The following commit(s) were added to refs/heads/release18.12 by this push:
     new e580958  Documented: Comment out the SOAP and HTTP engines (OFBIZ-12212)
e580958 is described below

commit e5809580bb469322ed4f999fa8ee5abc15a06a05
Author: Jacques Le Roux <[hidden email]>
AuthorDate: Tue Mar 30 13:04:35 2021 +0200

    Documented: Comment out the SOAP and HTTP engines (OFBIZ-12212)
   
    Documents that the EntitySync feature is no longer available OOTB.
    You need first to re allow the HTTP engine
---
 .../entityext/src/doc/asciidoc/EntitySync-manual.adoc | 19 +++++++++++--------
 1 file changed, 11 insertions(+), 8 deletions(-)

diff --git a/framework/entityext/src/doc/asciidoc/EntitySync-manual.adoc b/framework/entityext/src/doc/asciidoc/EntitySync-manual.adoc
index 9146736..ca495f9 100644
--- a/framework/entityext/src/doc/asciidoc/EntitySync-manual.adoc
+++ b/framework/entityext/src/doc/asciidoc/EntitySync-manual.adoc
@@ -27,20 +27,23 @@ ifdef::backend-pdf[]
 endif::[]
 
 == Introduction to Entity Synchronization
+WARNING: After https://issues.apache.org/jira/browse/OFBIZ-12212[OFBIZ-12212] "Comment out the SOAP and HTTP engines" this feature is no longer available OOTB. You need first to re allow the HTTP engine
+
+
 
 The general idea behind the Entity Sync stuff is to re-create transactions from a central database into one or
 more other databases, each represented by a set of records in the EntitySync and related entities.
 
-Though the Entity Sync mechanism can be used without the now deprecated POS, it was mostly destined to it.
+Though the Entity Sync mechanism can be used without the now deprecated POS, it was mostly destined to it.
 It works well on a reliable network (LAN), it's a bit harder on Internet (WAN) but nothing impossible...
 
-The four fields (lastUpdatedStamp, lastUpdatedTxStamp, createdStamp, createdTxStamp) are added to each entity and
-automatically populated so that queries can be done on each entity to get all records created, updated,
-or removed in a certain transaction, and so that in time order those transactions can be reproduced remotely
+The four fields (lastUpdatedStamp, lastUpdatedTxStamp, createdStamp, createdTxStamp) are added to each entity and
+automatically populated so that queries can be done on each entity to get all records created, updated,
+or removed in a certain transaction, and so that in time order those transactions can be reproduced remotely
 to get the data into the remote database in the proper order.
 
-The no-auto-stamp attribute is used to tell the Entity Engine not to automatically add these stamp fields,
-and not to automatically set the stamps when creating and updating the entities. It's false by default.
-So by default these values will be automatically set, and when records are removed the primary key will be saved
-in the EntitySyncRemove entity's table so that the record can be removed in the remote database.
+The no-auto-stamp attribute is used to tell the Entity Engine not to automatically add these stamp fields,
+and not to automatically set the stamps when creating and updating the entities. It's false by default.
+So by default these values will be automatically set, and when records are removed the primary key will be saved
+in the EntitySyncRemove entity's table so that the record can be removed in the remote database.