This topic has not yet been written. The content below is from the topic description.
16.4.4. Configuring Netty Servlet We also provide a Netty servlet transport for use with HornetQ. The servlet transport allows HornetQ traffic to be tunneled over HTTP to a servlet running in a servlet engine which then redirects it to an in-VM HornetQ server. The servlet transport differs from the Netty HTTP transport in that, with the HTTP transport HornetQ effectively acts a web server listening for HTTP traffic on, e.g. port 80 or 8080, whereas with the servlet transport HornetQ traffic is proxied through a servlet engine which may already be serving web site or other applications. This allows HornetQ to be used where corporate policies may only allow a single web server listening on an HTTP port, and this needs to serve all applications including messaging. Please see the examples for a full working example of the servlet transport being used. To configure a servlet engine to work the Netty Servlet transport we need to do the following things: Deploy the servlet. Here's an example web.xml describing a web application that uses the servlet: HornetQServlet org.jboss.netty.channel.socket.http.HttpTunnelingServlet endpoint local:org.hornetq 1 HornetQServlet /HornetQServlet We also need to add a special Netty invm acceptor on the server side configuration. Here's a snippet from the hornetq-configuration.xml file showing that acceptor being defined: org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory Lastly we need a connector for the client, this again will be configured in the hornetq-configuration.xml file as such: org.hornetq.core.remoting.impl.netty.NettyConnectorFactory Heres a list of the init params and what they are used for