Everything in CAP / Java
Type: 4
Domain
Origin
Signals
Java: Answers in Java
More
Group by: Capability
Distributed through
Form
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.
CAP Java reuse package for Airlines, Airports and Flights data
SAP's relational database platform, on-premise and in HANA Cloud
For provisioning a managed database on BTP, see [SAP HANA Cloud](artifact:btp-hana-cloud). Features differ between HANA versions; an on-premise deployment and a cloud instance are not interchangeable without compatibility checks.
Developer-centric command line for SAP HANA
Fork of cds-dbm with deploy, load, diff and drop tasks
Release and repository quiet for 39 months.
App-to-app setups between CAP Java and CAP Node.js under AMS and IAS
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.
CAP Java service consuming a Business Partner API mocked in Node.js
Neither the package manifest nor the repository tree declares a licence.
Developer-centric command line for SAP HANA
Agent skills for CAP development, each a SKILL.md with references
SAP's capire/skills packaged for the pi coding agent
If your tool reads the open skill standard directly, install [capire/skills](artifact:capire-skills) and skip the wrapper.
CAP review skill for coding agents with gates and prohibitions
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary There is no licence, so there is no grant to use or redistribute it. Everything else is secondary to that. Note too that its 'verified' claim means the skill text was checked against itself by an evaluation suite — not that the advice was run against a CAP version.
Agent skills for CAP development, each a SKILL.md with references
SAP skills for the Kiro IDE
Host-specific: outside Kiro the automatic context activation is the part that does not come with it, and what remains is prose you would have to wire in yourself. Breadth over depth by design — thirty-five skills across six product areas is an orientation layer, not a substitute for the focused sets in each.
Agent skill for SAP Customer Experience APIs, CDS and errors
Forty SAP development plugins for coding agents
GPL-3.0, which is a licence to read before vendoring any of it into something you ship. Forty plugins is also a lot of always-available surface — the ledger is there because breadth and verification pull in opposite directions, and it does not resolve that so much as report it.
CLI for Joule digital assistants and Joule Studio solutions
Pro-code CLI for building and deploying Joule Studio solutions
Skill assessing API usage against the SAP API Policy
It says so itself, in bold, and the atlas repeats it: not legal advice and not a compliance decision. Only SAP, your contract, or SAP support can answer bindingly, and the skill routes legal, commercial and roadmap questions there rather than guessing at them. Treat the output as evidence gathered, not as a verdict.
App-to-app setups between CAP Java and CAP Node.js under AMS and IAS
Neither the package manifest nor the repository tree declares a licence.
App-to-app setups between CAP Java and CAP Node.js under AMS and IAS
Neither the package manifest nor the repository tree declares a licence.
CAP Java authorization checks tried case by case
Neither the package manifest nor the repository tree declares a licence.
Groups npm audit findings by root dependency, with failing thresholds
It audits through npm: a project that resolves its dependencies with another package manager, or has no `package.json`, has nothing for it to run. What it reports is what `npm audit` knows, so a vulnerability outside the npm advisory data is not in its table.
Shows which feature branches reached which environment branch
A team that does not keep one long-lived branch per environment has no environment branches for it to compare feature branches against. What it reports is the merge state of branches in Git, so it says nothing about whether a merged change has been built or deployed to the environment.
Groups npm audit findings by root dependency, with failing thresholds
It audits through npm: a project that resolves its dependencies with another package manager, or has no `package.json`, has nothing for it to run. What it reports is what `npm audit` knows, so a vulnerability outside the npm advisory data is not in its table.
Consumer side of a CAP Java parent pom promotion model with Renovate
Neither the package manifest nor the repository tree declares a licence.
Maven parent pom pinning cds-services-bom and Spring Boot for CAP Java
Neither the package manifest nor the repository tree declares a licence.
Endpoint discovery for CAP services deployed to Cloud Foundry
Static end-to-end tracer of one CAP operation across repositories
Attaches a debugger to a CAP app running on Cloud Foundry
Workspace-wide CSN cache for querying CAP entities and columns
Command line for changing features of an existing Fiori project
Regex naming rules for SAP HANA artifacts in a CAP project
Everything it checks is a name: a file name under `rootDir`, or an identifier a parser extracted from a file, so a convention that cannot be written as a regex over one name has no rule shape here. Content rules targeting `.hdbanalyticalprivilege` or `.hdbconstraint` return no results, which the README states as not yet implemented, so conventions centred on those two artifact types go unchecked.
CLI of CAP development tools for Cloud Foundry workflows
There is no repository and no README: what the eight commands do is only readable from the compiled dist that ships in the package. Three of them — npmrc, install, project — are written for "SimpleMDG" projects rather than for CAP generally, so the reusable part is bind-local, run-local and debug. Seven releases up to July 2026. Its binding step writes the resolved VCAP_SERVICES into default-env.json in the project, where [@sap/cds-dk](artifact:sap-cds-dk) keeps only the place the credentials can be fetched from, so a project using it needs that file kept out of version control.
CAP Java service consuming a Business Partner API mocked in Node.js
Neither the package manifest nor the repository tree declares a licence.
pnpm workspace running CAP, a local launchpad and two UI5 apps
Neither the package manifest nor the repository tree declares a licence.
AWK script sketching an ER diagram from .cds files
No published releases; repository quiet for 26 months.
Static check that each exported TypeScript function has a test
It reads TypeScript exports only; a project written in plain JavaScript has no exported functions for it to extract. A call to the function name in a test file counts as tested, and a call through property access such as `.foo(` does not.
Terminal UI running Bruno collections against a CAP service
CAP Java draft cancel on composition items as a flag update
Neither the package manifest nor the repository tree declares a licence.
One object page field made read-only from another's value, two ways
Neither the package manifest nor the repository tree declares a licence.
Travel-booking reference app on CAP Node.js and Java backends
Java implementation of the capire/bookshop getting-started sample
Java implementation of the capire/bookstore composite app
Travel-booking reference app on CAP Node.js and Java backends
Bookshop app demonstrating the CAP Java SDK end to end
CAP Java travel-booking app built on xflights-java master data
UI5 app consuming the cds-bookshop server via ui5-middleware-cap
