Changes for page Multipart form-data

Summary

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

Details

Page properties

Content

...	...	@@ -33,19 +33,6 @@
33	33
34	34	On top of that we need to define the contentType header as follows.
35	35
36		-[[image:Main.Images.Microlearning.WebHome@expert-data-handling-multipart-form-data--content-type-header-config.png]]
37		-
38		-After you have set the stage you can use a standard transformer component to build your message in the correct manner. To build it correctly you need to take the following into account:
39		-
40		-* Each part of the message needs to be seperated by a boundary
41		-* The message needs to start with a boundary and finish with a boundary
42		-* Line breaks are needed to differentiate between the boundary and the text content
43		-* No line break is needed when the content is not text based
44		-
45		-Given all this you can write the following SpEL expression that will yield a desirable output:
46		-
47		-{{code}}test{{/code}}
48		-
49	49	Most users would think that communication via queues to connect two separate eMagiz models is a bright idea. However, this is something that we do not encourage. We discourage this for several practical and technical reasons alike.
50	50
51	51	When looking at the practical side of things getting it configured correctly is time-consuming and an error-prone action (as is evident by the question). Furthermore, it can lead to unexpected situations where you make a typo to listen to a queue on which no messages are provided. This queue will, however, be registered on the JMS level (when you activate the flow in question with the custom configuration), which can lead to confusing queue statistics and even more troublesome false-positive alerting based on missing queue metrics or missing consumers.