ui5-cap-serverside-rendering-demo
The demo project the ui5-cap-serverside-rendering-pluginui5-cap-serverside-rendering-pluginA CAP plugin that fills UI5 views and fragments with entity data on the server through Handlebars and streams them as XML, and renders a Vue app to HTML on a route of its own.independent, cap README points to: a CAP bookshop whose Books list and detail views sit in srv/views and reach the browser already filled with data.
db/schema.cds extends Books with the plugin's ServerSideRendering aspect and annotates it @(ServerSideRenderingType:'view'), and srv/cat-service.cds exposes it read-only through CatalogService. The two files under srv/views are ordinary UI5 XML with Handlebars where the bindings would be: {{#each Books}} around a StandardListItem titled {{title}} - {{ID}}, so what the server returns is the markup itself. On the app side, a TypeScript freestyle app under app/serverside-rendering ships no list or detail view of its own: its manifest sets routerClass to be.wl.serversiderendering.library.ServerSideRouter and gives each route a url such as /odata/v4/catalog/Books({id})/content, and the controller navigates by reading the ID the list item wrote into the DOM as CustomData. That router class is not in the repository: the app's package.json depends on the npm package be.wl.serversiderendering.library for it.
Facts
Where it sits
Who is behind it
In the atlas: maintains 25, contributes to 39, wrote 12@lemaiwomaintainer
Before choosing this
Signals
LicenceNo licenseNeither the package manifest nor the repository tree declares a licence
Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.
Conditions
PracticalFunctional boundary
As a deployment template it stops at the service: the mta.yaml has one module, gen/srv on the Node.js buildpack, and no HTML5 repository or router module for the app.
What it declares
Every artifact
- Type
- Sample
- Origin
- Independently maintained
- Use as
- A reference
- Runtime
- Node.js
- Runs on
- Cloud Foundry
As a sample
- Type declarations
- declared
- Form
- does not say
Connections
CAP Node.js runtime
Command line client and development toolkit for CAP
UI5 CLI middlewares running inside the CDS server
CAP plugin rendering UI5 views with entity data on the server
SQLite database service for CAP, in memory during development
Download
README
quoted from lemaiwo/ui5-cap-serverside-rendering-demo, readGetting Started
Welcome to your new project.
It contains these folders and files, following our recommended project layout:
| File or Folder | Purpose |
|---|---|
app/ | content for UI frontends goes here |
db/ | your domain models and data go here |
srv/ | your service models and code go here |
package.json | project metadata and configuration |
readme.md | this getting started guide |
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
Flavors
“|**App Generator**<br>@sap/generator-fiori-freestyle|” — ui5-cap-serverside-rendering-demo — app/serverside-rendering README, application details
History in the atlas
- First seen.
For your agent
- Ref
artifact:lemaiwo-ui5-cap-serverside-rendering-demo- JSON
- /artifacts/lemaiwo-ui5-cap-serverside-rendering-demo.json
- MCP
- Connecting an agent