cap-java-resilience
A CAP Java service consuming a Business Partner API that a CAP Node.js project in the same repository mocks, with the SAP Cloud SDK caching and resilience it is named for recorded as planned.
Two projects in one repository: business-partner-mock, a CAP Node.js service that provides a mock Business Partner API, and cap-java-resilience, the CAP Java service that consumes it — a remote-consumption loop with no real backend behind it. What the repository is named for is not in it: CLAUDE.md files the caching and resilience from SAP Cloud SDK under what "the plan is to add". That file is the only documentation, and the rest of it is instructions for an agent working in the repository.
Facts
Where it sits
Who is behind it
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer
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.
What it declares
Every artifact
- Type
- Sample
- Origin
- Independently maintained
- Use as
- A reference
- Runtime
- JavaNode.js
As a sample
- Form
- does not say
Connections
Running the whole stack on a laptop against real bindings
Using a remote service as if it were one of your own
Download
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
“THis is a CAP Java project” — CLAUDE.md — cap-java-resilience
“This is a CAP Node.js project” — CLAUDE.md — cap-java-resilience
History in the atlas
- First seen.
For your agent
- Ref
artifact:miyasuta-cap-java-resilience- JSON
- /artifacts/miyasuta-cap-java-resilience.json
- MCP
- Connecting an agent