Qi4j is constantly growing its libraries, to maximize re-usability among developers. Libraries are slightly different from most Java APIs and subsystems out on the market in that, since we can create much smaller re-usability patterns, most libraries can be extended and modified by the user to his/her use-cases to a much higher degree than is possible in most other systems. Some other systems have flexible extensions, but it comes with a complexity price both in terms of code size as well as configuration trouble for the users. We try to avoid this to the greatest degree possible.
Each library has it's own life cycle, and work will progress according to community activity. Each library maintain a dev-status file, to provide rudimentary information about the current status of that library. This is compiled automatically in the table below.
| Library | Codebase | Tests | Documentation | Licenses |
|---|---|---|---|---|
| Authentication/Authorization | early | none | none |
|
| Beans | early | some | none |
|
| Business | none | none | none |
|
| Cache | early | none | none |
|
| Constraints | early | some | none |
|
| Exception Handling | early | none | none |
|
| Executor | early | some | none |
|
| General | early | none | none |
|
| Http Service | early | none | none |
|
| Locking | early | none | none |
|
| Logging | early | some | brief |
|
| Quikit | early | some | none |
|
| RDF | early | none | none |
|
| Registry | early | none | none |
|
| RMI | early | some | none |
|
| Spring integration | early | some | brief |
|
| Thread | none | none | none |
|
| Transaction | early | some | none |
|
| UID | early | some | brief |
|
| Validation | early | none | none |
|
