celix
celix copied to clipboard
apache
Apache Celix is a framework for C and C++14 to develop dynamic modular software applications using component and in-process service-oriented programming.
# Intro Currently, it is difficult to install a generated Apache Celix container executable, including its required bundles and an optional config.properties file. This challenge can prevent users from using...
``` [ RUN ] RemoteServicesIntegrationTestSuite.InvokeRemoteCalcService [2024-01-01T00:08:42] [ info] [celix_framework] [framework_start:474] Celix framework started [2024-01-01T00:08:42] [ info] [celix_framework] [framework_start:474] Celix framework started [2024-01-01T00:08:42] [ info] [celix_framework] Starting TestExportImportRemoteServiceFactory [2024-01-01T00:08:42] [ info]...
For the next major version bump a lot deprecated functionality and functions can be dropped. Also some header files not meant for users should be made private. An overview of...
# Clarify and improve parsing of the .properties file format Apache Celix uses a .properties file to store and read configurable - framework and bundle - parameters. The Apache Celix...
Currently, the overall coverage of the framework library is around 85%. Utilizing error injector, we shall try to increase the code coverage to 90% or more. This should happen after...
# Netstring lib A netstring lib in C which can be used to encode/decode (serializer/deserialize) properties and/or metadata for remote service data and events for the - yet to be...
Our current API relies on bundle ID, which servers as a safe handle to dynamic bundle objects. Though the usage of bundle ID provides safety, it also brings inconvenience to...
# Framework statistics Implement some basic statistics for the framework (mainly service registry) to retrieve at least the following info: - Nr of service registered - Nr of service unregistered...
There is the following warning in section command's [documentation](https://www.doxygen.nl/manual/commands.html#cmdsection): > This command only works inside related page documentation and not in other documentation blocks! In our coding convention, it is...
Once #536 gets merged, we shall use ERR extensively for error logging in modules without bundle context. An example of this is `shm_pool`: https://github.com/apache/celix/blob/c0666d0ec501c54852198a18cf46eda69552ee50/bundles/remote_services/remote_service_admin_shm_v2/shm_pool/src/shm_pool.c#L46-L54