[jboss-remoting-issues] [JBoss JIRA] Resolved: (JBREM-1074) Config Guide should clarify the HTTP transport vs Servlet

[Ron Sigal (JIRA)]

     [ https://issues.jboss.org/browse/JBREM-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Sigal resolved JBREM-1074.
------------------------------

    Resolution: Done


The explanation is made in the new Remoting Users Guide.

> Config Guide should clarify the HTTP transport vs Servlet
> ---------------------------------------------------------
>
>                 Key: JBREM-1074
>                 URL: https://issues.jboss.org/browse/JBREM-1074
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Andrew Oliver
>              Labels: documentation, http, remoting
>
> http://docs.jboss.org/jbossas/unified_invoker/UnifiedInvoker_guide.html
> describes changing to use HTTP as a transport.  Meaning JBoss remoting launches its own HTTP server.  This is probably a pretty esoteric configuration and most people are probably looking for this:
> http://www.jboss.org/community/docs/DOC-9632
> instead.  The guide should clarify WHAT that is and where to find what you're probably REALLY looking for.
> (you probably don't want to run on some weird port if you're using HTTP and most installs probably run WITH tomcat which means you need to run through TC or have a totally separate IP which is pretty hard to do in most environments)

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira