• Post Reply Bookmark Topic Watch Topic
  • New Topic

Replacing T3 and JNP transport protocols with HTTP protocol for EJB JNDI Lookup  RSS feed

Jack Stevens
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello everyone

I have an app that is being migrated from Weblogic 9.2 to JBoss EAP 5.

This app currently (in its weblogic form) makes ejb jndi lookups to other weblogic apps via the weblogic t3 protocol. I understand that if I need this app (when moved to JBoss) to continue to make the ejb jndi lookup calls, the app needs to add wlclient.jar to its classpath and keep the t3 lookup code.

In addition to calling some external weblogic ejbs this app also has other external weblogic apps calling its own ejbs using the t3 JNDI lookup (in its current weblogic form). I understand that if I need this app to continue to make its ejbs (when moved to JBoss) available to the other weblogic clients then the weblogic clients need some jboss client jar in their classpath and change its ejb lookup code from a t3 jndi look up to a jndi jnp lookup.

First of all, are my above assumptions correct?

My second question is can I avoid adding client jars into either Weblogic or JBoss if I use the http or https protocol for jndi ejb lookups? All I know is that both Vendors support Http/Https JNDI lookup.

Any feedback is appreciated.


Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!