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
Copy file name to clipboardExpand all lines: docs/advanced/technical/over_the_wire.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
-
# The Key Concept: UI5 Over-the-Wire
1
+
# Key Concept: UI5 Over-the-Wire
2
2
3
-
The core principle of **abap2UI5** is to apply the proven **Over-the-Wire** concept to SAP UI5 application development.
3
+
The key concept of **abap2UI5** is to apply the **HTML Over-the-Wire** concept to SAP UI5 application development.
4
4
5
-
**Over-the-Wire** refers to a web architecture where the server renders user interfaces and sends ready-to-use HTML fragments to the browser. This avoids complex client-side frameworks and keeps the frontend lightweight and maintainable.
5
+
**HTML Over-the-Wire** refers to a web architecture where the server renders user interfaces and sends ready-to-use HTML fragments to the browser. This avoids complex client-side frameworks and keeps the frontend lightweight and maintainable.
6
6
7
7
While popular frameworks like Hotwire, Livewire, and Phoenix LiveView follow this approach, **abap2UI5 adapts it to SAP’s technological environment**, using SAP UI5 for frontend rendering and ABAP for backend-driven UI definitions.
8
8
@@ -12,8 +12,8 @@ While popular frameworks like Hotwire, Livewire, and Phoenix LiveView follow thi
- Backend-controlled UI logic and state management
68
68
- Targeted ViewModel updates ensure that only specific UI5 controls are re-rendered
69
69
70
70
#### Key Benefits and Characteristics
71
-
- Static UI5 Frontend: Delivered once, remaining generic and stable.
72
-
- Backend-Driven UI Control: All UI structures, logic, and dynamic behavior are defined and maintained in ABAP.
73
-
- Pure ABAP Development: No need for custom JavaScript or separate frontend development.
74
-
- Simplified Architecture: No frontend builds, no complex SPA frameworks — everything managed through backend artifacts.
75
-
- Seamless SAP Integration: Fully aligned with SAP’s UI5 and ABAP technology stack, compatible with ERP and S/4HANA releases.
71
+
- Static UI5 Frontend App: Delivered tieh the first HTTP request, remaining generic and stable for all apps
72
+
- Backend-Driven UI Control: All UI definitions and business logic is defined in ABAP classes
73
+
- Pure ABAP Development: No need for custom JavaScript or separate frontend development
74
+
- Simplified Architecture: No frontend builds, no complex SPA frameworks — everything managed through backend artifacts with abapGit and transports
75
+
- Seamless SAP Integration: Fully aligned with SAP’s UI5 and ABAP technology stack, compatible with all ERP and S/4HANA releases
76
76
- Efficient for Business Applications: Especially suitable for CRUD-heavy apps, forms, tables, dashboards, and typical enterprise use cases.
77
77
78
78
#### Limitations to Consider
@@ -83,7 +83,7 @@ Several frameworks successfully implement this pattern:
83
83
84
84
### Summary
85
85
86
-
The **key idea of abap2UI5** is to bring the simplicity and efficiency of the Over-the-Wire pattern into the SAP ecosystem.
86
+
The **key concept of abap2UI5** is to bring the simplicity and efficiency of the HTML Over-the-Wire pattern into the SAP ecosystem.
87
87
88
88
By shifting UI control back to the ABAP backend and leveraging SAP UI5 for rendering, abap2UI5 enables maintainable, pragmatic business applications — without the overhead of SPA architectures.
0 commit comments