[
https://issues.jboss.org/browse/AS7-6836?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-6836:
-------------------------------------
We are also planning on adding HTTP Upgrade support in AS8, and ideally we will use this
as the default for all remote protocols that support it, so in AS8 JMS should be
accessible over HTTP as the default, with the only overhead being the initial HTTP
request.
Allow access to JMS destinations over HTTP
------------------------------------------
Key: AS7-6836
URL:
https://issues.jboss.org/browse/AS7-6836
Project: Application Server 7
Issue Type: Enhancement
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 8.0.0.Alpha1
HornetQ provides a HTTP transport and a Netty servlet to access JMS resources over HTTP.
http://docs.jboss.org/hornetq/2.3.0.CR2/docs/user-manual/html/configuring...
This involves a lot of configuration tweaks that could be handled by the messaging
subsystem so that the users just have to specify a http-connector (or servlet-connector)
and the messaging subsystem will figure out the rest (find or create a web container,
place the netty servlet into it with the appropriate web.xml configuration, etc.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira