Skip to Content

Changes for page XPath - SpEL

Last modified by Erik Bakker on 2023/01/31 12:10
From version 5.1
edited by Erik Bakker
on 2022/05/02 08:20
Change comment: There is no comment for this version
To version 18.1
edited by Erik Bakker
on 2022/05/02 12:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -SOAP Web service Connectivity
1 +Restore Payload - SpEL
Content
... ... @@ -1,40 +1,30 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 -= About =
5 -This store element will allow you to create an easy connection to SOAP based web services. XML data can be send to these web services, and for each connectivity type there is a Flow Fragment available.
4 +== About ==
5 +With the help of this SpEL expression, you can easily restore the payload from a header so it can be used for further processing.
6 6  
7 -= Documentation =
7 +== Documentation ==
8 8  
9 - **~1. How to use**
10 -Ensure to locate the right connectivity method and import the right flow fragment.
9 +==== 1. How to use====
10 +With the help of this SpEL expression, you can easily restore the payload from a header so it can be used for further processing.
11 11  
12 -**2. Keynotes & restrictions **
12 +==== 2. Keynotes & restrictions====
13 13  
14 -a. These flow fragments will contain only the eMagiz components to make a call out to the SOAP based webservice - These components do not hold any system messages - The basic authentication flow fragment requires empty key and trust store that are to be added separately. These are not included in this store component.
14 +* Note that this is an example of how you can use the SpEL expression within eMagiz.
15 +* The key element of this SpEL expression is that it allows you to restore the original payload at any given moment in the flow (assuming you stored it previously).
15 15  
16 -**3. License Information**
17 +==== 3. License Information====
17 17  Part of the standard license agreement as agreed upon when using the store for the first time.
18 18  
19 -**4. Relevant eMagiz Academy Microlearnings**
20 -[[https:~~/~~/emagiz.github.io/docs/microlearning/novice-soap-webservice-connectivity-authorization-calling-a-soap-webservice>>url:https://emagiz.github.io/docs/microlearning/novice-soap-webservice-connectivity-authorization-calling-a-soap-webservice]]
20 +==== 4. Relevant eMagiz Academy Microlearnings====
21 21  
22 +[[https:~~/~~/emagiz.github.io/docs/microlearning/advanced-data-handling-spel-expressions>>url:https://emagiz.github.io/docs/microlearning/advanced-data-handling-spel-expressions]]
22 22  
23 -Would you please consult the privacy policy of eMagiz at the following link: [[https:~~/~~/www.emagiz.com/privacy-policy/?>>url:https://www.emagiz.com/privacy-policy/?]])))
24 +//Would you please consult the privacy policy of eMagiz at the following link:// [[https:~~/~~/www.emagiz.com/privacy-policy/?>>url:https://www.emagiz.com/privacy-policy/?]])))
24 24  
25 25  
26 26  
27 -((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %)
28 -|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option
29 -|(% style="width:45px" %) a|(% style="width:241px" %) Basic Authentication
30 -|(% style="width:45px" %) b|(% style="width:241px" %) WS Addressing - Call back
31 -|(% style="width:45px" %) c|(% style="width:241px" %) Client certificate
32 -|(% style="width:45px" %) d|(% style="width:241px" %) Mapped headers
33 -|(% style="width:45px" %) e|(% style="width:241px" %) Token based - static
34 -|(% style="width:45px" %) f|(% style="width:241px" %) Token based - dynamic
35 -|(% style="width:45px" %) g|(% style="width:241px" %) SSL
36 -|(% style="width:45px" %) h|(% style="width:241px" %) No authentication
37 -|(% style="width:45px" %) i|(% style="width:241px" %) Dynamic URL
38 -)))
28 +((()))
39 39  {{/container}}
40 40  {{/container}}