Everything in the atlas
Type
Domain: Protocols & APIs
Origin
Signals
More: 2
Group by: Capability
Maven bill of materials pinning CAP Java module versions
Ten short CAP Java references, one document per topic
Generates Open Resource Discovery documents from a CAP Java model
Compiler from a CDS service to SEGW model and data provider classes
The generated files are copied or deployed into the ABAP system by hand, the fourth step of its own usage list, so nothing keeps an activated service in step with the model it was generated from. Its peer dependency is `@sap/cds` ^9.8, so it does not install into a project on an earlier CAP release.
OData V2 protocol adapter built into the CAP Java runtime
OData V4 protocol adapter for CAP Java Application Services
Calling an unbound CAP Java function from freestyle UI5
Neither the package manifest nor the repository tree declares a licence.
CAP Java service calling role collection APIs via a generated client
Neither the package manifest nor the repository tree declares a licence.
Maven bill of materials pinning CAP Java module versions
Eclipse plug-in turning JSON or XML into ABAP types and DDIC objects
On an [SAP BTP ABAP environment](artifact:btp-abap-environment) system only the generated code is left: DDIC creation is not supported on ABAP Cloud, because classic DDIC object creation over REST is not available there. Create DDIC is also disabled where ADT is not installed in the same Eclipse, and Insert into Editor then works with any editor implementing `ITextEditor` instead of the ABAP one.
MCP adapter turning a CAP Java service into an MCP server
SAP prohibits gateway/proxy use for SAP Application APIs; the Atlas separately excludes CAP wrappers around those APIs from its assessed scope. Data changes require application-defined unbound actions, and the adapter supplies no rate limiting, agent-action audit logging, approval workflows or policy enforcement.