我想将Vert.x 3.3.2和socketJS与eventbus代理一起使用,一劳永逸地忘记URL,而只是在不创建REST接口的情况下进行消息交谈-这在Java平台上是多年来最好的事情!但是,我的世界无法正常工作。

我的测试如下:在每个已连接和断开连接的事件客户端和服务器端,它都打印在控制台上。而且,当客户端连接时,客户端会发送一条消息,服务器将对此作出响应,服务器也会向所有人发送通知。发生的情况是只有第一个客户端发送其消息并从服务器获得正确的响应。

Java:

public class App extends AbstractVerticle {

public static void main(String[] args) throws InterruptedException {
    Vertx.vertx().deployVerticle(MethodHandles.lookup().lookupClass().getName());
}

@Override
public void start() throws IOException {
    Router router = Router.router(vertx);
    BridgeOptions options = new BridgeOptions();
    PermittedOptions address = new PermittedOptions().setAddress("some-address");
    options.addInboundPermitted(address);
    options.addOutboundPermitted(address);
    SockJSHandler sockJSHandler = SockJSHandler.create(vertx).bridge(options, be -> {
        if (be.type() == BridgeEventType.REGISTER) {
            System.out.println("sockJs: connected");
            vertx.eventBus().publish("some-address", "hey all, we have a new subscriber ");
        }
        be.complete(true);
    });
    router.route("/sockjs/*").handler(sockJSHandler);
    router.route("/web/*").handler(StaticHandler.create("doc/clientSocketJS"));
    vertx.createHttpServer().requestHandler(router::accept).listen(8020, listenHandler -> {
        if (listenHandler.failed()) {
            LOGGER.log(Level.SEVERE, "Startup error", listenHandler.cause());
            System.exit(0); // stop on startup error
        }
    });
    vertx.eventBus().consumer("some-address", message -> {
        System.out.println("sockJs: received: " + message.body());
        message.reply("I received so I reply");
    });

    }

}


在doc / clientSocketJS文件夹中有一个index.html:

<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<script src="http://cdn.jsdelivr.net/sockjs/0.3.4/sockjs.min.js"></script>
<script src="js/vertx-eventbus.js"></script>
<script>
    var eb = new EventBus('http://localhost:8020/sockjs');
    eb.onopen = function() {
        console.log('connected');
        eb.registerHandler('some-address', function(error, message) {
            console.log('received: ' + JSON.stringify(message));
        });
        eb.send('some-address', {
            name : 'from ' + navigator.product
        }, null, function(a, message) {
            if (message == null) {
                console.log("ERROR: response null");
            } else {
            console.log('response: ', message.body);
            }
        });
    }
    eb.onclose = function() {
        console.log("disconnected");
        eb = null;
    };
</script>
</head>
</html>


回应如下:

加载第一个浏览器客户端:
服务器:

sockJs: connected
sockJs: received: hey all, we have a new subscriber
sockJs: received: {"name":"from Gecko"}


客户1:

connected
response: I received so I reply


这是预期的。然后加载第二个客户端(相同或其他浏览器):

服务器

sockJs: connected
sockJs: received: hey all, we have a new subscriber
(expecting a 'name' just like first time, but it doesn't appear)


客户2:

connected
(after a while) ERROR: response null  @ index.html::18


怎么了?

最佳答案

您的Java代码似乎完全正常。但是JavaScript代码看起来像是从一个旧示例中提取的。
registerHandler回调的第一个参数是消息本身,而不是错误。
为了以防万一,我还使用了托管的VertxEventBus,而不是所提供的。

这应该工作:



var eb = new vertx.EventBus('http://localhost:8020/sockjs');
        eb.onopen = function() {
            console.log('connected');
            eb.registerHandler('some-address', function(message) {
                console.log('received: ' + JSON.stringify(message));
            });
            eb.send('some-address', {
                name : 'from ' + navigator.product
            }, null, function(a, message) {
                if (message == null) {
                    console.log("ERROR: response null");
                } else {
                    console.log('response: ', message.body);
                }
            });
        };
        eb.onclose = function() {
            console.log("disconnected");
            eb = null;
        };

    <script src="http://cdn.jsdelivr.net/sockjs/0.3.4/sockjs.min.js"></script>
    <script src="https://cdnjs.cloudflare.com/ajax/libs/vertx/2.0.0/vertxbus.min.js"></script>

07-22 15:17