[
https://issues.redhat.com/browse/WFLY-14263?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFLY-14263:
-----------------------------------------
Note I don't mean to imply any particular urgency here. A unrelated minor discussion
led me to check if we use jboss-remote-naming in WF so I grepped that string and found no
real use, just this doc ref. So just a random thing I stumbled on.
Outdated "Remote EJB invocations via JNDI - EJB client API or
remote-naming project" document
---------------------------------------------------------------------------------------------
Key: WFLY-14263
URL:
https://issues.redhat.com/browse/WFLY-14263
Project: WildFly
Issue Type: Bug
Components: EJB
Reporter: Brian Stansberry
Assignee: Cheng Fang
Priority: Major
This doc looks wrong:
https://docs.wildfly.org/21/Developer_Guide.html#Remote_EJB_invocations_v...
AFAICT WildFly no longer ships org.jboss:jboss-remote-naming.
There are also a number of places where that doc refers to WildFly 21 which I believe is
a dynamic value that is now incorrect. It's generally better to not include specific
WildFly versions in the docs, as the URL for our docs already include a version number.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)