- also added TcpPipelineHandler for wrapping a pipeline
- added Java & Scala docs with a complete example
- test verify interop with standard blocking java SSL client and server
- test is placed in akka-remote to benefit from AkkaProvider for
SecureRandom; should be moved into akka-actor eventually
also included:
- a complete rewrite of the TCP docs based on real/tested/working code
samples
- an EchoServer implementation which handles all the edge cases,
available in Java & Scala
- renamed StopReading to SuspendReading to match up with ResumeReading
- addition of Inbox.watch()
- Inbox RST docs for Java(!) and Scala
not included:
- ScalaDoc / JavaDoc for all IO stuff
New module integration-test that contains integration tests. Created an
initial test that obtains a reference to the DiningHakkerService, creates
a dining Hakker, and then interrogates its name and current state.
The dining Hakker messages were moved to the API bundle, so that the
integration test has access to them without seeing the implementation
classes in core.
The test is run via the standard "mvn install" command.
Update Maven scala plugin to 3.1.2
Update to Akka 2.2-SNAPSHOT (failing integration test)
- Netty was updated to 3.6.2.Final (at least 3.6.0 is required by
akka-remote)
- Removed the temporary import on akka.remote.netty in core
- Removed the temporary settings in application.conf
- Changed references to akka-actor to akka-osgi
Conflicts:
core/src/main/resources/application.conf
Add karaf tar.gz/zip as deps to avoid pax exam download
Add an example of a Karaf cfg to only access jars locally
Conflicts:
project/Build.scala
Fix indentation in application.conf (Done by Raman Gupta)
Change default IP address to localhost (Done by Raman Gupta)
ServiceRegistration is typed in OSGi 4.3
Add a wildcard type for the ServiceRegistration declaration. (Done by Raman Gupta)
Fix spelling errors in Dining Hakker and Hacker (Done by Raman Gupta)
removing protobuf as bundlelized through the maven karaf feature
* Make SystemMessage extend Serializable to avoid ambiguity when
setting serialization-bindings.
* Set serialVersionUID in SystemMessages and create tests to
ensure binary formats remain unchanged.
* Add tests for reference.conf's serialization settings.
* Make some existing serialization tests more robust.
Removed boilerplate from serialization tests
Use actual reference.conf; tidy up
Make serialization compatible
* ClusterSingletonManager
* ClusterSingletonManagerSpec multi-node test
* Use in cluster router with single master sample
* Extensive logging to be able to understand what is
going on
* Java api
* Add cluster dependency to contrib
* Add contrib dependency to sample
* Scaladoc
* rst docs in contrib area, ref from cluster docs
