|author||Arnoud Glimmerveen <email@example.com>||Fri Nov 08 17:00:06 2019 +0100|
|committer||Christian Schneider <firstname.lastname@example.org>||Fri Nov 08 17:00:06 2019 +0100|
ARIES-1940 Handle failure that can happen during service export (#30) Changed implementation and use of ExportRegistration to align with specification Changed use of ExportRegistration to deal with cases the ExportRegistration relates to a failed exported services
The Aries Remote Service Admin (RSA) project is the reference implementation of Remote Services and Remote Service Admin from the OSGi R7 specs.
It allows to transparently use OSGi services for remote communication. OSGi services can be marked for export by adding a service property service.exported.interfaces=*. Various other properties can be used to customize how the service is to be exposed.
Aries Remote Service Admin provides two different transport layers out of the box and can be extended with custom transports.
The discovery providers are responsible for finding the available endpoint descriptions of remote services. Aries RSA provides three different implementations and can be extended with custom discovery providers. The three available implementations are
mvn clean release:prepare -DskipTests -Darguments=-DskipTests mvn release:perform -DskipTests -Darguments=-DskipTests
This creates a staging repository. After all artifacts are deployed login to the Apache maven repo and close the staging repository.
The source zip needs to be copied to the Apache release svn.
gpg --print-md SHA512 <filename> > <filename>.sha512