cap-java-draft-composition-delete
Draft cancel on composition items turned into a flag update instead of a cascading physical delete, with the handler reading the incoming CQN so both delete paths behave the same.
The tests cover deleting an item by its own entity path and deleting it through the header-to-items navigation a Fiori list report produces — the two shapes that make a naive handler work in one case and not the other.
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
- Runtime
- Java
As a sample
- Form
- Code snippets
Connections
Editing a record over several requests before it becomes real
Download
README
quoted from miyasuta/cap-java-draft-composition-delete, readCAP Java Composition Delete Test
This project demonstrates how to implement logical deletes for composition items in a CAP Java service. Draft-enabled headers with composed items are exposed via OData V4, and delete operations from Fiori List Report-style navigation paths must not physically remove the child records.
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
History in the atlas
- First seen.
For your agent
- Ref
artifact:miyasuta-cap-java-draft-composition-delete- JSON
- /artifacts/miyasuta-cap-java-draft-composition-delete.json
- MCP
- Connecting an agent