In this session we will talk about the UI code requests when open a Fiori app.
The sample below is from https://sapui5.hana.ondemand.com/#docs/guide/8f93bf2b2b13402e9f035128ce8b495f.html
The file structure of a simplest SAPUI5 app looks like:
And the XHRs triggered when access this app is:
As you can see, there are some “404” failed requests. They are NOT bugs.
The SAPUI5 core framework will request for “Componnet-preloiad.js”, which is generally the conbination of various kinds of files, such as view.xml, controller.js, .properties, etc..
If this request failed, the framework will multiple request for concrete files sperately, such as .js files, .xml files, .properties files, etc..
As you can see, Component-preload.js can save the performance.
But in a “real” Fiori application, the requests looks like:
As you can see, Component-preload.js is returned successfully and hence there is no further request for other files such as xml, js, .properties, etc..
There is a special program which generates this file in the server side.