com.sap.cds:cds-adapter-odata-v2
The OData V2 protocol adapter for CAP Java, which the runtime serves natively once this beta module is on the classpath, so a V2 frontend keeps working without a change to the CDS model.
Maps inbound OData V2 requests onto CQN events for the CAP Java runtime, so a frontend still built against V2 keeps working without a change to the CDS model behind it. capire calls the support native to CAP Java: on Node.js the same job needs @cap-js-community/odata-v2-adapter@cap-js-community/odata-v2-adapterExposes a CAP service as OData V2 for clients that cannot move to V4.community org, cap installed separately, while here the runtime serves V2 itself once this module is on the classpath. Its version comes from com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, cap; added to srv/pom.xml with runtime scope, it also needs a matching .cdsrc.json change (odata.version: v2) so the CDS compiler emits V2 EDMX, and by default it serves each Application Service under /odata/v2/<Service>. OData V4 stays the default protocol, capire marks this adapter Beta, and a service can run both at once through the @protocols annotation.
Facts
What it declares
Every artifact
- Type
- Package
- Origin
- By SAP
- Runtime
- Java
As a package
- Where it runs
- does not say
- Distributed through
- does not say
Connections
Exposing data and operations through OData
Download
Others providing
Compare all 7 on the OData page →- com.sap.cds:cds-adapter-odata-v4com.sap.cds:cds-adapter-odata-v4The OData V4 protocol adapter for CAP Java, auto-exposing every Application Service in the model at /odata/v4/<Service> without protocol code of its own, active by default in the CDS Maven Archetype.sap official, capOData V4 protocol adapter for CAP Java Application Services
- @cap-js-community/odata-v2-adapter@cap-js-community/odata-v2-adapterExposes a CAP service as OData V2 for clients that cannot move to V4.community org, capExposes a CAP service as OData V2
- @odatano/core@odatano/coreA CAP plugin that serves the Cardano blockchain as OData V4, giving enterprise-shaped access to a public chain, funded through Cardano Catalyst.independent, capCAP plugin serving the Cardano blockchain as OData V4
- @odatano/nightgate@odatano/nightgateIndexes the Midnight blockchain and submits transactions to it from CAP, exposed as OData V4, with command-line tools for schema deltas, key rotation and migration.independent, capCAP plugin indexing the Midnight blockchain, exposed as OData V4
- @root3287/cap-segw@root3287/cap-segwA CAP build tool that compiles a CDS service into the ABAP Model Provider and Data Provider classes a SAP Gateway SEGW project expects, for OData V4 by default or V2.independent, capCompiler from a CDS service to SEGW model and data provider classes
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtime
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
“OData V2 adapter for CDS Services Java” — com.sap.cds:cds-adapter-odata-v2 — Maven POM
History in the atlas
- 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.
- First seen.
For your agent
- Ref
artifact:cap-java-cds-adapter-odata-v2- JSON
- /artifacts/cap-java-cds-adapter-odata-v2.json
- MCP
- Connecting an agent