swixfort/Sdw.Abap.Di
A dependency-injection container for ABAP: register classes or interfaces, then resolve an object with its dependencies already constructed.
Wiring a class's dependencies by hand means constructing every collaborator in order before the object that needs them. Sdw.Abap.Di's container lets a report register classes and interfaces, for example a service class and the two dependencies its constructor imports, then call get_instance to receive the object with those dependencies already constructed and passed in. Registration is case-insensitive, so it does not matter whether a class name is given in upper or lower case.
Facts
Where it sits
Who is behind it
In the atlas: maintains 1, contributes to 2@swixfortmaintainer
Before choosing this
Signals
RepositoryNot reachableNot reachable since 2026-10-20
Since 2026-10-20 the repository this entry names answers that it does not exist.
What it declares
Every artifact
- Type
- Package
- Origin
- Independently maintained
As a package
- Where it runs
- does not say
- Distributed through
- does not say
Connections
Wiring an object's collaborators from outside it
Download
Others providing
Compare all 2 on the Dependency injection page →- bothzoli/ABAP-IoC-Containerbothzoli/ABAP-IoC-ContainerAn inversion-of-control container for ABAP, with which collaborators are registered and resolved instead of each call site constructing what it needs; its maintainer calls it a naive implementation.independent, abapInversion-of-control container for ABAPfrom ABAP
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
abaplint
History in the atlas
- First seen.
For your agent
- Ref
artifact:swixfort-sdw-abap-di- JSON
- /artifacts/swixfort-sdw-abap-di.json
- MCP
- Connecting an agent