Finish documentation for migration of JBoss EJB Legacy Client BOM

Documentation for migration of JBoss EJB Legacy Client BOM has not been finished as a part of MR eap8-documentation!275. See also related EAP7-1994 RFE and related EAPDOC-944 documentation jira.

Functional analysis of EAP7-1994 clearly state that:

content should also suggest and guide customers on how to replace usage of such deprecated legacy API

Specifically these parts needs to be finished as a part of this follow-up jira:

• Migration path from migration guide describes which classes were removed and how to write EJB client from scratch. Rewriting client from scratch could be considered as migration path, but the quality of this migration is poor, because this is too much complicated way for customers. The better migration path needs to be described in documentation. Documentation doesn't need to force customers to migrate before the end of EAP 7.4 support (according to the current version of this document, its 30th June 2025), on the other hand if customers want to migrate, migration guide should provide reasonable way for it earlier, so customers would have enough time for migration.
  • Specifically, this linked document describes removed classes, properties for InitialContext and one properties file. Migration guide needs to describe how each of this specific things can be migrated.
• According to our 7.4 product documentation, client bom can be used in both "<dependencyManagement>" and "<dependencies>" sections. This linked article contains information how to prepare java code from scratch, but there is no information about dependencies, so customers don't know how pom dependencies should be migrated from migration guide. This needs to be fixed.
  • Migration should leads to new solution with similar level of maintenance, like previous solution (removed legacy bom).