onedevatlasBeta
Browse the atlas
AllABAPCAPUI5BTP
PackagePackagetypeA library you install and call yourself.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

bothzoli/ABAP-IoC-Container

An 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.

An implementation of dependency injection in ABAP: a container that collaborators are registered with and resolved from, instead of each call site constructing what it needs. Its maintainer calls the implementation naive. The reasoning behind it is written up in Implementing an IoC Container in ABAP, which the README gives as the place for more details.

GitHub4 ★
abaplint1,627 lines

Facts

Last pushLicenceMIT

Where it sits

Lives in
ABAP
Provides
Dependency injectionABAPDependency injectioncapabilityWiring an object's collaborators from outside it, so a class can be swapped for another implementation without editing the code that uses it.

Who is behind it

Zoltan BothZoltan BothPersonMaintains this
In the atlas: maintains 1, contributes to 1@bothzolimaintainerAlexandr ZhuravlevPersonContributes to this
In the atlas: contributes to 1@alezhu1 contributor

Before choosing this

Signals

ActivityQuietNo published releases; repository quiet for 62 months

It publishes no releases, and its repository has been quiet for at least 24 full months. This may be normal for stable software; check whether its current state still fits your use.

What it declares

Every artifact

Type
Package
Origin
Independently maintained

As a package

Where it runs
does not say
Distributed through
does not say

Connections1

README

quoted from bothzoli/ABAP-IoC-Container under MIT, read
bothzoli/ABAP-IoC-Container/README.mdOn GitHub

ABAP-IoC-Container

This repository contains a naive implementation of an IoC Container in ABAP.

See this article for more details.

MIT, read

Others providing1

Compare all 2 on the Dependency injection page →
Dependency injection
  1. swixfort/Sdw.Abap.DiA dependency-injection container for ABAP: register classes or interfaces, then resolve an object with its dependencies already constructed.

Details

Sources3
dotabapdiscovered herechecked
github.com/bothzoli/ABAP-IoC-Containertree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

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
discovered viadotabap
first seen in the atlas
ecosystem and domainabap, developer-experience
abaplint
issues under its own abaplint configuration465
lines1,627
statements666
objects14
files28
analysed, master
abaplint version2.120.84
read fromabaplint.app,
Contributors1
Alexandr Zhuravlev

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:bothzoli-abap-ioc-container
JSON
/artifacts/bothzoli-abap-ioc-container.json
MCP
Connecting an agent