You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<em>abap2UI5 – HTML created in browser based on XML View and Data, both sent from the backend</em>
89
87
</p>
90
88
91
-
The UI5 application remains a single-page application (SPA), but its role changes: it solely creates HTML for server-defined views and data.
89
+
The UI5 application remains a single-page application, but its role changes: it now focuses solely on creating HTML based on views and data provided by the server.
92
90
93
91
#### Frontend Events on the Server
94
92
@@ -104,23 +102,23 @@ When a user triggers an event (e.g., pressing a button), the event information i
104
102
<em>abap2UI5 – Simple shell app, backend handles all logic</em>
105
103
</p>
106
104
107
-
In standard UI5 freestyle applications, each app requires its own dedicated set of frontend artifacts:
105
+
As a result, the frontend becomes a static UI5 shell shared across all applications. Views and logic are fully defined and maintained in the backend and each application is represented by backend ABAP class that generates the view and handles events. Every UI5 app becomes a complete ABAP backend project managed through abapGit — eliminating the need for separate frontend deployments entirely:
<em>UI5 freestyle – Each application requires its own set of deployed UI and App artifacts</em>
110
+
<em>abap2UI5 – Shared shell app, with each application defined by backend artifacts only</em>
113
111
</p>
114
112
115
-
With abap2UI5, the frontend becomes a static UI5 shell shared across all applications. Views and logic are fully defined and maintained in the backend. Each application is represented by a single ABAP class that generates the view and handles events:
113
+
In contrast to that in conventional UI5 freestyle applications, each app requires its own dedicated set of frontend artifacts:
<em>abap2UI5 – Shared shell app, with each application defined by backend artifacts only</em>
118
+
<em>UI5 freestyle – Each application requires its own set of deployed UI and App artifacts</em>
121
119
</p>
122
120
123
-
As a result, every UI5 app becomes a complete ABAP backend project managed through abapGit — eliminating the need for separate frontend deployments entirely.
121
+
This leads to additional deployment effort during both development and go-live.
0 commit comments