CapabilityProtocols & APIsJava, read from its artifacts

OData

Serving a model as OData — V4, which CAP generates by default from CDS, and V2 for the clients that cannot move: older Fiori applications, SAPUI5 smart controls and integrations built against V2.

Showing artifacts, examples and content with confirmed Java applicability. View All CAP

Overview

SAP SHIPS
com.sap.cds:cds-adapter-odata-v2

Serves the OData V2 protocol natively inside the CAP Java runtime, mapping inbound V2 requests onto CQN events so an existing V2 frontend keeps working against the same model.

com.sap.cds:cds-adapter-odata-v4

Auto-exposes every Application Service in the CDS model as an OData V4 endpoint, mapping inbound requests onto CQN events for the CAP Java runtime to process.

A Java coverage assessment has not been written. View all flavors

THE COMMUNITY ADDS

A Java coverage assessment has not been written. View all flavors

Artifacts3

3 of 3 artifacts
ArtifactSignals
Build tools1
@root3287/cap-segwCompiler from a CDS service to SEGW model and data provider classes
Signals
Functional boundary
Packages2
com.sap.cds:cds-adapter-odata-v2OData V2 protocol adapter built into the CAP Java runtime
Signals
none
com.sap.cds:cds-adapter-odata-v4OData V4 protocol adapter for CAP Java Application Services
Signals
none

Seen working1

ArtifactSignals
Samples1
fiori-invoke-functionCalling an unbound CAP Java function from freestyle UI5
No license

Details

Coverage
statecore and community, CAP, Java, derived
also inABAP
Comparison properties1

These are the questions used to compare what the artifacts do. Values come from their documentation and may apply to a particular ecosystem or runtime. Each recorded value in the comparison opens its statement and sources.

Protocols
For your agent