This is an automated email from the ASF dual-hosted git repository.
jamesnetherton pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 8351d9c Remove serializable messages section from camel-hl7 docs
8351d9c is described below
commit 8351d9c7e9c29d2980d3112bd26edba75b5df12d
Author: James Netherton <[email protected]>
AuthorDate: Tue May 11 09:56:35 2021 +0100
Remove serializable messages section from camel-hl7 docs
---
.../resources/org/apache/camel/catalog/docs/hl7-dataformat.adoc | 7 -------
components/camel-hl7/src/main/docs/hl7-dataformat.adoc | 7 -------
docs/components/modules/dataformats/pages/hl7-dataformat.adoc | 7 -------
3 files changed, 21 deletions(-)
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/hl7-dataformat.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/hl7-dataformat.adoc
index 2c7ad13..38b5eb8 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/hl7-dataformat.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/hl7-dataformat.adoc
@@ -264,13 +264,6 @@ a byte stream and put on a JMS queue. +
Here we unmarshal the byte stream into a HAPI Message object that is
passed to our patient lookup service.
-=== Serializable messages
-
-As of HAPI 2.0, the HL7v2 model classes are fully
-serializable. So you can put HL7v2 messages directly into a JMS queue
-(i.e. without calling `marshal()` and read them again directly from the
-queue (i.e. without calling `unmarshal()`.
-
=== Segment separators
Unmarshalling does not automatically fix segment
diff --git a/components/camel-hl7/src/main/docs/hl7-dataformat.adoc
b/components/camel-hl7/src/main/docs/hl7-dataformat.adoc
index 2c7ad13..38b5eb8 100644
--- a/components/camel-hl7/src/main/docs/hl7-dataformat.adoc
+++ b/components/camel-hl7/src/main/docs/hl7-dataformat.adoc
@@ -264,13 +264,6 @@ a byte stream and put on a JMS queue. +
Here we unmarshal the byte stream into a HAPI Message object that is
passed to our patient lookup service.
-=== Serializable messages
-
-As of HAPI 2.0, the HL7v2 model classes are fully
-serializable. So you can put HL7v2 messages directly into a JMS queue
-(i.e. without calling `marshal()` and read them again directly from the
-queue (i.e. without calling `unmarshal()`.
-
=== Segment separators
Unmarshalling does not automatically fix segment
diff --git a/docs/components/modules/dataformats/pages/hl7-dataformat.adoc
b/docs/components/modules/dataformats/pages/hl7-dataformat.adoc
index 8000cd1..72a641b 100644
--- a/docs/components/modules/dataformats/pages/hl7-dataformat.adoc
+++ b/docs/components/modules/dataformats/pages/hl7-dataformat.adoc
@@ -266,13 +266,6 @@ a byte stream and put on a JMS queue. +
Here we unmarshal the byte stream into a HAPI Message object that is
passed to our patient lookup service.
-=== Serializable messages
-
-As of HAPI 2.0, the HL7v2 model classes are fully
-serializable. So you can put HL7v2 messages directly into a JMS queue
-(i.e. without calling `marshal()` and read them again directly from the
-queue (i.e. without calling `unmarshal()`.
-
=== Segment separators
Unmarshalling does not automatically fix segment
