Legacy EAP5 Client JNDI lookup in EAP7.4 Server

Posted on

We have a large number of Legacy EAP5.2 Client applications that cannot be easily upgraded (read basically almost impossible). We want to upgrade our JBOSS Server to EAP7.4 but are unable to because the Legacy EAP5.2 Client applications are not able to perform a JNDI lookup using jnp (in order to lookup a JMS Queue) because it is no longer supported in EAP7.4

A Github project jboss-as-legacy-naming appears to solve this problem, but the project no longer compiles using the EAP7.4 jar files and the documentation referenced by this project https://mojo.redhat.com/docs/DOC-950104 in the article is not accessible/unavailable.

Any suggestions on how to solve this problem (Other than upgrading the Legacy Clients, which would be extremely expensive and time consuming).

Responses