Skip to Content

Changes for page Remove Namespace

Last modified by Erik Bakker on 2024/05/07 10:30
From version 2.1
edited by Erik Bakker
on 2022/04/29 15:18
Change comment: There is no comment for this version
To version 18.1
edited by Erik Bakker
on 2023/01/31 12:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -REST - Request & Response
1 +Remove Namespace
Content
... ... @@ -1,33 +1,29 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 -(((1. How to use
4 -With this store component, you can easily set up a connection to a REST endpoint using various authentication mechanisms while taking the response into account.
3 +(((
4 +== About ==
5 +With the help of this transformation, you can easily remove a namespace from your message. This is sometimes needed to process the message properly.
5 5  
6 -2. Keynotes & restrictions
7 -Note that you need to select the valid authentication based on the requirement of the external system.
7 +== Documentation ==
8 8  
9 -3. License Information
10 -Part of the standard license agreement as agreed upon when using the store for the first time.
9 +==== 1. How to use====
10 +With the help of this transformation, you can easily remove a namespace from your message. This is sometimes needed to process the message properly.
11 11  
12 -4. Relevant eMagiz Academy Microlearnings
13 -https://emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index
12 +==== 2. Keynotes & restrictions====
14 14  
15 - Would you please consult the privacy policy of eMagiz at the following link: https://www.emagiz.com/privacy-policy/
16 -]])))
14 +* Note that this is a custom XSLT that is designed for a specific cause.
15 +* Always try to understand the context before you implement this transformation.
16 +* This will lead to an attribute name clash if an element contains two attributes with the same local name but a different namespace prefix.
17 +* Nodes that cannot have a namespace are copied as such.
17 17  
19 +==== 3. License Information====
20 +Part of the standard license agreement as agreed upon when using the store for the first time.
18 18  
22 +==== 4. Relevant eMagiz Academy Microlearnings====
19 19  
20 -((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %)
21 -|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option
22 -|(% style="width:45px" %) a|(% style="width:241px" %) OAuth 2.0 - Authorization Code
23 -|(% style="width:45px" %) b|(% style="width:241px" %) REST - Basic Auth
24 -|(% style="width:45px" %) c|(% style="width:241px" %) REST - Client Certificate
25 -|(% style="width:45px" %) d|(% style="width:241px" %) REST - Header Mapper
26 -|(% style="width:45px" %) e|(% style="width:241px" %) OAuth 2.0 - Client Credentials
27 -|(% style="width:45px" %) f|(% style="width:241px" %) REST - SSL
28 -|(% style="width:45px" %) g|(% style="width:241px" %) Dynamic Token
29 -|(% style="width:45px" %) h|(% style="width:241px" %) Token
30 -|(% style="width:45px" %) i|(% style="width:241px" %) No Authentication (Fire & Forget)
31 -)))
24 +None
25 +
26 +//Would you please consult the privacy policy of eMagiz at the following [[link>>https://www.emagiz.com/privacy-policy/||target="blank"]])))
27 +((()))
32 32  {{/container}}
33 33  {{/container}}