Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-14263

Updating the outdated "Remote EJB invocations via JNDI - EJB client API or remote-naming project" document

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 24.0.0.Beta1, 24.0.0.Final
    • None
    • EJB
    • None
    • Undefined
    • ---
    • ---

    Description

      This doc looks wrong:

      https://docs.wildfly.org/21/Developer_Guide.html#Remote_EJB_invocations_via_JNDI_-_EJB_client_API_or_remote-naming_project

      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.

      Attachments

        Issue Links

          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-20417 [7.3] Improve EJB Client configuration documentation related to defining remote EJB servers

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Activity

            People

              rchakrab Ranabir Chakraborty
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: