| commit | 1b7cc37d52ef03d11699a67342765967e9fa5957 | [log] [tgz] |
|---|---|---|
| author | Tim Ward <timothyjward@apache.org> | Thu Sep 09 12:50:01 2021 +0100 |
| committer | Tim Ward <timothyjward@apache.org> | Thu Sep 09 13:15:26 2021 +0100 |
| tree | 4d7d56a09cb02e409ae2f7c94efeb604e9d31c2e | |
| parent | 3c58a7f1e68d4dc41970c3349fba3e78504c2bb9 [diff] |
Fix JavaDoc ahead of creating a first release
This project contains an implementation of the OSGi Typed Safe Event Service specification, and related services to allow the Type Safe Event Service to interoperate with remote event sources and consumers.
The Type Safe Event Service is defined in Chapter 157 of the OSGi R7 specification. This specification is not yet final, but public drafts of this specification are available from the OSGi Alliance.
Given that the specification is non-final the OSGi API declared in this project is subject to change at any time up to its official release. Also the behaviour of this implementation may not always be up-to-date with the latest wording in the specification . The project maintainers will, however try to keep pace with the specification, and to ensure that the implementations remain compliant with any relevant OSGi specifications.
The following modules are available for use in OSGi
If you're looking at this project then you almost certainly want to use org.apache.aries.typedevent.bus. If you also want to support distributed events then you should also take a look at the various remote event implementations present