Skip to content

Commit a4b1775

Browse files
committed
added dev-msg-node-vertx
1 parent 624ae82 commit a4b1775

25 files changed

+2739
-0
lines changed
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
## dev-msg-node-vertx
2+
3+
### Setup Environment
4+
5+
#### JavaScript
6+
On the first time you are cloning this repository, you need to run the command ```npm run init-setup```;
7+
8+
After running successfully this command you will have 2 folders (node_modules and vendor), these folders are excluded from the commit process, and are only for development.
9+
10+
If you already have the project configured on your machine, you only need run the command ```npm install``` to add new dependencies;
11+
12+
If you have some trouble with the environment, you can open an issue;
13+
14+
#### Java
15+
Follow the link to [Install Maven](https://maven.apache.org/install.html).
16+
* Build the project with: mvn package
17+
* Run vertx node with: mvn exec:java
18+
19+
### Use of VertxProtoStub
20+
Once the MessageNode is active, we are able to connect with the ProtoStub. The best example of how this is done is in the test/VertxProtoStub.js in "runtime connectivity" test. It's important to send the "runtimeURL" in the config parameter, because it will be used to link the connection channel to the runtime.
21+
22+
With this it's possible to send messages between runtimes, but Hyperty registration is something that should be done externally.
23+
24+
The connection is auto managed. It means, there is no need to call "connect()" explicitly, and it will always try to be in "connected" until "disconnect()" is called. Status messages are sent to "runtimeProtoStubURL/status".
25+

0 commit comments

Comments
 (0)