Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-206

Allow access to JMS destinations over HTTP

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 8.0.0.Alpha2
    • None
    • JMS
    • None

    Description

      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-transports.html#d0e3665

      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.)

      Attachments

        Issue Links

          relates to

          Feature Request - Feature requests from customers and/or users WFLY-2128 Support one-port connection for JMS

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Feature Request - Feature requests from customers and/or users WFLY-328 Reintroduce the feature to allow EJB invocations over HTTP

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              jmesnil1@redhat.com Jeff Mesnil
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: