Geek Answers Handbook

WSO2 ESB 5.0.0 BETA WebSocket InboundEndPoint

I am testing a beta version of wso2 esb 5.0.0, which has an interesting feature for me, websockets.

I declare an incoming endpoint, for example, the define documentation ( https://docs.wso2.com/display/ESB500/WebSocket+Inbound+Protocol ), but I can only receive empty messages from my client (connection is complete), and I cannot send any message to the client.

Have someone try this feature?

Thank.

PD: this is my ws incoming enpoint

<inboundEndpoint name="testws" onError="errorsq" protocol="ws"
    sequence="testwssq" suspend="false">
    <parameters>
        <parameter name="inbound.ws.port">9091</parameter>
        <parameter name="ws.outflow.dispatch.sequence">testbesq</parameter>
        <parameter name="ws.outflow.dispatch.fault.sequence">errorsq</parameter>
        <parameter name="ws.client.side.broadcast.level">1</parameter>
    </parameters>
</inboundEndpoint>

and these are my sequences

 <sequence name="testbesq">
    <log level="full"/>
</sequence>
<sequence name="testwssq">
    <log level="full"/>
    <log level="custom">
        <property name="request" value="message receive"/>
    </log>
</sequence>
+4
source share
1 answer

HTTP, , WebSocket , , . - - WebSocket. , , .

Synapse.

synapse(contentType='application/json')
synapse(contentType='application/xml')
synapse(contentType='text/xml')

Netty WebSocket , . (), <Test>message</Test>, websocket.

java -DsubProtocol="synapse(contentType='application/xml')" -DclientPort=9091 -cp netty-example-4.0.30.Final.jar:lib/*:. io.netty.example.http.websocketx.client.WebSocketClient
+3

More articles:


All Articles