[camel] branch master updated: Convert external links to AsciiDoc (#4062)

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[camel] branch master updated: Convert external links to AsciiDoc (#4062)

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

acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/master by this push:
     new 81a965a  Convert external links to AsciiDoc (#4062)
81a965a is described below

commit 81a965a5f9d018ee135353fcd760a6447cfd1ec6
Author: yuri <[hidden email]>
AuthorDate: Fri Jul 31 17:04:57 2020 +0200

    Convert external links to AsciiDoc (#4062)
---
 docs/components/modules/dataformats/pages/asn1-dataformat.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/components/modules/dataformats/pages/asn1-dataformat.adoc b/docs/components/modules/dataformats/pages/asn1-dataformat.adoc
index 8dec893..d794393 100644
--- a/docs/components/modules/dataformats/pages/asn1-dataformat.adoc
+++ b/docs/components/modules/dataformats/pages/asn1-dataformat.adoc
@@ -10,7 +10,7 @@
 
 *Since Camel {since}*
 
-The ASN.1 Data Format Data Format [Intoduction to ASN.1](https://www.itu.int/en/ITU-T/asn1/Pages/introduction.aspx) is a Camel Frameworks's data format implementation based on Bouncy Castle's bcprov-jdk15on library and jASN.1's java compiler for the formal notation used for describing data transmitted by telecommunications protocols, regardless of language implementation and physical representation of these data, whatever the application, whether complex or very simple. Messages can be u [...]
+The ASN.1 Data Format (https://www.itu.int/en/ITU-T/asn1/Pages/introduction.aspx[Intoduction to ASN.1]) is a Camel Frameworks's data format implementation based on Bouncy Castle's bcprov-jdk15on library and jASN.1's java compiler for the formal notation used for describing data transmitted by telecommunications protocols, regardless of language implementation and physical representation of these data, whatever the application, whether complex or very simple. Messages can be unmarshalled  [...]
 
 == ASN.1 Data Format Options
 
@@ -50,7 +50,7 @@ from("direct:unmarshal").unmarshal(asn1).split(body(Iterator.class)).streaming()
 -----------------------------------------------------------------------
 
 In the last example we unmarshal BER file payload to plain old Java Objects using Split EIP. The reason for applying Split EIP is already mentioned in the previous example. Please note and keep in mind that reason. In such example we also need to set the fully qualified name of the class or <YourObject>.class reference through data format.
-The important thing to note here is that your object should have been generated by jasn1 compiler which is a nice tool to generate java object representations of your ASN.1 structure. For the reference usage of jasn1 compiler see [JASN.1 Project Page](https://www.beanit.com/asn1/) and please also see how the compiler is invoked with the help of maven's exec plugin.
+The important thing to note here is that your object should have been generated by jasn1 compiler which is a nice tool to generate java object representations of your ASN.1 structure. For the reference usage of jasn1 compiler see https://www.beanit.com/asn1/[JASN.1 Project Page] and please also see how the compiler is invoked with the help of maven's exec plugin.
 For example, in this data format's unit tests an example ASN.1 structure(TestSMSBerCdr.asn1) is added in `src/test/resources/asn1_structure`. jasn1 compiler is invoked and java object's representations are generated in `$\{basedir\}/target/generated/src/test/java`
 The nice thing about this example, you will get POJO instance at the mock endpoint or at whatever your endpoint is.