The vertx-eventbus.js
file is a SockJS-based event bus bridge to connect your JavaScript frontend application to Vert
.x 3.x. You can use it in a front-end application or in a node.js application.
If you already use a previous version of the bridge, please check the changelog below.
- The vert.x web site: http://vertx.io
- The Event Bus Bridge documentation: http://vertx.io/docs/vertx-web/java/#_sockjs_event_bus_bridge
Changes from the 3.2 to 3.2.1
- Update the eventbus client version to 3.2.1
Changes from the 3.1.1 to 3.2
- Update the eventbus client version to 3.2.0
Changes from the 3.1 to 3.1.1
- Update the
main
attribute in thebower.json
file.
Changes from the 3.0.x to 3.1
- IMPORTANT: The API has been changed to be compatible with node.js and to be closer to the vert.x eventbus API
.Creating the bridge is made using
var eb = new EventBus("http://localhost:8080/eventbus");
instead ofnew vertx .EventBus...
. In addition, registering a handler use the node convention:eb.registerHandler("metrics", function(err, res) {...}
instead ofev.registerHandler("metrics", res)
. - The file name has been updated to
eventbus-client.js
This project is exotic... It generate a git repository compliant with the Bower expectation. It:
- Compute the
bower.json
content and copy it to the root directory - Download the vert.x event bus bridge and copy it to the root directory
Generation is triggered by mvn clean package
-
- Open the
pom.xml
file and edit thevertx.version
property (~ project version) and thepackage.version
(packaging iteration)
- Open the
-
- Update using
mvn clean package
- Update using
-
- Add all modified files:
NOTE: the $VERSION
is the package.version
git add bower.json vertx-eventbus.js pom.xml README.md
-
- Commit
git commit -m "update version to $VERSION"
-
- Create tag
git tag -a $VERSION -m "tag for version $VERSION"
-
- Push everything
git push origin --tags master
Done.
As the repository is already registered on Bower, the update should be automatic.