Events Development: Difference between revisions
Jump to navigation
Jump to search
(→TODO) |
|||
(One intermediate revision by the same user not shown) | |||
Line 5: | Line 5: | ||
=TODO= | =TODO= | ||
< | <pre> | ||
doc/events TODO.docx | |||
</ | </pre> | ||
=Clone= | =Clone= |
Latest revision as of 21:00, 28 April 2017
Internal
TODO
doc/events TODO.docx
Clone
git clone git@github.com:NovaOrdis/events.git
Development
Unnumbered Development Release
This will install a new unnumbered (same release number) "development" release locally:
cdevents mvn clean install; ./bin/install -f
Numbered Release
Individual Unit Test
mvn -Dmaven.surefire.debug="-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5012" -Dtest=EventsApplicationRuntimeTest clean test
How to add New Commands
This is how you code new clad commands:
A few things to keep in mind:
- The pipeline is initialized by the runtime, but there is no queue between the event processor and terminator. The command must install it.
- The command executes on the main thread and might exit (and kill the JVM in the process) before the terminator had a chance to process its queue. Always register an EndOfStreamListerer with the terminator and wait on the main thread until that listener is notified.
Terminator terminator = runtime.getTerminator(); final CountDownLatch rendezVous = new CountDownLatch(1); terminator.addEndOfStreamListener(new EndOfStreamListener() { @Override public void eventStreamEnded() { rendezVous.countDown(); } }); // ... // // wait until terminator finishes its queue // rendezVous.await();
or, better yet:
runtime.waitForEndOfStream();