[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:all-tabpanel ]

Paul Benedict updated WFLY-3282:
--------------------------------

    Description: 
This page needs updating. 
1) It refers to old "remote" protocol but WildFly only supports "http-remoting" through HTTP Upgrade.
2) The link " EJB invocations from a remote client using JNDI" points to AS71 not WFLY8

https://docs.jboss.org/author/display/WFLY8/Remote+EJB+invocations+via+JNDI+-+EJB+client+API+or+remote-naming+project

  was:
This page needs updating. It refers to old "remote" protocol but WildFly only supports "http-remoting" through HTTP Upgrade.

https://docs.jboss.org/author/display/WFLY8/Remote+EJB+invocations+via+JNDI+-+EJB+client+API+or+remote-naming+project


    
> 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: Tom Wells
>            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) The link " EJB invocations from a remote client using JNDI" points 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