Changes for page Validation

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.dfirdausy
	1	+XWiki.ebakker

Content

...	...	@@ -1,5 +1,5 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
2		-In the previous microlearning session, we covered how to configure a REST service. Now, we will focus on validating the data structure of incoming messages to ensure they meet the required format. This includes how to handle errors when validation fails and how to notify the client about these issues. By the end of this microlearning, you’ll understand how to implement validation for REST endpoints effectively
	2	+In the previous microlearning, we learned how to configure a REST service. In this microlearning, we will discuss how you can validate whether the party calling your REST endpoint is sending the correct information in terms of the structure of the message. We will also learn how you can subsequently report back to the client that a validation error occurred.
3	3
4	4	Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5	5
...	...	@@ -10,11 +10,12 @@
10	10	== 2. Key concepts ==
11	11
12	12	This microlearning centers around validating incoming messages when hosting a REST web service.
13		-* With REST, we mean: A web service that adheres to the RESTful principles.
14		-* With validation, we mean: Verifying whether the data structure we received is valid according to our definition.
	13	+With REST, we mean: A web service that adheres to the RESTful principles
	14	+With validation, we mean: Verifying whether the data structure we received is valid according to our definition
	15	+
15	15	* The external application pushes data to a REST web service (or API) hosted by eMagiz
16		-** When doing so, the external application should adhere to the defined data structure
17		-** If not, we need to refuse the call and respond with an error message
	17	+* When doing so, the external application should adhere to the defined data structure
	18	+* If not, we need to refuse the call and respond with an error message
18	18
19	19	== 3. Validation ==
20	20
...	...	@@ -36,23 +36,26 @@
36	36
37	37	if (exists(//err:xml-validation-exception)) then 'validation' else if (exists(//err:exception[@class='org.springframework.integration.MessageTimeoutException'])) then 'timeout' else ''
38	38
39		-== 4. Key takeaways ==
	40	+== 4. Assignment ==
40	40
41		-* External applications must follow the defined data structure when sending information to a REST web service (or API) hosted by eMagiz.
42		-* If the incoming data does not meet the required structure, the request should be rejected, and an appropriate error message should be sent back to the client.
43		-* eMagiz automatically handles much of the validation process when using the API Gateway, simplifying error management and reporting.
44		-* For messaging flows, additional configuration is needed to replicate the same validation and error-handling functionality.
	42	+Navigate to a flow within your (Academy) project in which you host a REST Webservice.
	43	+Ensure that when a validation error is thrown, eMagiz will return a proper response to the client.
	44	+This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
45	45
46		-== 5. Suggested Additional Readings ==
	46	+== 5. Key takeaways ==
47	47
48		-If you are interested in this topic and want more information on it please read the help text provided by eMagiz when executing these actions and read the following links:
	48	+* The external application pushes data to a REST web service (or API) hosted by eMagiz
	49	+* When doing so, the external application should adhere to the defined data structure
	50	+* If not, we need to refuse the call and respond with an error message
	51	+* eMagiz auto generates a lot when using the API Gateway
	52	+* You need to recreate this when using the same functionality in a messaging flow
49	49
50		-* [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
51		-** [[Crash Course Messaging (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.WebHome||target="blank"]]
52		-*** [[Filter (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-filter||target="blank"]]
53		-* [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
54		-** [[REST Connectivity (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.REST Connectivity.WebHome||target="blank"]]
55		-*** [[Configuration REST web service (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.REST Connectivity.intermediate-rest-webservice-connectivity-configuration-gen3.WebHome||target="blank"]]
56		-* [[Host REST web service (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&l_space_facet=10&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22host+REST+web+service%22||target="blank"]]
	54	+== 6. Suggested Additional Readings ==
57	57
	56	+If you are interested in this topic and want more information, please read the help text provided by eMagiz.
	57	+
	58	+== 7. Silent demonstration video ==
	59	+
	60	+Please check out the store for a working example for a messaging solution.
	61	+
58	58	)))((({{toc/}}))){{/container}}{{/container}}