[
https://issues.jboss.org/browse/WFLY-9459?page=com.atlassian.jira.plugin....
]
Wolfgang Knauf updated WFLY-9459:
---------------------------------
Description:
The WildFly doc contains some pages which should be updated to reflect the change to
"WildFly naming client" instead of "EJB client API"/"remote
naming project":
[EJB invocations from a remote client using
JNDI|https://docs.jboss.org/author/display/WFLY/EJB+invocations+from+a+re...]
[Remote EJB invocations via JNDI - EJB client API or remote-naming project
|https://docs.jboss.org/author/display/WFLY/Remote+EJB+invocations+via+JNDI+-+EJB+client+API+or+remote-naming+project]
This should be fixed mainly in the new asciidoc
was:
The WildFly doc contains some pages which should be updated to reflect the change to
"WildFly naming client" instead of "EJB client API"/"remote
naming project":
[link EJB invocations from a remote client using
JNDI|https://docs.jboss.org/author/display/WFLY/EJB+invocations+from+a+re...]
[link Remote EJB invocations via JNDI - EJB client API or remote-naming project
|https://docs.jboss.org/author/display/WFLY/Remote+EJB+invocations+via+JNDI+-+EJB+client+API+or+remote-naming+project]
This should be fixed mainly in the new asciidoc
Outdated doc für ejb client
---------------------------
Key: WFLY-9459
URL:
https://issues.jboss.org/browse/WFLY-9459
Project: WildFly
Issue Type: Bug
Components: Documentation
Affects Versions: 11.0.0.CR1
Reporter: Wolfgang Knauf
The WildFly doc contains some pages which should be updated to reflect the change to
"WildFly naming client" instead of "EJB client API"/"remote
naming project":
[EJB invocations from a remote client using
JNDI|https://docs.jboss.org/author/display/WFLY/EJB+invocations+from+a+re...]
[Remote EJB invocations via JNDI - EJB client API or remote-naming project
|https://docs.jboss.org/author/display/WFLY/Remote+EJB+invocations+via+JNDI+-+EJB+client+API+or+remote-naming+project]
This should be fixed mainly in the new asciidoc
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)