[jboss-jira] [JBoss JIRA] (WFLY-3282) Remote EJB invocations needs corrected ports and protocol

[Paul Benedict (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963931#comment-12963931 ] 

Paul Benedict commented on WFLY-3282:
-------------------------------------

Stuart, okay, I will add that note because I think the documentation implies it's totally removed. And I'd like to also document, if such an option exists, how to turn off HTTP Remoting connection upgrades so it's impossible to remote through a public port. Anything like that exist?
                
> Remote EJB invocations needs corrected ports and protocol
> ---------------------------------------------------------
>
>                 Key: WFLY-3282
>                 URL: https://issues.jboss.org/browse/WFLY-3282
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: 8.1.0.CR1
>            Reporter: Paul Benedict
>            Assignee: Darran Lofthouse
>            Priority: Minor
>              Labels: jndi, remoting
>
> This page needs updating. 
> 1) It refers to old "remote" protocol but WildFly only supports "http-remoting" through HTTP Upgrade.
> 2) All links to other pages point to AS71 not WFLY8.
> https://docs.jboss.org/author/display/WFLY8/Remote+EJB+invocations+via+JNDI+-+EJB+client+API+or+remote-naming+project

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