Everything in the atlas
Type
Domain: 3
Origin
Signals
More: Java
Group by: Capability
Eclipse plugin bringing Claude into ABAP Development Tools
MCP server for ABAP on the ADT session, in Eclipse or standalone
In the Eclipse mode the server lives in a developer's IDE, binds to 127.0.0.1 and answers any request carrying an `Origin` header with HTTP 403, so a pipeline or a remote agent has nothing to reach; the standalone mode on the runtime of the ADT for VS Code extension is the documented route with no IDE open. A new connection starts in write mode, so the 11 write tools are live against a connected system until someone presses Toggle Read-Only. The dropins route for the two bundles is documented as untested.
A2A adapter turning a CAP Java service into an LLM-backed agent
Hands-on building an AI agent with the SAP Cloud SDK for AI
Bridge from CAP Java to SAP AI Core, with Fiori field recommendations
Hands-on building an AI agent with the SAP Cloud SDK for AI
CAP Java plugin sending audit log events to SAP Audit Log service
CAP Java handler for SAP Audit Log service API version 2
Maven bill of materials pinning CAP Java module versions
OAuth2 token validation from XSUAA and SAP Cloud Identity Services
Former XSUAA JWT validation for CAP Java, removed in CAP Java 3.0
Maven bill of materials pinning CAP Java module versions
CAP Java authorization checks tried case by case
Neither the package manifest nor the repository tree declares a licence.
Change log of annotated entity fields for CAP Java
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions
CAP Java draft cancel on composition items as a flag update
Neither the package manifest nor the repository tree declares a licence.
Maven bill of materials pinning CAP Java module versions
One object page field made read-only from another's value, two ways
Neither the package manifest nor the repository tree declares a licence.
Maven bill of materials pinning CAP Java module versions